Bug 24666

Summary: ipfw bridging and dummynet causes panic in 4.2,4.1 and stops in 3.5.1
Product: Base System Reporter: admin <admin>
Component: i386Assignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description admin 2001-01-27 06:20:01 UTC 
When trying to implement ipfw with bridging and dummynet, it isn't
stable at all. I tried 4.2 and received a panic whenever I enabled net.link.ether.bridge_ipfw.
Same thing in 4.1. I then went back to 3.5.1 and it will run, however
after running for a few minutes it quits responding.

Fix: 

Only on 3.5.1. Issue a sysctl -w net.link.ether.bridge_ipfw=0 then
wait a few seconds then issue sysctl -w net.link.ether.bridge_ipfw=1 and
it starts responding again for a few minutes then dies again.
On 4.1 and 4.2 I couldn't determine a fix. I've tried several different
types of network cards, both PCI and ISA to no avail.
How-To-Repeat: Enable bridging ipfw and dummynet.
Comment 1 tmoestl 2001-01-27 17:17:24 UTC 
Hi,

this bug has hopefully been fixed in -STABLE (after 4.2 was released).
An update should help you.

	- thomas
Comment 2 admin 2001-01-28 20:14:48 UTC 
Thank you, Thomas!!!!!
That did the trick! I upgraded to 4.2-STABLE and the ipfw, bridging and
dummynet work like a charm! I am once again a happy camper!
Sean
Comment 3 ru freebsd_committer freebsd_triage 2001-01-29 07:48:22 UTC 
State Changed
From-To: open->closed

Originator reports that the panics disappeared with the recent code.