| Main index | Section 4 | Options |
options ALTQ_CBQ options ALTQ_CODEL options ALTQ_RED options ALTQ_RIO options ALTQ_HFSC options ALTQ_CDNR options ALTQ_PRIQ options ALTQ_FAIRQ
The user interface for ALTQ is implemented by the pfctl(8) utility, so please refer to the pfctl(8) and the pf.conf(5) man pages for a complete description of the ALTQ capabilities and how to use it.
| ALTQ | Enable ALTQ. |
| ALTQ_CBQ | Build the "Class Based Queuing" discipline. |
| ALTQ_CODEL | |
| Build the "Controlled Delay" discipline. | |
| ALTQ_RED | Build the "Random Early Detection" extension. |
| ALTQ_RIO | Build "Random Early Drop" for input and output. |
| ALTQ_HFSC | Build the "Hierarchical Packet Scheduler" discipline. |
| ALTQ_CDNR | Build the traffic conditioner. This option is meaningless at the moment as the conditioner is not used by any of the available disciplines or consumers. |
| ALTQ_PRIQ | Build the "Priority Queuing" discipline. |
| ALTQ_FAIRQ | |
| Build the "Fair Queuing" discipline. | |
| ALTQ_NOPCC | |
| Required if the TSC is unusable. | |
| ALTQ_DEBUG | |
| Enable additional debugging facilities. | |
Note that Ns cannot be loaded as kernel modules. In order to use a certain discipline you have to build it into a custom kernel. The pf(4) interface, that is required for the configuration process of ALTQ can be loaded as a module.
The ndis(4) framework also has support for ALTQ and thus all encapsulated drivers.
The tun(4) and ng_iface(4) pseudo drivers also do support ALTQ.
| ALTQ (4) | March 20, 2018 |
| Main index | Section 4 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | Hang in there, people suffering from natural disasters and deadly diseases - we're putting ribbons on our cars as fast as we can | ” |
| — Artur Bagyants | ||