Date: Fri, 26 Jan 2001 22:18:36 -0800 (PST) From: admin@allegan.net To: freebsd-gnats-submit@FreeBSD.org Subject: i386/24666: ipfw bridging and dummynet causes panic in 4.2,4.1 and stops in 3.5.1 Message-ID: <200101270618.f0R6Iak50861@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 24666 >Category: i386 >Synopsis: ipfw bridging and dummynet causes panic in 4.2,4.1 and stops in 3.5.1 >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 26 22:20:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Sean Gum >Release: 4.2, 4.1 , 3.5.1 >Organization: Allegan Internet Services, Inc. >Environment: FreeBSD bandwidth.allegan.net 3.5.1-RELEASE FreeBSD 3.5.1-RELEASE #0: Fri Jan 26 21:06:27 EST 2001 sean@bandwidth.allegan.net:/usr/src/sys/compile/FWKERNEL i386 >Description: 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. >How-To-Repeat: Enable bridging ipfw and dummynet. >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. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101270618.f0R6Iak50861>