Auto-Bridging LAN-ports often fails, promiscuous mode, dev_set_promiscuity

[JochenR]

Hi,
I have a strange behaviour with my bridging, which causes the LAN ports not to work anymore...

On a normal boot, the syslog looks like the following, when the LAN ports are working:

Jan  1 01:00:03 kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.37.0
Jan  1 01:00:03 kernel: PCI: Enabling device 01:02.0 (0004 -> 0006)
Jan  1 01:00:03 kernel: eth1: Broadcom BCM4318 802.11 Wireless Controller 3.90.38.0
Jan  1 01:00:03 kernel: 3:00:00:00:01 mcast address to master interface
Jan  1 01:00:03 kernel: vlan0: add 33:33:ff:6b:80:be mcast address to master interface
Jan  1 01:00:03 kernel: vlan0: dev_set_promiscuity(master, 1)
Jan  1 01:00:03 kernel: device eth0 entered promiscuous mode
Jan  1 01:00:03 kernel: device vlan0 entered promiscuous mode
Jan  1 01:00:03 kernel: device eth1 entered promiscuous mode
Jan  1 01:00:03 kernel: br0: port 2(eth1) entering listening state
Jan  1 01:00:03 kernel: br0: port 1(vlan0) entering listening state
Jan  1 01:00:03 kernel: br0: port 2(eth1) entering learning state
Jan  1 01:00:03 kernel: br0: port 1(vlan0) entering learning state
Jan  1 01:00:03 kernel: br0: port 2(eth1) entering forwarding state
Jan  1 01:00:03 kernel: br0: topology change detected, propagating
Jan  1 01:00:03 kernel: br0: port 1(vlan0) entering forwarding state
Jan  1 01:00:03 kernel: br0: topology change detected, propagating

However, very often the syslog from the same position on, will look like this:

Jan  1 01:00:03 kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.37.0
Jan  1 01:00:03 kernel: PCI: Enabling device 01:02.0 (0004 -> 0006)
Jan  1 01:00:03 kernel: eth1: Broadcom BCM4318 802.11 Wireless Controller 3.90.38.0
Jan  1 01:00:03 kernel: 3:00:00:00:01 mcast address to master interface
Jan  1 01:00:03 kernel: vlan0: add 33:33:ff:6b:80:be mcast address to master interface
Jan  1 01:00:03 kernel: device eth1 entered promiscuous mode
Jan  1 01:00:03 kernel: br0: port 1(eth1) entering listening state
Jan  1 01:00:03 kernel: br0: port 1(eth1) entering learning state
Jan  1 01:00:03 kernel: br0: port 1(eth1) entering forwarding state
Jan  1 01:00:03 kernel: br0: topology change detected, propagating

Then, the LAN ports are not working...

I cannot find any correlation of when this second thing happens. It seems to happen more often when doing "reboot" instead of power on/off. And it seems to happen more often, when having USB harddisk or stick connected - but this is not deterministic.
The syslog will always look exactly the same before the quoted lines, in both cases.

So what can I do around this behaviour?

Thanks!
Jochen

[JochenR]

I did a funny script to detect if promiscuity mode has been set correctly and otherwise reboot...

#!/bin/sh
PROMI=$(cat /tmp/syslog.log | grep dev_set_promiscuity | wc -l)

if [ $PROMI -eq 0 ]; then
        sleep 30 && reboot
else
        logger -t lan-check "Device promiscuity mode has been set (dev_set_promiscuity). No need to reboot."
fi

Do you have a better idea?

[jleinonen]

I have similar problem, but I haven't got LAn ports to bridge at all.

I have 1 device connected with LAN cable to asus. If I put this devices gw address point to asus I can ping it from asus, but nowhere else. If changed gw to point to nw real gw, then ping isn't working at all.

I looked previous posts and it seems that mine syslog is missing line:
Jan 1 01:00:03 kernel: vlan0: dev_set_promiscuity(master, 1)

How to set promiscuity correctly? FW release version is 1.9.2.7-8

Jan  1 02:00:03 kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 4.108.9.0
Jan  1 02:00:03 kernel: PCI: Enabling device 01:02.0 (0004 -> 0006)
Jan  1 02:00:03 kernel: eth1: Broadcom BCM4318 802.11 Wireless Controller 4.108.9.0
Jan  1 02:00:03 kernel: device eth0 entered promiscuous mode
Jan  1 02:00:03 kernel: device vlan0 entered promiscuous mode
Jan  1 02:00:03 kernel: device eth1 entered promiscuous mode
Jan  1 02:00:03 kernel: device vlan1 entered promiscuous mode
Jan  1 02:00:03 kernel: br0: port 3(vlan1) entering learning state
Jan  1 02:00:03 kernel: br0: port 2(eth1) entering learning state
Jan  1 02:00:03 kernel: br0: port 1(vlan0) entering learning state
Jan  1 02:00:03 kernel: br0: port 3(vlan1) entering forwarding state
Jan  1 02:00:03 kernel: br0: topology change detected, propagating
Jan  1 02:00:03 kernel: br0: port 2(eth1) entering forwarding state
Jan  1 02:00:03 kernel: br0: topology change detected, propagating
Jan  1 02:00:03 kernel: br0: port 1(vlan0) entering forwarding state
Jan  1 02:00:03 kernel: br0: topology change detected, propagating

[jleinonen]

I have similar problem, but I haven't got LAn ports to bridge at all.

Problem solved: I had configured Wireless -> advanced -> Extended mode: Station, instead of Ethernet Bridge. After changed Ethernet Bridge LAN ports started to work