On Wed, May 10, 2017 at 4:47 AM, Gabriele Tozzi <gabri...@tozzi.eu> wrote: > I have a quite simple pf setup: I have defined 3 queues for my external > interface in my pf.conf: > > queue ext on $Ext bandwidth 900K > queue normal parent ext bandwidth 386K, max 850K qlimit 10 default > queue high parent ext bandwidth 193K qlimit 10 > queue low parent ext bandwidth 193K, max 540Kb qlimit 10 > > I have noticed that the "high" queue got the wide majority of traffic, > so I have removed all the rules referencing it from pf.conf and, > surprisingly, this is the result after reloading the ruleset: > > # pfctl -s queue -v > [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: > 0 ] > [ qlength: 0/ 50 ] > queue ext on pppoe0 bandwidth 900K qlimit 50 > [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: > 0 ] > [ qlength: 0/ 50 ] > queue normal parent ext bandwidth 386K, max 850K default qlimit 10 > [ pkts: 1555 bytes: 130921 dropped pkts: 0 bytes: > 0 ] > [ qlength: 0/ 10 ] > queue high parent ext bandwidth 193K qlimit 10 > [ pkts: 19303 bytes: 28319771 dropped pkts: 179 bytes: > 255401 ] > [ qlength: 0/ 10 ] > queue low parent ext bandwidth 193K, max 540K qlimit 10 > [ pkts: 4863 bytes: 4044635 dropped pkts: 487 bytes: > 176124 ] > > Still a lot of data is sent through the "high" queue, even if no rules > in pf.conf is referencing it. As a counter-proof, I can remove the queue > creation line from pf.conf and reload the ruleset without triggering any > error, so the queue is definitely not referenced. > > What could be wrong?
You'll have to post your pf.conf.
