Bug #3619
closed
ipfw/dummynet not always loaded when required in 2.2
Added by Chris Buechler about 10 years ago.
Updated over 9 years ago.
Category:
Operating System
Description
Any attempt at loading a rules.limiter file results in:
: ipfw /tmp/rules.limiter
Line 2: setsockopt(IP_DUMMYNET_CONFIGURE): Protocol not available
for example this rules.limiter:
pipe 1 config bw 10Mb plr 0.8
pipe 2 config bw 10Mb plr 0.0
This is i386, not sure whether amd64 is affected.
- Subject changed from Limiters not working on 2.2 to ipfw/dummynet not always loaded when required in 2.2
forgot to mention, I manually kldloaded ipfw as it wasn't there, but didn't on dummynet. After kldload of dummynet as well, things work.
The limiters in this case were only defined under Firewall>Traffic Shaper, Limiter. They weren't applied to any firewall rules. So maybe that's the specific bug, it's only checking whether limiters are in active use in a rule when determining whether or not to load ipfw and/or dummynet? Haven't looked at that hypothesis at all.
Strange since the code to load the module is there already.
- Status changed from New to Feedback
This has been fixed with the bug on kldstat on 10.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by Ermal Luçi 
Updated by