Date: Sun, 24 Sep 2000 23:36:21 -0700 (PDT) From: x69@x69.net To: freebsd-gnats-submit@FreeBSD.org Subject: misc/21534: ipfw + bridging + 4.x release = crash Message-ID: <20000925063621.96B7837B42C@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 21534 >Category: misc >Synopsis: ipfw + bridging + 4.x release = crash >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Sep 24 23:40:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Gerard D. >Release: 4.1-stable >Organization: skycom1 >Environment: bash-2.04$ uname -a FreeBSD freebsd.x69.net 4.1-RELEASE FreeBSD 4.1-RELEASE #5: Mon Sep 25 01:02:48 CDT 2000 root@freebsd.x69.net:/usr/src/sys/compile/x69 i386 >Description: when i enable bridging and firewalling support into the kernel and set a firewall rule ie ipfw add pipe 1 ip from any to any ipfw pipe 1 config delay 20ms or config any pipe it will make the system page fault and crash.. >How-To-Repeat: add options IPFIREWALL and options DUMMYNET into the kernel set the sysctl var net.link.ether.bridge=1 and net.link.ether.bridge_ipfw=1 then add a pipe like "ipfw add pipe 1 ip from any to any" then config the pipe like "ipfw pipe 1 config delay 20ms" and soon as any data passes through the bridge it will cause the kernel to pagefault.. >Fix: i wish i knew.. >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?20000925063621.96B7837B42C>