Help with routing 2 VLAN's to the same Ethernet Port

fredmc · Nov 1, 2023

Hi,

I've posted a similar thread recently but it was moved and I never did receive any reply, so I'm trying again hoping for any help. As this question is independent of any ASUS model, I ask the mods to keep it in the general forum please.

I have an Asus router running Merlin latest firmware and with a manual configuration for my ISP's (Vodafone PT) IPTV settings:

Selected ISP Profile: manual setting
Internet: VID 100 / PRIO: 1
LAN Port 4: 101 / PRIO: 1
LAN Port 3: 105 / PRIO: 1

It's been running well for several years, but I'm about to renew my contract and the new TV Box requires both the IPTV VLAN (105) and the Internet VLAN (100).

How can I pass both VLAN's to the same ethernet port 3?

Thank you in advance for any help.

Jeffrey Young · Nov 1, 2023

Reliably, no easy way with Asus.

There are a number of forum posts that go into using custom scripts to setup various vlans on Merlin. You need to seek them out and review them.

To start with, you need to share what you are using for a router. If there is one thing that is consistent about Asus is their inconsistency between models on how the network is setup. Although this is getting better with newer models. Past that, I have ideas, but without knowing how the network is setup by Asus internally, I am of no help. Even then, I think you need to look at another router brand that can do vlans natively

Crimliar · Nov 1, 2023

@fredmc do you have a source for these requirements? I'm not doubting, but it does seem a very strange setup indeed!

fredmc · Nov 1, 2023

Hi and thank you for your help.

I'm not looking at creating or managing my own VLAN's - these are only my ISP settings. I have an ONT that receives the fiber, and the ONT is connected to my Asus router. To get access to the different services I must configure my ISP VLAN settings - in my case (Vodafone Portugal) the VLAN for Internet is 100, for IPTV is 105, and for the phone is 101. I just configure those on the IPTV page on the Asus Router.

I've read somewhere how to ssh the router and issue a couple of easy commands to open/route both VLAN's to the same ethernet port (in my case, port 3) but I can't find those instructions any more.

The router is an AX86U but I think the model is not important? I know I did it successfully some years ago on an AC68U. It is running latest Merlin 3004.388.4.

I have a simple network configuration with a separate guest wifi (managed with YazFi) for my IoT devices. Ethernet port 3 is only for the TV box and Ethernet port 4 is connected to a Linksys PAP2T for the phone service.

What I'm looking to do is to have both Internet (VLAN 100 from Vodafone) and IPTV (VLAN 105 from Vodafone) on ethrnet port 3.

Thanks.

fredmc · Nov 1, 2023

Crimliar said:
@fredmc do you have a source for these requirements? I'm not doubting, but it does seem a very strange setup indeed!

Hi @Crimliar, thanks for your help.

Not sure I understand "the source of these requirements"?

Basically, the new TV box needs internet access (the current one only needs the IPTV VLAN 105) and I need to open both VLANs on that Ethernet port for it to work.

Crimliar · Nov 1, 2023

"Source of these requirements?" where did the information come from!
Your internet data arriving at your router has the VLAN 100 removed at that WAN, and your data travelling to your ISP has VLAN 100 added at the WAN. If that weren't the case you'd have to tag the data to all your devices with VLAN 100.
Next is the bit I'm not sure of, and if anyone knows better please correct me! The IPTV VLAN is passed through the router, creating that virtual LAN that stretches from your ISP to your IPTV device. Depending on how it's set up, this doesn't prevent your IPTV device from also communicating with devices on your LAN and the Internet via packets that are not tagged (they get the internet VLAN tag when they hit the WAN). I would strongly suspect that you only need set up the one VLAN for the IPTV service, and that your TV Box will also quite happily connect to the internet like every other device on your LAN.
*Refrained from giving the history lesson on why IPTV and VLANs go hand in hand!

fredmc · Nov 1, 2023

Crimliar said:
"Source of these requirements?" where did the information come from!
Your internet data arriving at your router has the VLAN 100 removed at that WAN, and your data travelling to your ISP has VLAN 100 added at the WAN. If that weren't the case you'd have to tag the data to all your devices with VLAN 100.
Next is the bit I'm not sure of, and if anyone knows better please correct me! The IPTV VLAN is passed through the router, creating that virtual LAN that stretches from your ISP to your IPTV device. Depending on how it's set up, this doesn't prevent your IPTV device from also communicating with devices on your LAN and the Internet via packets that are not tagged (they get the internet VLAN tag when they hit the WAN). I would strongly suspect that you only need set up the one VLAN for the IPTV service, and that your TV Box will also quite happily connect to the internet like every other device on your LAN.
*Refrained from giving the history lesson on why IPTV and VLANs go hand in hand!

Thank you for your help once again.

Unfortunately, as the configuration is set now, the tv box does not have internet, only the TV services (the TV channels). Hence why I am trying to also tag the VLAN 100 to the port 3. Similarly, the port 4 also does not have internet, only access to the phone services.

I'm seeing this tutorial online:

He seems to only configure the VLAN 100 on the IPTV settings webpage, and creates the VLANs 101 and 105 using robocfg on an ssh terminal:

Code:

filipe@RT-AC66U:/tmp/home/root# vconfig add eth0 101
filipe@RT-AC66U:/tmp/home/root# vconfig add eth0 105


filipe@RT-AC66U:/tmp/home/root# ifconfig vlan101 up
filipe@RT-AC66U:/tmp/home/root# ifconfig vlan105 up

ilipe@RT-AC66U:/tmp/home/root# robocfg vlan 1 ports "1 2 3 8t"
filipe@RT-AC66U:/tmp/home/root# robocfg vlan 100 ports "0t 4t 8t"
filipe@RT-AC66U:/tmp/home/root# robocfg vlan 101 ports "0t 4t 8t"
filipe@RT-AC66U:/tmp/home/root# robocfg vlan 105 ports "0t 4t 8t"

For the little I get, this would tag all ports with all the VLANS while I only need to tag VLAN 100 to ethernet port 3 (in addition to the already tagged VLAN 105 in the IPTV settings page).

Also, I don't seem to have robocfg installed - how can i install it (or should i use nvram instead)? Am i on the right track?

Thanks in advance.

ColinTaylor · Nov 1, 2023

fredmc said:
The router is an AX86U but I think the model is not important?

Yes it is important. VLAN support works completely differently on the AX86U compared to the AC68U. As far as I know there's no way of doing what you're asking using SSH on the AX86U.

Does the Vodafone(Portugal) preset not work for you?

Jeffrey Young · Nov 1, 2023

fredmc said:
Thank you for your help once again.

Unfortunately, as the configuration is set now, the tv box does not have internet, only the TV services (the TV channels). Hence why I am trying to also tag the VLAN 100 to the port 3. Similarly, the port 4 also does not have internet, only access to the phone services.

I'm seeing this tutorial online:

He seems to only configure the VLAN 100 on the IPTV settings webpage, and creates the VLANs 101 and 105 using robocfg on an ssh terminal:

Code:

filipe@RT-AC66U:/tmp/home/root# vconfig add eth0 101 filipe@RT-AC66U:/tmp/home/root# vconfig add eth0 105 filipe@RT-AC66U:/tmp/home/root# ifconfig vlan101 up filipe@RT-AC66U:/tmp/home/root# ifconfig vlan105 up ilipe@RT-AC66U:/tmp/home/root# robocfg vlan 1 ports "1 2 3 8t" filipe@RT-AC66U:/tmp/home/root# robocfg vlan 100 ports "0t 4t 8t" filipe@RT-AC66U:/tmp/home/root# robocfg vlan 101 ports "0t 4t 8t" filipe@RT-AC66U:/tmp/home/root# robocfg vlan 105 ports "0t 4t 8t"

For the little I get, this would tag all ports with all the VLANS while I only need to tag VLAN 100 to ethernet port 3 (in addition to the already tagged VLAN 105 in the IPTV settings page).

Also, I don't seem to have robocfg installed - how can i install it (or should i use nvram instead)? Am i on the right track?

Thanks in advance.

As @ColinTaylor pointed out, the commands you are referring to are for the older AC68U. They won't work on the newer routers. I've never played around much with the IPTV stuff in the router, so I don't know how the router sets things up internally when using IPTV (does it create any bridges, how are the routes done, etc. etc.). Sorry that I can't be of any more help on this.

Jeffrey Young · Nov 1, 2023

OK, so this is a bit a shot in the dark. From what I read, IPTV creates a new bridge br101. In that bridge is the eth0.v0, which is your WAN VLAN tag, eth1.v0, which is your LAN4 VLAN tag and eth2.v0, which is your LAN3 VLAN tag.

So, you might be able to create the VLAN tagged interface that you need to add;

Code:

ip link add link eth2 name eth2.100 type vlan id 100
ip link set dev eth2.100 up

Then add it to the br101 bridge

Bash:

brctl addif br101 eth2.100

If this works, and it would be a big IF, you can script it into the proper startup script later. I would not do it now until you test it manually in case you lock yourself out.

To be honest though, I never seen the application you are explaining. Are both VLANs required (one for the TV channels and one so the smart TV can access the internet?) If so, that does not make sense to me. The internet should already be on that port.

fredmc · Nov 2, 2023

ColinTaylor said:
Yes it is important. VLAN support works completely differently on the AX86U compared to the AC68U. As far as I know there's no way of doing what you're asking using SSH on the AX86U.

Does the Vodafone(Portugal) preset not work for you?
View attachment 53915

Unfortunately not - this was made to have port 4 in bridge mode so the vodafone router could also be connected and take care of IPTV and phone. Unfortunately Vodafone Portugal stopped giving 2 ip's per installation years ago and this method became obsolete.

Currently it's working fine with the manual configuration adding the IPTV VLAN (105) to port 3, and the phone VLAN (101) to port 4, but each port only receives that VLAN and not the 100 VLAN that has internet access - and that is what I need for the new shiny 4k TV box from vodafone.

fredmc · Nov 2, 2023

Jeffrey Young said:
OK, so this is a bit a shot in the dark. From what I read, IPTV creates a new bridge br101. In that bridge is the eth0.v0, which is your WAN VLAN tag, eth1.v0, which is your LAN4 VLAN tag and eth2.v0, which is your LAN3 VLAN tag.

So, you might be able to create the VLAN tagged interface that you need to add;

Code:

ip link add link eth2 name eth2.100 type vlan id 100

Then add it to the br101 bridge

Bash:

brctl addif br101 eth2.100

If this works, and it would be a big IF, you can script it into the proper startup script later. I would not do it now until you test it manually in case you lock yourself out.

To be honest though, I never seen the application you are explaining. Are both VLANs required (one for the TV channels and one so the smart TV can access the internet?) If so, that does not make sense to me. The internet should already be on that port.

This is awesome. Thank you for your help and for this. I will try it later and will let you know. If it does work I may need some help with the startup script.

Thanks!

fredmc · Nov 2, 2023

If it helps, this is the current ifconfig for my network:

Code:

ASUSWRT-Merlin RT-AX86U 3004.388.4_0 Mon Aug 21 19:34:20 UTC 2023


user@ASUSWRT:/tmp/home/root# ifconfig


br0       Link encap:Ethernet  HWaddr FB:34:98:8C:21:71 


          inet addr:172.37.0.1  Bcast:172.37.0.255  Mask:255.255.255.0


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:67847703 errors:0 dropped:298455 overruns:0 frame:0


          TX packets:181063383 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:11173115260 (10.4 GiB)  TX bytes:205869208177 (191.7 GiB)






br101     Link encap:Ethernet  HWaddr 10:7C:45:E2:80:C1 


          inet addr:77.54.226.57  Bcast:77.54.226.255  Mask:255.255.224.0


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:1088639659 errors:0 dropped:0 overruns:0 frame:0


          TX packets:41853755 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:1427155376378 (1.2 TiB)  TX bytes:8141470947 (7.5 GiB)






eth0      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70 


          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1


          RX packets:1151401747 errors:0 dropped:0 overruns:0 frame:0


          TX packets:52242377 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:1552641843887 (1.4 TiB)  TX bytes:9651311986 (8.9 GiB)






eth0.v0   Link encap:Ethernet  HWaddr FC:35:97:8C:23:70 


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:1151379663 errors:0 dropped:0 overruns:0 frame:0


          TX packets:51659440 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:1522682107881 (1.3 TiB)  TX bytes:9364092600 (8.7 GiB)






eth1      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70 


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:54096 errors:0 dropped:1 overruns:0 frame:0


          TX packets:991819705 errors:30848 dropped:0 overruns:0 carrier:0


          collisions:41425 txqueuelen:1000


          RX bytes:15478715 (14.7 MiB)  TX bytes:1328849548299 (1.2 TiB)






eth1.v0   Link encap:Ethernet  HWaddr FC:35:97:8C:23:70 


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:54095 errors:0 dropped:0 overruns:0 frame:0


          TX packets:991669694 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:14511691 (13.8 MiB)  TX bytes:1324837306000 (1.2 TiB)






eth2      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70 


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:284386 errors:0 dropped:7 overruns:0 frame:0


          TX packets:10436284 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:21865089 (20.8 MiB)  TX bytes:14307026763 (13.3 GiB)






eth2.v0   Link encap:Ethernet  HWaddr FC:35:97:8C:23:70 


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:9227693 errors:0 dropped:0 overruns:0 frame:0


          TX packets:1049796959 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:909735512 (867.5 MiB)  TX bytes:1412707528013 (1.2 TiB)






eth3      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70 


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:42344603 errors:0 dropped:31 overruns:0 frame:0


          TX packets:69384621 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:13201402988 (12.2 GiB)  TX bytes:64557111564 (60.1 GiB)






eth4      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70 


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:25409333 errors:0 dropped:568 overruns:0 frame:0


          TX packets:49425456 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:5155332070 (4.8 GiB)  TX bytes:45807827950 (42.6 GiB)






eth5      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70 


          UP BROADCAST ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:0 errors:0 dropped:0 overruns:0 frame:0


          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)






eth6      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70 


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:2095100 errors:0 dropped:0 overruns:0 frame:40259240


          TX packets:6125864 errors:4422 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:1254909673 (1.1 GiB)  TX bytes:2099978054 (1.9 GiB)


          Interrupt:48






eth7      Link encap:Ethernet  HWaddr FC:35:97:8C:21:72 


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:46584112 errors:0 dropped:21 overruns:0 frame:0


          TX packets:41706295 errors:0 dropped:5388 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:8105336387 (7.5 GiB)  TX bytes:28863553641 (26.8 GiB)






lo        Link encap:Local Loopback 


          inet addr:127.0.0.1  Mask:255.0.0.0


          UP LOOPBACK RUNNING MULTICAST  MTU:65536  Metric:1


          RX packets:24697834 errors:0 dropped:0 overruns:0 frame:0


          TX packets:24697834 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:6228557828 (5.8 GiB)  TX bytes:6228557828 (5.8 GiB)






lo:0      Link encap:Local Loopback 


          inet addr:127.0.1.1  Mask:255.0.0.0


          UP LOOPBACK RUNNING MULTICAST  MTU:65536  Metric:1






spu_ds_dummy Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 


          UP RUNNING NOARP  MTU:1500  Metric:1


          RX packets:0 errors:0 dropped:0 overruns:0 frame:0


          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:100


          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)






spu_us_dummy Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 


          UP RUNNING NOARP  MTU:1500  Metric:1


          RX packets:0 errors:0 dropped:0 overruns:0 frame:0


          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:100


          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)






tun21     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 


          inet addr:10.8.0.1  P-t-P:10.8.0.1  Mask:255.255.255.0


          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1


          RX packets:0 errors:0 dropped:0 overruns:0 frame:0


          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)






wl0.2     Link encap:Ethernet  HWaddr FC:34:97:8C:21:32 


          inet addr:172.40.100.1  Bcast:172.30.100.255  Mask:255.255.255.0


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:12350855 errors:0 dropped:0 overruns:0 frame:40259240


          TX packets:2365987 errors:47475 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:2079384117 (1.9 GiB)  TX bytes:463289803 (441.8 MiB)

Thanks

Jeffrey Young · Nov 2, 2023

The output of brctl show will also help.

ColinTaylor · Nov 2, 2023

@fredmc Is there a reason you are using a T-Mobile public IP address range (172.37.0.0/24) for your LAN (br0)?

fredmc · Nov 2, 2023

Jeffrey Young said:
The output of brctl show will also help.

Code:

user@ASUSWRT:/tmp/home/root# brctl show


bridge name    bridge id        STP enabled    interfaces


br0        8000.fc34978b2170    yes        eth3


                            eth4


                            eth5


                            eth6


                            eth7


                            wl0.2


br101        8000.107b44e290c2    yes        eth0.v0


                            eth1.v0


                            eth2.v0

Thank you.

fredmc · Nov 2, 2023

ColinTaylor said:
@fredmc Is there a reason you are using a T-Mobile public IP address range (172.37.0.0/24) for your LAN (br0)?

Hi, yeah, just ignore... I've changed ip's and mac add's on my post.

Jeffrey Young · Nov 2, 2023

fredmc said:

Code:

user@ASUSWRT:/tmp/home/root# brctl show


bridge name    bridge id        STP enabled    interfaces


br0        8000.fc34978b2170    yes        eth3


                            eth4


                            eth5


                            eth6


                            eth7


                            wl0.2


br101        8000.107b44e290c2    yes        eth0.v0


                            eth1.v0


                            eth2.v0

Thank you.

Thanks. I edited my suggested fix for your issue. I added a command to bring the interface up. Not entirely certain that it is needed, but I put it in just in case.

fredmc · Nov 5, 2023

Jeffrey Young said:
Thanks. I edited my suggested fix for your issue. I added a command to bring the interface up. Not entirely certain that it is needed, but I put it in just in case.

Thanks a lot for your help!

Unfortunately it doesn't seem to work. This is my ifconfig and brctl after issuing the commands:

Code:

user@ASUSWRT:/tmp/home/root# ifconfig


br0       Link encap:Ethernet  HWaddr FB:34:98:8C:21:71


          inet addr:172.27.0.1  Bcast:172.27.0.255  Mask:255.255.255.0


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:3316919 errors:0 dropped:18727 overruns:0 frame:0


          TX packets:4154860 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:515291300 (491.4 MiB)  TX bytes:3547331497 (3.3 GiB)






br101     Link encap:Ethernet  HWaddr 10:7C:45:E2:80:C1


          inet addr:77.54.226.57  Bcast:77.54.226.255  Mask:255.255.224.0


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:74806588 errors:0 dropped:0 overruns:0 frame:0


          TX packets:1698184 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:98294544072 (91.5 GiB)  TX bytes:320944521 (306.0 MiB)






eth0      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70


          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1


          RX packets:79776481 errors:0 dropped:0 overruns:0 frame:0


          TX packets:2503730 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:107333774355 (99.9 GiB)  TX bytes:418585235 (399.1 MiB)






eth0.v0   Link encap:Ethernet  HWaddr FC:35:97:8C:23:70


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:79772125 errors:0 dropped:0 overruns:0 frame:0


          TX packets:2466956 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:105861302291 (98.5 GiB)  TX bytes:404370419 (385.6 MiB)






eth1      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:300 errors:0 dropped:3 overruns:0 frame:0


          TX packets:71926575 errors:885 dropped:0 overruns:0 carrier:0


          collisions:1044 txqueuelen:1000


          RX bytes:96136 (93.8 KiB)  TX bytes:96560128391 (89.9 GiB)






eth1.v0   Link encap:Ethernet  HWaddr FC:35:97:8C:23:70


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:297 errors:0 dropped:0 overruns:0 frame:0


          TX packets:71916817 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:90232 (88.1 KiB)  TX bytes:96269501087 (89.6 GiB)






eth2      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:700527 errors:0 dropped:7 overruns:0 frame:0


          TX packets:73434261 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:75495542 (71.9 MiB)  TX bytes:99406527287 (92.5 GiB)






eth2.100  Link encap:Ethernet  HWaddr FC:35:97:8C:23:70


          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1


          RX packets:0 errors:0 dropped:0 overruns:0 frame:0


          TX packets:3397 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:0 (0.0 B)  TX bytes:4508413 (4.2 MiB)






eth2.v0   Link encap:Ethernet  HWaddr FC:35:97:8C:23:70


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:735179 errors:0 dropped:0 overruns:0 frame:0


          TX packets:76421997 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:66877658 (63.7 MiB)  TX bytes:103140875111 (96.0 GiB)






eth3      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:2286334 errors:0 dropped:20 overruns:0 frame:0


          TX packets:3656193 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:432580235 (412.5 MiB)  TX bytes:2967647577 (2.7 GiB)






eth4      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:1162019 errors:0 dropped:17 overruns:0 frame:0


          TX packets:1382502 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:225943035 (215.4 MiB)  TX bytes:505402382 (481.9 MiB)






eth5      Link encap:Ethernet  HWaddr FFC:35:97:8C:23:70


          UP BROADCAST ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:0 errors:0 dropped:0 overruns:0 frame:0


          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)






eth6      Link encap:Ethernet  HWaddr FC:35:97:8C:23:70


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:90162 errors:0 dropped:0 overruns:0 frame:2613006


          TX packets:419290 errors:204 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:40646908 (38.7 MiB)  TX bytes:167037437 (159.2 MiB)


          Interrupt:48






eth7      Link encap:Ethernet  HWaddr FC:35:97:8C:21:72


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:1546816 errors:0 dropped:21 overruns:0 frame:0


          TX packets:1646695 errors:0 dropped:1375 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:240829959 (229.6 MiB)  TX bytes:530524412 (505.9 MiB)






lo        Link encap:Local Loopback


          inet addr:127.0.0.1  Mask:255.0.0.0


          UP LOOPBACK RUNNING MULTICAST  MTU:65536  Metric:1


          RX packets:1534371 errors:0 dropped:0 overruns:0 frame:0


          TX packets:1534371 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:0


          RX bytes:384365170 (366.5 MiB)  TX bytes:384365170 (366.5 MiB)






lo:0      Link encap:Local Loopback


          inet addr:127.0.1.1  Mask:255.0.0.0


          UP LOOPBACK RUNNING MULTICAST  MTU:65536  Metric:1






spu_ds_dummy Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00


          UP RUNNING NOARP  MTU:1500  Metric:1


          RX packets:0 errors:0 dropped:0 overruns:0 frame:0


          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:100


          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)






spu_us_dummy Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00


          UP RUNNING NOARP  MTU:1500  Metric:1


          RX packets:0 errors:0 dropped:0 overruns:0 frame:0


          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:100


          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)






tun21     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00


          inet addr:10.8.0.1  P-t-P:10.8.0.1  Mask:255.255.255.0


          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1


          RX packets:0 errors:0 dropped:0 overruns:0 frame:0


          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)






wl0.2     Link encap:Ethernet  HWaddr FC:35:97:8C:21:72


          inet addr:172.40.100.1  Bcast:172.40.100.255  Mask:255.255.255.0


          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1


          RX packets:804742 errors:0 dropped:0 overruns:0 frame:2613006


          TX packets:172752 errors:683 dropped:0 overruns:0 carrier:0


          collisions:0 txqueuelen:1000


          RX bytes:135273334 (129.0 MiB)  TX bytes:31091968 (29.6 MiB)














user@ASUSWRT:/tmp/home/root# brctl show


bridge name    bridge id        STP enabled    interfaces


br0        8000.fc34978b2170    yes        eth3


                            eth4


                            eth5


                            eth6


                            eth7


                            wl0.2


br101        8000.107b44e290c2    yes        eth0.v0


                            eth1.v0


                            eth2.100


                            eth2.v0

I was planning to try it using the netflix channel that they used to have on the TV Box but I just noticed that they removed all content that required internet access from this Box.

After issuing the commands there is no interruption on the TV signal. I re-started the box but there is no change of ip address on the box (it's still the ip addrees associated to the TV services network), and the TV Box doesn't show on the DHCP clients (I remember on the old AC68U it appeared on the client's list once the internet VLAN was added). I also tried connecting a laptop to port 3 and it recognizes the "unknown" network but it doesn't have internet access.

If you have any other ideas I could try it would be most helpful. And thank you so much for all your help so far.

fredmc · Nov 5, 2023

Jeffrey Young said:
To be honest though, I never seen the application you are explaining. Are both VLANs required (one for the TV channels and one so the smart TV can access the internet?) If so, that does not make sense to me. The internet should already be on that port.

Yes, many things in Vodafone Portugal do not make any sense. If you have a new installation, you are given an all-in-one router+ont and you are unable to put it in bridge mode (to use your own router) without paying an extra fee. Fortunately, I'm an old client and I still have the old devices with a separate ONT that I can connect directly to my Asus router. Plus, I still pay almost the same i used to pay a decade ago (which is a very significant discount on today prices).

They provide three different services - internet, tv and home phone. They have this services on different VLAN's - each VLAN has it own separate network carrying only each service: VLAN 100 for internet, VLAN 101 for VoIP, and VLAN 105 for IPTV. Their own router is configured to assign the VLAN's to the ports, and they have both TV and internet (105 and 100) on a specific Ethernet port to which you connect the TV box. Unfortunately, with ASUS, I seem to only be able to assign 1 VLAN to an Ethernet port on the IPTV settings page - and when I assign it, it doesn't carry the VLAN 100 for internet (if I clear all values from "LAN Port 3" it has internet access but no access to VLAN 105 that is required for the TV services).

Hope this makes it a bit clearer. ASUS should really update their settings for "Vodafone Portugal" as their current settings have been useless for years since Vodafone stopped giving 2 ip's per installation (maybe 5 years ago??). The new correct settings should have IPTV STB Port carrying both VLAN 100 and VLAN 105 on port 3, and VoIP Services carrying VLAN 101 on port 4.

Thanks for your help.

Thread starter	Title	Forum	Replies	Date
G	[Help] Routing VPN server through VPN client (external VPN Provider)	Asuswrt-Merlin	14	Dec 27, 2023
L	Help with some routing/filtering configuration for CUPS printers in Debian linux	Asuswrt-Merlin	2	Aug 19, 2023
	Need help with OpenVPN server configured in non-routing mode	Asuswrt-Merlin	1	Jun 28, 2023
C	Solved Need help with nat-start scripts	Asuswrt-Merlin	3	Wednesday at 2:31 AM
G	Need help with VPN	Asuswrt-Merlin	2	Tuesday at 9:07 AM
P	Help with traffic filtering	Asuswrt-Merlin	0	Apr 19, 2024
C	Need some help with a DHCP problem	Asuswrt-Merlin	9	Apr 14, 2024
S	Help Required AC68U (TM-AC1900) troubleshooting after power outage	Asuswrt-Merlin	3	Apr 9, 2024
C	Need help with GT-AXE11000 and DNS Director	Asuswrt-Merlin	0	Apr 5, 2024
	need help with network loop.	Asuswrt-Merlin	9	Apr 1, 2024

Help with routing 2 VLAN's to the same Ethernet Port

Occasional Visitor

Very Senior Member

Very Senior Member

Occasional Visitor

Occasional Visitor

Very Senior Member

Occasional Visitor

Part of the Furniture

Very Senior Member

Very Senior Member

Occasional Visitor

Occasional Visitor

Occasional Visitor

Very Senior Member

Part of the Furniture

Occasional Visitor

Occasional Visitor

Very Senior Member

Occasional Visitor

Occasional Visitor

Similar threads

Similar threads

Sign Up For SNBForums Daily Digest