A little longwinded, but the crux of the matter is my firewall locks up
once the bridge is enabled, but here is the entire story --> I sat down
today tried my bridging firewall again. I started with a nice clean 2.4.17
kernel. Patched it with the following files in that order:
01_config_inet_dependency.diff
02_enslave_bridge_dev_to_bridge_dev.diff
2_4_fix_port_state_handling.diff
bridge-nf-0_0_5-against-2_4_17.diff
The last bridge-nf-0_0_5-against-2_4_17.diff had one hunk failed in
br_device.c, gave that 'appears to be patched, assume -R?' error, which I
answered "n" to and "n" to 'patch anyway?' as well.
That done, I made the kernel, enabling the experimental options (thats
"Prompt for development and/or incomplete drivers" under "Code maturity
level options" if anyone makes a kernel with xconfig instead of the text
based one.
Kernel compilied nicely, I copied things to the relevent places and
rebooted into the new kernel.
Everything appeared fine. The two network cards eth0 and eth1 that form
my bridge tested out ok, so then I got to set up the bridge.
I put eth0 and eth1 into promisc mode, then used the following commands:
brctl addbr br0
brctl addif br0 eth0
brctl addif br0 eth1
ifconfig br0 up
This is where the fun starts. After about twenty seconds the machine
locks up solid. No network activity, mouse, keyboard, nothing. You need
to do a hard reset.
This happens whenever I bring up the bridge, regardless of which network
cards are part of it. (The machine has 3 network cards in it). If eth0
(A DEC tulip card) is in the bridge, in /var/log/messages you get one or two:
"kernel:eth0:(6) System Error occurred (1)"
just before it locks up.
Yersterday, the same machine was bridging wonderfully with exactly the
same configuration, only the firewall component wasn't loaded, so I think I
can say the problem is down to the firewalling. However, ebfore I start
hitting my head against a brick wall I thought I'd ask and see if anyone
else has had problems like this or can offer any suggestions?
The machine is a PII, 400Mhz, running Redhat 7.1 with kernel 2.4.17. It
has three network cards, eth0=DEC tulip; eth1=Eepro100 and eth2=3Com
3c590c, but only eth0 and eth1 take part in the bridge.
Thanks,
Ryan.
--
Ryan McConigley - Systems Administrator _.-,
Computer Science University of Western Australia .--' '-._
Tel: (+61 8) 9380 7082 - Fax: (+61 8) 9380 1089 _/`- _ '.
Email: [EMAIL PROTECTED] - http://www.cs.uwa.edu.au/~ryan '----'._`.----. \
` \;
"You're just jealous because the voices are talking to me" ;_\
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
