On 21.09.2014 20:56, Kevin Gerrard wrote:
I was receiving this same error a few days ago. It was because I had a
rule
that was referring to a table that was not there or something another.
That
was the exact error I received. Finally figured that out and it has
been
flawless since.
The rule to flush queues only is : pfctl -F queue
There is no such option, you may see pfctl(8)
[ns]~$ pfctl -F queue
pfctl: Unknown flush modifier 'queue'
usage: pfctl [-deghnPqrvz] [-a anchor] [-D macro=value] [-F modifier]
[-f file] [-i interface] [-K host | network]
[-k host | network | label | id] [-L statefile] [-o level] [-p
device]
[-S statefile] [-s modifier [-R id]] [-t table -T command
[address ...]]
[-x level]
I also had to reboot to get away from that error but it was something
to do
with a table that was not right or a rule referring to the wrong table.
Can't remember why exactly but it was a typo.
As for max queues here is a simple few line queue rule to try and it is
tested and works. All it does is control MAX bandwidth on the interface
for
me. It is tested and works.
##### Queues #####
######################################################################
queue download on $int_if bandwidth 10M, max 10M
queue down parent download bandwidth 10M default
queue upload on $ext_if bandwidth 10M, max 10M
queue up parent upload bandwidth 10M default
Keep in mind this is a fiber connection where AT&T lets us spike above
our
25Mbit limit.... for a price, therefore we put this rule in to keep
that
from happening.
Hope this helps.
Kevin Gerrard
Thanks for your time. I'm going to rewrite my rulesets with minimum for
my needs and I'll test again.
