In this article, we will explore the topic of ALTQ in depth, examining its origins, its impact on contemporary society and its relevance in different areas of daily life. In order to better understand this phenomenon, we will delve into its history, analyze different perspectives and give a voice to experts in the field. Throughout these pages, I invite the reader to reflect on ALTQ from various perspectives and to question their own preconceived ideas about it. I hope that this article proves to be a source of knowledge and inspiration, and that it contributes to enriching the dialogue around ALTQ.
The content on this page originally appeared in the FreeBSD man pages for ALTQ and pf.conf, and from the original ALTQ webpage. |
ALTQ (ALTernate Queueing) is the network scheduler for Berkeley Software Distribution. ALTQ provides queueing disciplines, and other components related to quality of service (QoS), required to realize resource sharing. It is most commonly implemented on BSD-based routers. ALTQ is included in the base distribution of FreeBSD, NetBSD, and DragonFly BSD, and was integrated into the pf packet filter of OpenBSD but later replaced by a new queueing subsystem (it was deprecated with OpenBSD 5.5 release, and completely removed with 5.6 in 2014).[1]
With ALTQ, packets can be assigned to queues for the purpose of bandwidth control. The scheduler defines the algorithm used to decide which packets get delayed, dropped or sent out immediately. There are five schedulers currently supported in the FreeBSD implementation of ALTQ: