News: This forum is now permanently frozen.
Pages: [1]
Topic: Bridged LAN cable must be plugged in or else traffic stops on all interfaces  (Read 1151 times)
« on: January 23, 2012, 06:57:57 »
trs *
Posts: 1

Hey all,

I'm running M0n0Wall 1.33 on a Soekris net4801 machine. I have a wireless Atheros mini-pci card installed, and the three NICs that come by default. I have the Wan plugged in, a Lan, and the third NIC is bridged with the LAN. The wireless is also bridged with the Lan.

Everything works fine as long as there are three ethernet cables plugged in and the devices connected are powered on. (I'm connected on a laptop via wireless) The strange thing is, if I unplug the cable that is bridged with the LAN, all traffic stops (internet, can't ping the router, etc.). As soon as I plug the cable back in everything is back to normal.

Any ideas? It's driving me nuts, I've tried removing the adapter from the webgui, rebooting, but nothing works. I don't want to have to have another device turned and on and plugged in when I'm not using it just to make the router happy. Thanks
« Last Edit: January 23, 2012, 07:05:09 by trs »
« Reply #1 on: January 23, 2012, 10:20:02 »
Јаневски ***
Posts: 153

Hey all,

I'm running M0n0Wall 1.33 on a Soekris net4801 machine. I have a wireless Atheros mini-pci card installed, and the three NICs that come by default. I have the Wan plugged in, a Lan, and the third NIC is bridged with the LAN. The wireless is also bridged with the Lan.

Everything works fine as long as there are three ethernet cables plugged in and the devices connected are powered on. (I'm connected on a laptop via wireless) The strange thing is, if I unplug the cable that is bridged with the LAN, all traffic stops (internet, can't ping the router, etc.). As soon as I plug the cable back in everything is back to normal.

Any ideas? It's driving me nuts, I've tried removing the adapter from the webgui, rebooting, but nothing works. I don't want to have to have another device turned and on and plugged in when I'm not using it just to make the router happy. Thanks

Hmm... something in physical interface up and interface down procedure brings up and down the whole bridge as far as I could understand...

A workaround is to use separate networks for every interface, and add rules to permit access from one network to the others and vice versa, this must work, if this fails then it's surely a hardware problem.

« Reply #2 on: January 27, 2012, 04:49:39 »
cmb *****
Posts: 851

The interface with the IP address must be up for that IP to be reachable. IIRC m0n0wall doesn't have the ability to assign the bridge interface itself (which is the typical work around as it will never be down), so you'll have to make sure whichever NIC has the IP is always up. The wireless card is probably a good choice since it can't be unplugged.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines