Date: Thu, 20 Dec 2001 21:07:35 -0600 From: "Robert D. Hughes" <rob@robhughes.com> To: "Luigi Rizzo" <rizzo@aciri.org>, "Yusuf Goolamabbas" <yusufg@outblaze.com> Cc: <freebsd-net@FreeBSD.ORG>, <freebsd-stable@FreeBSD.ORG>, <cez@pkl.net> Subject: RE: 4.4-stable kernel panic with dummynet/bridging. Same rules work fine with 4.3-RC Message-ID: <B95B566BD245174196CA4EE29E581883092E9F@HEXCH01.robhughes.com>
next in thread | raw e-mail | index | archive | help
Really? Its still part of the default rc.firewall that's being
distributed and I haven't seen it mentioned anywhere the its been
deprecated.
-----Original Message-----
From: Luigi Rizzo [mailto:rizzo@aciri.org]
Sent: Thursday, December 20, 2001 2:49 PM
To: Yusuf Goolamabbas
Cc: freebsd-net@FreeBSD.ORG; freebsd-stable@FreeBSD.ORG; cez@pkl.net
Subject: Re: 4.4-stable kernel panic with dummynet/bridging. Same rules
work fine with 4.3-RC
I wonder if this isn't related to some change in the handling of
interface lists, routes or arp entries. I do not recall any recent
change in the dummynet/bridge code that might cause this.
On passing. the line ${fwcmd} add 400 pass udp from 0.0.0.0 2054 to
0.0.0.0
has not been supported for a long time.
How repeatable is the problem ? It shouldn't be hard to track, it looks
like a null pointer dereference.
cheers
luigi
On Thu, Dec 20, 2001 at 11:15:45AM -0000, Yusuf Goolamabbas wrote:
> Hi, Similar to what Ceri describes in this message
>=20
>
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D508422+0+current/freebsd-s=
t
able
>=20
> I have observed a 4.4-stable box panicing whenever bridging is turned
> on. This was cvsup'ed today morning. I have other boxes cvsup'ed at
> the same time except that they don't have dummynet/bridging configured
> in them and they work pretty well
>=20
> I replaced the box with an another 4.3-RC box and the same rules
> enclosed here work just fine
>=20
> ${fwcmd} add 100 pass all from any to any via lo0
> ${fwcmd} add 200 deny all from any to 127.0.0.0/8
> ${fwcmd} add 300 deny ip from 127.0.0.0/8 to any
> # If you're using 'options BRIDGE', uncomment the following line to
pass ARP
> ${fwcmd} add 400 pass udp from 0.0.0.0 2054 to 0.0.0.0
> ${fwcmd} add 500 pass all from <ip_range> to any in via fxp0
> ${fwcmd} add 800 pipe 1 ip from <ip_range> to any in via fxp1
> ${fwcmd} pipe 1 config mask src-ip 0x000000ff bw 512Kbit/s queue 50=20
>=20
> Basically, fxp1 is connected to a switch and every machine on that
> switch is rate limited to 512Kbit/s individually
>=20
> I had configured the box with DDB but didn't have serial console so I
> transcribed everything at the db> prompt
>=20
> Fatal trap 12: page fault while in kernel mode
> fault virtual address =3D 0xa4
> fault code =3D superviser read, page not present
> instruction pointer =3D 0x8:0xc0199164
> strack pointer =3D 0x10:0xc9889b5c
> frame pointer =3D 0x10:0xc9889bac
> code segment =3D base 0x0, limit 0xfff type 0x1b
> =3D DPL 0, pres 1, def32 1, gran 1
> processor eflags =3D interrupt enabled, resume, IOPL =3D 0
> current process =3D 55 (sh)
> interrupt mask =3D
> kernel: type 12 trap, code =3D 0
> stopped at in_arpinput+0x158; movl 0xa4(%eax,%eax)
>=20
> db> t
> in_arpinput(c077cb00,0,c989cac,c020d625,c020d5df) at in_arpinput+0x158
> arpintr(c020dfdf,0,c02800,0,c7640010,c0e700,0) at arpintr+0x112
> swi_net_next(c028c26c,c764f000,3,0,c835c440) at swi_net_next
> trap_pfault(c9889d20,0,c764f000,0,806c591) at trap_pfault+0xbe
> trap(10,c9880010,c01d0010,c764f000,80be591_ at trap+0x31f
> calltrap() at calltrap+0x11
> trap 0xc : eip - 0xc02172cf , esp - 0xc9889d60, ebp - 0xc9889d88
> copyinstr(c9889e68,0,0,c9889f80,c9889f80) at copyinstr+0x37
> exec_elf_imagact(c9889e68,c835c440,3,c9889f80,c9889e68) at
exec_elf_imagact+0xba
> execve(c835c440,c9889f80,80be5d4,0,80be590) at execve+0x26c
> syscall2(2f,2f,2f,80be590,0) at syscall2+0x1a5
> Xinit0x80_syscall() + Xint-x80_syscall+0x25
>=20
> Hope this helps
>=20
> Regards, Yusuf
>=20
> --=20
> Yusuf Goolamabbas
> yusufg@outblaze.com
>=20
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B95B566BD245174196CA4EE29E581883092E9F>