On Sat, Nov 21, 2009 at 04:01:30PM +0200, Timo Juhani Lindfors wrote: > but noticed that all arp replies come back prefixed with "vlan 0, p > 0," according to tcpdump. After some googling I was able to figure > out that with 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?
> > modprobe 8021q > vconfig eth0 0 > ip addr add 192.168.1.5/24 dev eth0.0 > ip link set eth0.0 up > ping 192.168.1.1 > > I can connect to the router. Any idea how I could configure the router > to not encapsulate all traffic inside vlan 0? > > r...@openwrt:/etc/config# cat network > #### VLAN configuration > 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 connected differently. I've got labels on all my 5 wrt's to indicate which is which on that specific model ;-). 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. 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" ;-). -- .signature not found _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
