Hacker News Reader

Comment by knorker | Hacker News Reader

But it doesn't have QoS, right? Sure, shaping is all well and good, but this really all there is to it in OpenBSD.

I was shocked that a server OS this old could be this immature on something this basic.

It pretty much excludes it from being a serious router/firewall.

I am not sure what is meant by this. It certainly seems to have QoS in the form of the queue directive. It works for me for limiting buffer bloat on my VDSL model upstream. The defaults work well for my VOIP stuff so that all I have is this in my pf.conf:

    queue outq on re1 flows 1024 bandwidth 3000K max 3000K qlimit 1024 default

I think the magic is in the "flows" part.

Added: Relevant articles:

* https://dataswamp.org/~solene/2021-08-30-openbsd-qos-lan.htm... * https://www.pauladamsmith.com/blog/2018/07/fixing-bufferbloa...

Like I said, this is a very superficial view of QoS.

And I'm surprised OpenBSD only did the bare minimum.

as said, the "flows" keyword actually summons fq_codel to the task which represents the state of the art in sane-by-default QoS implementations.

Not sure what exactly you mean by QoS, but there is the `prio` keyword, which lets you put packets into priority queues.

However, I tried it a while back and couldn’t actually make it do anything useful, but that might have been me misconfiguring it.

you can filter packets by TOS bits and queue them the way you want

OpenBSD is pretty good by default. Traffic with different TOS is separately queued with reasonable priority defaults. So you normally don't have to do anything.

I was a bit surprised that my VOIP stuff was just working when I moved my router from Linux to OpenBSD and had to go looking to figure out why.

state of the art is to put packets into separate queues based on the 4-tuple (src,dst,port) then dequeue them fairly based on packet- and queuesize

Reply on news.ycombinator.com