Attach is the regs.
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
option type bridge
option proto static
option ipaddr 192.168.1.1
option netmask 255.255.255.0
config interface wan
option ifname eth0
option proto dhcp
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
>
regs
Description: Binary data
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
