Don't think that VLAN tagging is working.
TCP dump results are shown below:
# tcpdump -eni eth2
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
19:00:21.462159 00:15:6d:c3:81:b1 > ff:ff:ff:ff:ff:ff, ethertype ARP
(0x0806), length 60: arp who-has 192.168.1.2 tell 192.168.1.1
19:00:21.462586 00:02:a5:4e:93:d9 > 00:15:6d:c3:81:b1, ethertype ARP
(0x0806), length 42: arp reply 192.168.1.2 is-at 00:02:a5:4e:93:d9
19:00:21.462231 00:15:6d:c3:81:b1 > 00:02:a5:4e:93:d9, ethertype IPv4
(0x0800), length 98: 192.168.1.1 > 192.168.1.2: ICMP echo request, id 1331,
seq 0, length 64
19:00:21.462253 00:02:a5:4e:93:d9 > 00:15:6d:c3:81:b1, ethertype IPv4
(0x0800), length 98: 192.168.1.2 > 192.168.1.1: ICMP echo reply, id 1331,
seq 0, length 64
19:00:22.456433 00:15:6d:c3:81:b1 > 00:02:a5:4e:93:d9, ethertype IPv4
(0x0800), length 98: 192.168.1.1 > 192.168.1.2: ICMP echo request, id 1331,
seq 1, length 64
19:00:22.456453 00:02:a5:4e:93:d9 > 00:15:6d:c3:81:b1, ethertype IPv4
(0x0800), length 98: 192.168.1.2 > 192.168.1.1: ICMP echo reply, id 1331,
seq 1, length 64
config 'interface' 'loopback'
option 'ifname' 'lo'
option 'proto' 'static'
option 'ipaddr' '127.0.0.1'
option 'netmask' '255.0.0.0'
config 'interface' 'lan'
option 'ifname' 'eth1.1'
option 'proto' 'static'
option 'ipaddr' '192.168.1.1'
option 'netmask' '255.255.255.0'
config 'interface' 'wan'
option 'ifname' 'eth0'
option 'proto' 'dhcp'
config 'alias'
option 'interface' 'wan'
option 'proto' 'static'
option 'ipaddr' '1.1.1.20'
option 'netmask' '255.255.255.0'
config 'switch'
option 'name' 'eth1'
option 'reset' '1'
option 'enable_vlan' '1'
option 'enable' '1'
config 'switch_vlan'
option 'device' 'eth1'
option 'vlan' '1'
option 'vid' '1'
option 'ports' '0t 1t 2t 3t 4t 5t'
On Fri, Apr 1, 2011 at 4:59 PM, Peter Lebbing <pe...@digitalbrains.com>wrote:
> On -10/01/37 20:59, Yeoh Chun Yeow wrote:
> > It seems that ADM6996FC is different from ADM6996M. How to ensure the
> > port get tagged? Is this by simply modifying Configuration register Bit
> 4?
>
> It's a lot more involved on the M model. A whole bunch of bits need to be
> changed before it works as one would expect. Okay, perhaps as I would
> expect.
>
> > 2. VLAN separation is alright but VLAN tagging is not working. I
> > am using the following:
> >
> > config 'switch'
> > option 'name' 'eth1'
> > option 'reset' '1'
>
> This is a point for the documentation to be written: the ADM6996 appears to
> have
> no possibility to reset. The "reset" swconfig option is a no-op.
>
> > option 'enable_vlan' '1'
> > option 'enable' '1'
> >
> > config 'switch_vlan'
> > option 'device' 'eth1'
> > option 'vlan' '1'
> > option 'vid' '1'
> > option 'ports' '0t 1t 5t'
> >
> > Tag and No Tag on the port, I am still able to PING a host
> > without VLAN tagging. It means that the VLAN tagging is not
> working.
>
> I just did a quick test, and it confirmed my suspicion. At least Windows 7
> couldn't care less if incoming packets are VLAN tagged, it processes them
> equally to untagged packets. I can ping fine from a switch port that only
> sends
> tagged packets to the Windows box.
>
> Not unexpected, my Linux box is more picky and drops VLAN tagged packets
> when
> VLANs aren't configured.
>
> So it depends on the OS you use to test. On a Linux box, you can get a lot
> more
> info with, for example:
>
> # tcpdump -eni eth0
>
> The -e argument says to print the link-level header. Without it, tcpdump
> won't
> give an indication that the incoming packet is VLAN tagged.
>
> Furthermore, watch out that the numbering printed beneath the ports on your
> router doesn't necessarily correspond to the numbering in the switch chip.
> On my
> router, the port labeled "LAN 1" is connected to switch port 3, for
> example.
>
> HTH,
>
> Peter.
>
> --
> I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
> You can send me encrypted mail if you want some privacy.
> My key is available at http://wwwhome.cs.utwente.nl/~lebbing/pubkey.txt
>
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
