[N1GKn]

Hi all,

I installed Firmware: DD-WRT v3.0-r47911 on a TP-Link Ac1750 v5 and I configured the vlan tagging as showed in the attachment but I am not able to use the router connected directly to the ONT.

Could you help me to understand how I can configure the vlan tagging to use the router as third party router?

Thank you very much

[egc]

VLAN's are router/platform specific (it is understandable you do not know that)

I will transfer this thread to the appropriate forum for you

[N1GKn]

Thank you egc and sorry, I'm new in this forum but I completely used the wrong section.

I'm sorry

[egc]

No problem we are here to help

To get the best out of DDWRT and the forum read the forum guidelines full of helpful pointers:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087

I am sure one of our VLAN experts will chime in although " 'Twas the night before Christmas... "

[kernel-panic69]

You're trying to tag VLAN 0 on the networking page; I would have to see if that is a display error or correct, but I think you have to tag VLAN 2. As I found out, you have to add VLAN 1 and VLAN 2 and then tag the proper VLAN, most likely. @egc: I think that should be selectable on add instead of starting at 0 and requiring unnecessary adds the way it does.

[egc]

Maybe it works like this, if you add the vlan interface to eth0 you get interface eth0.0?

But confusing it is, one of these days someone has got to get to the bottom of this and write a wiki

[kernel-panic69]

It seems to me that something changed here, I don't recall it being this way before, and I am not about to dial up every router in the wild that requires this to check it. I could've sworn this defaulted to the WAN interface before or there was a selectable option of which vlan to tag.

[Per Yngve Berg]

Check the config in CLI

swconfig dev switch0 show

[N1GKn]

Hi guys, thank you for answering.

Yes it is very confusing and a wiki would be perfect to better understand.

I'm honest, the DD-WRT build on this TP-Link is not very stable, sometimes it shows to me the "Switch" tab other time not.

Anyway I think that the correct way to set the VLAN tagging is in network. The real problem is that when I go on basic setup, sometimes a new sqare to flag saying "enable VLAN Tagging" compares but other time for example refreshing the page, I don't have the square to flag. It is very stressful.

I have also read on this https://wiki.dd-wrt.com/wiki/index.php/VLAN_Support:
Only Broadcom based devices support port-based VLAN's, no Atheros or Ralink devices. Non-Broadcom platforms support 802.1q VLAN tagging via the Networking page options (Linux's vconfig utility is used internally for this) but it often does not work correctly and it is for tagging entire interfaces (the LAN ports are all one interface on these platforms).

This is the output:

[Per Yngve Berg]

Your wan is tagged with vlan 2. Remove the tagging in Networking and put in startup script:

swconfig dev switch0 vlan 2 set vid 201
swconfig dev switch0 set apply

As port 0 is also tagged, it probably be wrong in the other end. Then select the new interface eth.201 as wan in networking.

[N1GKn]

Done as you suggested and I get this:

[kernel-panic69]

[Per Yngve Berg]

swconfig commands are not persistent. They have to be re-done after a restart.

That's why we put them in the startup script.

[N1GKn]

Hi,
finally solved.