I finnaly managed to use vlan support on WRT160NL with the following config:

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   eth0.0
        option type     bridge
        option proto    static
        option ipaddr   192.168.2.1
        option netmask  255.255.255.0

config interface wan
        option ifname   eth1
        option proto    dhcp
        
config interface wan2
        option ifname   eth0.1
        option proto    dhcp

config switch
        option name     eth0
        option reset    1
        option enable_vlan 1

config switch_vlan
        option device   eth0
        option vlan     0
        option ports    "1 2 3 4*"
        
config switch_vlan
        option device   eth0
        option vlan     1
        option ports    "0 4t"


For what I tested I see two issues:

CPU port is 4 and not 5 as specified in
http://wiki.openwrt.org/doc/switch. This is terrible for anyone trying
to start.
Should this be implemented on a standard way? Or should I create a
table on wiki specifying the which port is which in different routers?

Exchanging 4* with 4t, i.e., putting the default vlan on the wan2
port, breaks both lan and wan2 interface. Any reason? I don't see
where the untagged traffic comes...

Regards,
-- 
+ Nuno Gonçalves
+ [email protected]
+ http://nunoassimassim.blogspot.com/
+ PORTUGAL
E-mail sent directly from Google Mail webmail using HTTPS on behalf of
Nuno João Pinto Gonçalves, birth date 1986-11-16. E-mail headers
provide good assurance that this message was not tampered and
originates from [email protected]. If you require additional security,
I may provide on request X509 electronic signature under Portuguese
government chain.
Se precisar de assinatura digital do Cartão de Cidadão, de uma apitadela.
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to