Age | Commit message (Collapse) | Author |
|
|
|
since we do not modify the struct pf_altq *a any more but our private copy,
we can of course not inherit teh scheduler type from it, since it did not
inherit the scheduler type from the parent.
so just inherit the scheduler type from the parent directly...
ok dhartmei@ cedric@
|
|
it. modifying the original one had undesired side effects if a queue was
expanded to more than one because it belonged to more than one interface
ok pb@ cedric@ dhartmei@
|
|
resolution we can handle), don't say it must be >6KB, the value actually
depends on quite some factors, including interface MTU. Instead, calculate
the real minimum value and show that.
mpech@ did a good job in bugging me to fix that ;-)
ok pb@ dhartmei@ cedric@
|
|
ok cedric@ pb@
|
|
ok dhartmei@ henning@
|
|
ok jmc@
|
|
calculation, in verbose output (pfctl -vvsr). Instead, use a new flag -g for
that.
result of a longer discussion with dhartmei@ and jakob@
ok cedric@ pb@
|
|
when looking up the queue IDs using qname_to_qid, we do not need to limit
the matching on the interface in question, as it is guaranteed that same
named queues on different interfaces habe the same queue id. moreover, we
must not limit the matches to the interface if we do not have an interface
given on the filter rule to match on ;-)
found after problems reported by Andre Nathan <andre at v2r dot com dot br>
ok dhartmei@ pb@ cedric@
|
|
ok jmc@ henning@
|
|
|
|
-do not print 100.00Kb but 100Kb, but still 1.50Mb. requested by theo. hint
by dhartmei lead to a easier algorithm than initially had
-while beeing there, use a much nicer, shorter algorithm for determining
and printing the unit. a little further easification thanks to a hint by
markus@
ok dhartmei@ cedric@
|
|
print the bandwidth in percent instead of the calculated absolute value.
if a queue belongs to more than one interface and they have different
bandwidth the calculated absolute is of course different per interface.
previously the first calculated absolute value was shown; what of course is
incorrect on the second interface. note that only the print was wrong, the
correct values were passed to the kernel.
ok theo daniel
|
|
the control class was a legacy of the original CBQ design by LBL/Sun
to support RSVP.
the control class is not used in openbsd, in the sense that
we don't automatically set filters for ICMP/IGMP/RSVP for the control
class.
ok dhartmei@ kjc@ deraadt@
|
|
same queue id. in the usual case this was already true, but not guaranteed.
ok dhartmei@ kjc@
|
|
ok deraadt@ henning@
|
|
reuse the value of r->qid if not.
ok dhartmei@ mcbride@
|
|
ok dhartmei@ cedric@
|
|
ok dhartmei@ henning@
|
|
|
|
symset() but just prepend a new sym entry to symhead like we always did. as
symget searches the list sequentially, the newest one is picked first.
prevents an endless loop introduced when trying to reuse the existing entry
by an invalid setting for the next pointer.
fixes regress test pf57.
found after conversation with Chris Linn, celinn at mtu dot edu
ok dhartmei@ cedric@
|
|
ok henning@
|
|
ok cedric@ dhartmei@
|
|
interface, found by krause (who is doing EXCELLENT work. Thank you very
much!), fix by me, ok dhartmei@ and cedric@
|
|
|
|
|
|
with jasondixon at myrealbox dot com
ok dhartmei@
|
|
a /prefix), reported by Jason Dixon. ok henning@
|
|
ok markus@
|
|
from krause
|
|
Produce wrong output on pfr7 regression test, discovered by henning@.
ok+testing henning@
|
|
smith.
ok dhartmei@
|
|
due to a bug in the loadopt check options were always loaded no matter which
loadopts where specified.
while beeing there, move the prints for that to where they belong, into the
appropriate pfctl_set_* functions, and thus only print when the options are
actually loaded.
fixes regress tests pfopt3, pfopt4, pfopt5 I added earlier.
ok dhartmei@
|
|
|
|
|
|
shadows a global. rename.
|
|
mcbride@, dhartmei@ ok
|
|
mcbride@, dhartmei@ ok
|
|
|
|
extif>"whatever"
should not be the same as
extif="whatever"
but a syntax error.
|
|
|
|
ok pb@ mcbride@ deraadt@
|
|
might have occured before.
|
|
|
|
Ok dhartmei@
|
|
|
|
|
|
|
|
about
|
|
without '!' everywhere
ok dhartmei@
|