ard <[email protected]> writes: > It sounds like the switch in your wrt is configured wrongly. > Can you try all other ports and see if you still get tagged > traffic?
wrt54gl v1.1 physical port "Internet" ------------------------------------- sends dhcp queries and does not reply to arp since it has no IP address. 19:20:44.619337 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:1e:e5:45:de:94, length 361 19:20:44.652976 arp who-has 192.168.1.1 tell 192.168.1.5 19:20:45.652975 arp who-has 192.168.1.1 tell 192.168.1.5 I killed dhcp client and did "ifconfig eth0.1 192.168.1.2". After that it replies but encapsulates replies in vlan 1: 19:26:41.824972 arp who-has 192.168.1.2 tell 192.168.1.5 19:26:41.825282 vlan 1, p 0, arp reply 192.168.1.2 is-at 00:1e:e5:45:de:94 19:26:42.824976 arp who-has 192.168.1.2 tell 192.168.1.5 19:26:42.825288 vlan 1, p 0, arp reply 192.168.1.2 is-at 00:1e:e5:45:de:94 wrt54gl v1.1 physical ports "1", "2", "3" and "4" ------------------------------------------------- replies to arp requests but encapsulates replies in vlan 0: 19:22:12.253984 arp who-has 192.168.1.1 tell 192.168.1.5 19:22:13.252994 arp who-has 192.168.1.1 tell 192.168.1.5 19:22:13.253336 vlan 0, p 0, arp reply 192.168.1.1 is-at 00:1e:e5:45:de:94 19:22:14.269985 arp who-has 192.168.1.1 tell 192.168.1.5 19:22:14.270321 vlan 0, p 0, arp reply 192.168.1.1 is-at 00:1e:e5:45:de:94 19:22:15.269975 arp who-has 192.168.1.1 tell 192.168.1.5 19:22:15.270316 vlan 0, p 0, arp reply 192.168.1.1 is-at 00:1e:e5:45:de:94 >> config switch eth0 >> option vlan0 "0 1 2 3 5*" >> option vlan1 "4 5" > > Well, I keep wondering if that's the right config. It changes > with each hardware release. In the sense that the ports are openwrt-wrt54g-squashfs.8.09.1.bin release works and has identical vlan options in that file. > On the other hand: if a normale release does wrok (with the same > network config), it just might be a bug in the scripts. > You can determine the real settings in /proc/switch/eth0 or other > way around. r...@openwrt:/# find /proc/switch/eth0 -type f | xargs head ==> /proc/switch/eth0/vlan/15/ports <== ==> /proc/switch/eth0/vlan/14/ports <== ==> /proc/switch/eth0/vlan/13/ports <== ==> /proc/switch/eth0/vlan/12/ports <== ==> /proc/switch/eth0/vlan/11/ports <== ==> /proc/switch/eth0/vlan/10/ports <== ==> /proc/switch/eth0/vlan/9/ports <== ==> /proc/switch/eth0/vlan/8/ports <== ==> /proc/switch/eth0/vlan/7/ports <== ==> /proc/switch/eth0/vlan/6/ports <== ==> /proc/switch/eth0/vlan/5/ports <== ==> /proc/switch/eth0/vlan/4/ports <== ==> /proc/switch/eth0/vlan/3/ports <== ==> /proc/switch/eth0/vlan/2/ports <== ==> /proc/switch/eth0/vlan/1/ports <== 4 5t ==> /proc/switch/eth0/vlan/0/ports <== 0 1 2 3 5t* ==> /proc/switch/eth0/version <== 0.02 ==> /proc/switch/eth0/driver <== bcm53xx ==> /proc/switch/eth0/reset <== b ==> /proc/switch/eth0/enable_vlan <== 1 ==> /proc/switch/eth0/enable <== 1 This output is exactly the same under my self-compiled versin and released version. > You are looking for which ports are tagged, and which are not. > And in which vlans the ports are configured. > > Vlan id 0 is a very nasty one, because it actually is only used to > tag l2 priority on your packets. Every normal switch will just > prioritize and strip the "tag" ;-). Aha! Could that also explain why the output of "tcpdump -i eth0 -n" magically changes (stops showing "vlan 0" prefix) when I do vconfig add eth0 0 ? Having a debug tool not show the real data that was received from network worries me. _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
