solution from @moore : maybe this (define vlan for each dsa-port and the cpu-port) can be used to sniff traffic on the bridge:
ifconfig eth0 up
ifconfig lan1 up
ifconfig lan0 up
brctl addbr br0
brctl addif br0 lan1
brctl addif br0 lan0
vconfig add br0 10
ifconfig br0 up
ifconfig br0.10 10.10.10.254 netmask 255.255.255.0
echo 1 > /sys/class/net/br0/bridge/vlan_filtering
echo 1 > /sys/class/net/br0/bridge/vlan_stats_enabled
bridge vlan show
bridge vlan add dev lan0 vid 10 # define vlan10 for lan0
bridge vlan add dev br0 vid 10 self
bridge vlan show
if you are using ip instead ifconfig (shortened only as example):
ip link set eth0 up
ip link add link br0 name br0.10 type vlan id 10
ip addr add 10.10.10.254/24 dev br0.10
have not tried it yet, because i have no bridge on my device and currently not much freetime. if i understand it right, you can let tcpdump listen to br0.10 to get lan0-traffic
Did you finaly solve it?
Iām in the same situation. Iām really frustrated, due Iām unable to reach a solution with bridgingā¦ Imā going to test it at old style, with ARP Proxy, but I really know that is is not the best choice.
There is a userspace tool called devmem2. Afair you need CONFIG_DEVKMEM option to get /dev/kmem to work on it. Imho it should not be used in productive environments as it gives full access to memory and is potential security hole