Thanks to everyone who contributed to this thread. Replies were not what I hoped for, but I still appreciate I didn't get just silence.
My claims about the issue were: - setting prio as per manpage instructions does not throttle lower-priority traffic - setting bandwidth on queues as manpage instructs does not shape traffic to declared bandwidth, unless queues are fixed with undocumented mandatory min and max values I hoped for something like: - observe output of this and that, post it here so we can check facts and give you clear instruction on how to achieve your goal - (or at least) it is not possible with contemporary OpenBSD I got: - try what you already have - I have also noticed it - recompile the kernel with unsupported option - I guess I made it work for me by doing undocumented thing I think that the fact that a network admin with 10 years worth of experience with OpenBSD and PF has to spend more than 50 hours of reading bits and pieces on the Internet in order to classify low-priority traffic and throttle it down when higher-priority traffic is on the wire, and still not succeed in it, proves bad state of either relevant official documentation, or software capabilities. New queueing mechanism might be cool from developer's point of view, but if people who actually configure production firewalls need 50 hours not to accomplish the same goal which they used to accomplish in 20 minutes, I'm sure they would go for uncool queueing mechanism of old. So, when I post "your shiny new queueing mechanism doesn't do its job, and your famous documentation is incorrect" on openbsd-misc mailing list, developers are hush? Hope this is due to Christmas holidays... -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
