News: This forum is now permanently frozen.
Pages: [1]
Topic: random dc in bridge mode  (Read 3203 times)
« on: October 23, 2012, 18:37:47 »
pin117 *
Posts: 3

Hi,

I use the m0n0wall since more than a year without any problem, but changed 2 days ago the configuration to bridge 2 of the 3 networkadapter. Since then I get trouble: random disconnects on WAN-Port.

M0n0wall Version is 1.33 (built on Wed Mar 16 12:01:42 CET 2011) running on the ALIX platform from pc engines (Z├╝rich).

WAN Port is DHCP (IP from ISP)
LAN Port just 192.168.1.1/24
3rd Port Bridged to LAN

Errorlog says:
...
Oct 23 16:24:13    last message repeated 39 times
Oct 23 16:14:40    last message repeated 23 times
Oct 23 16:03:16    last message repeated 6 times
Oct 23 16:02:46    last message repeated 5 times
Oct 23 16:01:56    kernel: vr2: watchdog timeout
Oct 23 16:00:25    dhclient: bound to 82.136.110.x-- renewal in 1732 seconds.
Oct 23 16:00:25    dhclient: New Broadcast Address: 82.136.110.xx
Oct 23 16:00:25    dhclient: New Network Number: 82.136.110.xx
Oct 23 15:59:52    last message repeated 19 times
Oct 23 16:00:25    dhclient: DHCPACK from 212.4.65.xx
Oct 23 16:00:25    dhclient: DHCPREQUEST on vr0 to 212.4.65.xx port 67
Oct 23 15:55:17    last message repeated 30 times
Oct 23 15:44:52    kernel: vr2: watchdog timeout
Oct 23 15:40:31    kernel: vr2: watchdog timeout
Oct 23 15:40:01    kernel: vr2: watchdog timeout
...

The result is a complete dc of my network as you can see above.

I remember that bridges can be painfull in wrong configuration. But in this case the bridged IP-Range is greyed out and the function on board of m0n0wall. Before I changed into bridgemode the problem was not there and I used on the 3rd LAN-Port 192.168.2.1/24.

I allready diconnected all additional bridges, switches (exept one swicth) to find out where the problem comes from.

Any idea?

PS: I found now in the configuration that I had still "Enable syslog'ing to remote syslog server" into the 192.168.2.1 network. Maybe this was the reason? I changed it now and will check...
« Last Edit: October 23, 2012, 19:05:09 by pin117 »
« Reply #1 on: October 23, 2012, 21:08:02 »
pin117 *
Posts: 3

yes, looks like this was the reason - no dc anymore untill now.

The IP for the syslog was set before i changed the port to bridge and was still active. The IP did'nt exist anymore and caused the crashes (overflows?).
« Reply #2 on: October 25, 2012, 23:00:43 »
pin117 *
Posts: 3

no, still dc's
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines