Posted: Tue Feb 13, 2018 6:24 Post subject: ac1450 kong's build vlan tagging question
I am kong's firmware for ac1450. I want to set port 3 to use vlan 3 and vlan1. Vlan1 and vlan3 will have different subnet. I connected with ubquiti unifi ac pro, and have one guest network to use vlan 3, it works fine. However, when I try to connect my macbook ethernet port to the switch, the macbook can't get ip. Anything I did wrong?
I've found the GUI to be mostly useless for 802.1q (vlan tagging/trunk port assignment). You need to set vlan data via cmd line. I roughly followed this to get vlans working properly on my R7000s: https://www.dd-wrt.com/wiki/index.php/Switched_Ports
I've found the GUI to be mostly useless for 802.1q (vlan tagging/trunk port assignment). You need to set vlan data via cmd line. I roughly followed this to get vlans working properly on my R7000s: https://www.dd-wrt.com/wiki/index.php/Switched_Ports
I've found the GUI to be mostly useless for 802.1q (vlan tagging/trunk port assignment). You need to set vlan data via cmd line. I roughly followed this to get vlans working properly on my R7000s: https://www.dd-wrt.com/wiki/index.php/Switched_Ports
THanks, I will try it
The nvram set doesn't work for me
Here is what I did
This is the original settings
root@DD-WRT:~# nvram show | grep vlan.*ports
size: 45247 bytes (20289 left)
vlan2ports=4 5u
vlan1ports=3 2 1 0 5*
root@DD-WRT:~# nvram show | grep port.*vlans
size: 45247 bytes (20289 left)
port5vlans=1 2 16
port3vlans=1 18 19 21
port1vlans=1 18 19 21
port4vlans=1 18 19 21
port2vlans=1 18 19 21
port0vlans=2 18 19 21
root@DD-WRT:~# nvram show | grep vlan.*hwname
size: 45247 bytes (20289 left)
vlan2hwname=et0
vlan1hwname=et0
I entered these commands
root@DD-WRT:~# nvram set 'vlan3ports=3t 5u'
root@DD-WRT:~# nvram set 'port3vlans=1 3 16 18 19 21'
root@DD-WRT:~# nvram set 'vlan3hwname=et0'
Same result as what I did in the web gui, I did try to use nvram set 'vlan3ports=3t 5' instead of nvram set 'vlan3ports=3t 5u', no luck.
When I plug the macbook to the switches that connected to port3, no luck. But the unifi ap is working. Not sure what happened. Does my computer/wired devices need some hardware requirement?