Posted: Tue Mar 09, 2021 18:17 Post subject: Another VLAN Tagging/Trunking Thread C7 Gateway - WR1043 WAP
Hello,
I think I stuck on the last 10% to get trunking on my home network running.
Current configuration:
gateway: Archer C7 V4 r44406
currently there are running 4 networks on this router
Home LAN/Wifi VLAN1
Home VPN Wifi VLAN3
Guest Wifi VLAN4
all bridges and DHCHPs setup and working on this device
VAP: TP Link 1043 OpenWrt 19.07.4 r11208
connected to Home LAN and distributes Home Wifi
Target configuration:
My target is to trunk/tagg all 4 networks to the VAP and distribute all 4 Wifis on the VAP
Question 1: how do I create more than 4 VLANs in the WEB UI?
Question 2: how is the trunk Port defined in the Web UI?
Question 3: does the dropdown menu "assign to Bridge" in "Setup/Switch Config" section assign to a brigde, but to which on? tbh, this drop down menue makes no visible sense for me, can anyone explain this to me?
unfortunately I found no proper guide or forum thread were these questions are answered.
BTW, is there a good reason why the wiki is pretty much outdated and the forum is almost the only source were to get information? I think you guys often do get the similar questions because of the lack of a better information source... _________________ VLANs, Wireguard Site to Site, OpenVPN Client, WDS
TP-Link Archer C7 V4, V5
TP-Link Archer A7 V5
TP-Link WR1043 V4
Unifi UAP-AC-M
Last edited by tomron on Mon Mar 22, 2021 14:07; edited 1 time in total
I'll tell you what I tell everyone about VLANs w/ dd-wrt.
VLANs are hardware dependent, and as such, questions need to be asked in the relevant forum for your router's chipset (TP-Link is typically Qualcomm/Atheros). Each chipset has its own way of handling it. For example, in the case of Atheros (iirc), it uses its own switch utility called swconfig.
That's why VLAN (re)configuration rarely works using the GUI. It was originally designed for Broadcom routers, specifically the now ancient Linksys WRT54G series. As other brands w/ other chipsets got support from dd-wrt, little to no effort was made to keep the VLANs portion of the GUI compatible. It just fell by the wayside. And that's why nearly all VLAN support requires scripting and the CLI.
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Wed Mar 10, 2021 3:33 Post subject:
Topic moved. Usually, the only gripes I've seen about moving topics from Advanced Networking is due to them being about Broadcom hardware, since the rest use swconfig and associated CLI commands AFAIK, so I didn't move this one before _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
OK thanks, didn't know that vlans are that device specific and the gui isn't really usable. I will study the cli commands and sort it then out.
Would it then not be a good idea to place that information into the help section of this configuration page? Unfortunately the help section is completely empty and gives no clue how to handle vlans, which then results in countless threads how to configure vlans by the web ui... I mean it's just workload for the forum mods which could be mostly avoided. _________________ VLANs, Wireguard Site to Site, OpenVPN Client, WDS
TP-Link Archer C7 V4, V5
TP-Link Archer A7 V5
TP-Link WR1043 V4
Unifi UAP-AC-M
The wired ports shall not be tagged. Is that correct?
The chip supports VLAN up to 127 only.
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 1 set ports "0t 3 4 5"
swconfig dev switch0 vlan 2 set ports "0t 1"
swconfig dev switch0 vlan 4 set ports "0t 2"
swconfig dev switch0 vlan 5 set ports "0t 5"
swconfig dev switch0 set apply
vconfig add eth1 4
vconfig add eth1 5
Note: Check that the interface is eth1.
is this still true that VLANs are limited up to 127?
