Hi,
Over last few months, in a few separate threads here on misc@, I have
been trying to call attention to the fact that pf queueing mechanism
does not shape traffic as it should, at least on my APU box.
It took me some time to test hundreds of possible configurations on 5.8,
both amd64 and i386, and I have come to the conclusion it definitely
can't do even simple shaping, like splitting parent queue to 3 child
queues, giving each one of them maximum bandwidth of parent queue
when other queues are empty, but throttling them appropriately when
other queues request their bandwidth:
-----
queue download on $if_int bandwidth 10M max 10M
queue ssh parent download bandwidth 1M
queue web parent download bandwidth 8M
queue bulk parent download bandwidth 1M default
match to port ssh set queue ssh
match from port ssh set queue ssh
match to port { 80 443 } set queue web
match from port { 80 443 } set queue web
-----
In above configuration, ftp transfer (bulk, default) never gets
throttled so that http transfer (web) gets its 8M when it kicks in.
If OpenBSD didn't have all these great, elegantly configurable daemons
such as carp/pfsync, openbgpd, openospfd, ipsec and npppd, which have
been serving me for a decade without problems, I wouldn't have been
returning here asking for help, even though I had been repeatedly
ignored, and sometimes even insulted for doing it. I would look for
alternatives instead. But I know there aren't (m)any of them that can
combine all these functionalities in single, stable, secure, elegant OS.
So, what exactly do I need to do to submit bug report? Any outputs of
any commands? Logs? I understand developers won't take my word for it,
but I simply don't know how to prove it, except watching output of
systat queues and monitoring queue bandwidth in real time.
Regards,
--
Before enlightenment - chop wood, draw water.
After enlightenment - chop wood, draw water.
Marko Cupać
https://www.mimar.rs/
