Is it normal for WAN to be tagged on every vlan? ETH4 and ETH5 reversed

Routers
1

Is it normal for WAN to be tagged on every vlan?
I create a new vlan and its tagged for the it..

Not sure if that should be happening.

Just noticed in a terminal. eth0 wan1, eth1 lan1, eth2 lan2, eth3 lan3. Those are all configured with a vlan interface eth0.1 eth0.5 extra.

problem.. eth4 shows my ISP IP( this is SFP+ LAN port). No Vlans on this one.
(is this just how the hardware is laid out to work?)
eth5 show as lan with all vlans.

Hopefully that makes some sense.

2

Can you share some screenshots or more easily parsed information?

3

Figured I’d provide an example from one of my routers just for you to compare to since I have a few VLANs configured as well:

root@HomeRouter:~# cat /etc/config/network 

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config device
	option name 'eth3'
	option mtu '1500'

config interface 'wan'
	option ifname 'eth3'
	option metric '200'
	option dns_metric '200'
	option proto 'dhcp'
	option norelease '1'
	option ipaddr 'xxx.xxx.xxx.xxx
	option peerdns '0'
	option dns '9.9.9.11 1.1.1.2'

config device
	option name 'eth4'
	option mtu '1500'

config interface 'wan2'
	option ifname 'eth4'
	option metric '201'
	option dns_metric '201'
	option proto 'dhcp'
	option norelease '1'
	option peerdns '1'

config device
	option type '8021q'
	option ifname 'eth2'
	option vid '4'
	option name 'eth2.4'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth1'
	option vid '4'
	option name 'eth1.4'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth0'
	option vid '4'
	option name 'eth0.4'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth5'
	option vid '4'
	option name 'eth5.4'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth2'
	option vid '10'
	option name 'eth2.10'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth1'
	option vid '10'
	option name 'eth1.10'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth0'
	option vid '10'
	option name 'eth0.10'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth5'
	option vid '10'
	option name 'eth5.10'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth2'
	option vid '100'
	option name 'eth2.100'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth1'
	option vid '100'
	option name 'eth1.100'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth0'
	option vid '100'
	option name 'eth0.100'
	option mtu '1500'

config device
	option type '8021q'
	option ifname 'eth5'
	option vid '100'
	option name 'eth5.100'
	option mtu '1500'

config device
	option name 'br-lan'
	option type 'bridge'
	option mtu '1500'
	option stp '0'
	option igmp_snooping '0'
	option multicast_querier '0'
	option ports 'eth2 eth1 eth0 eth5'
	option macaddr 'bc:b9:23:81:42:c4'

config interface 'lan'
	option ifname 'br-lan'
	option proto 'static'
	option ipaddr '192.168.10.1/24'
	option force_link '1'

config device
	option name 'br-lan_4'
	option type 'bridge'
	option mtu '1500'
	option stp '0'
	option igmp_snooping '0'
	option multicast_querier '0'
	option ports 'eth2.4 eth1.4 eth0.4 eth5.4'
	option macaddr 'bc:b9:23:81:42:c4'

config interface 'lan_4'
	option ifname 'br-lan_4'
	option proto 'static'
	option ipaddr '192.168.4.1/24'
	option force_link '1'

config device
	option name 'br-lan_10'
	option type 'bridge'
	option mtu '1500'
	option stp '0'
	option igmp_snooping '0'
	option multicast_querier '0'
	option ports 'eth2.10 eth1.10 eth0.10 eth5.10'
	option macaddr 'bc:b9:23:81:42:c4'

config interface 'lan_10'
	option ifname 'br-lan_10'
	option proto 'static'
	option ipaddr '10.87.7.0/24'
	option force_link '1'

config device
	option name 'br-lan_100'
	option type 'bridge'
	option mtu '1500'
	option stp '0'
	option igmp_snooping '0'
	option multicast_querier '0'
	option ports 'eth2.100 eth1.100 eth0.100 eth5.100'
	option macaddr 'bc:b9:23:81:42:c4'

config interface 'lan_100'
	option ifname 'br-lan_100'
	option proto 'static'
	option ipaddr '192.168.100.1/24'
	option force_link '1'

Assuming you ran the same command from the terminal, I don’t believe my WAN ports have any VLANs tagged on them whereas every LAN port does which I what I would expect.

I believe the internal port names from the terminal don’t necessarily match the port names in the UI or on the physical router. I seem to recall that due to some particulars of the chipset used in the Route10, the WAN ports are assigned to eth3 and eth4 internally.

4

It may be that the hardware layout is confusing, because it doesn’t map left-to-right from eth0 to eth5. For some performance considerations, IIRC, eth0 is actually L2.

5

Yeah, it’s a little confusing if you start poking around in the shell at first! Thanks mentioning the performance consideration bit, I had a vague memory of someone mentioning something like that at some point lol.

Otherwise I just figured I’d post the config of another router so @Bill_Ny would have something to compare to.

1 Like
6

Thanks for posting.. Mine looks very close to yours.

The hardware to name mapping is what is getting me. I think GUI reports it backwards.. Going to confirm this and submit a bug if I find that to be a problem.

Thanks again

7

question::: Is it a must to have all the VPN config. I am not using any vpn’s at this time.
Having them in config makes no sense.

8

The GUI doesn’t report anything backwards, because it doesn’t expose the interface names at all. You can check the mapping by using this tool: https://help.alta.inc/hc/en-us/articles/31118887370779-Route10-MAC-Addresses