Posted: Sat Sep 05, 2020 8:12 Post subject: Help setting up port#vlans
I have been trying to set up the VLANs on my DD-WRT AP and I am having the following issue.
I followed this article Switched_Ports in order to set up the vlan#ports and vlan#hwname & port#vlans. However, after doing a nvram commit; & then reboot, the port#vlans reset back. They even lose the 18 19 21 (which indicate auto-negotiate, gigabit ports)
Here's the list of commands that I went thru:
Why does the port#vlans get reset? How would I set this up?
Note: I use my DD-WRT only in AP mode. I don't want it to handle any firewall rules or DHCP. I just want it to be aware of the VLANs, so that the WiFi devices connecting to it can be routed appropriately by the pfSense router.
Once the port#vlans can be set up correctly, I want to create 4 wireless SSIDs -- so each VLAN and the main LAN can connect to their individual wireless network. Can you also point me to some readings or help me out with that?
Joined: 18 Mar 2014 Posts: 12882 Location: Netherlands
Posted: Sat Sep 05, 2020 8:35 Post subject:
We can help you better if you follow the forum guidelines, link in my signature at the bottom of this post.
Like always stating router model and build number.
We can help you better if you follow the forum guidelines, link in my signature at the bottom of this post.
Like always stating router model and build number.
The build number is listed in the code block above, but here it is nonetheless: DD-WRT v24-sp2 vpn (c) 2013 NewMedia-NET GmbH
Release: 03/25/13 (SVN revision: 21061)
Joined: 18 Mar 2014 Posts: 12882 Location: Netherlands
Posted: Sat Sep 05, 2020 9:40 Post subject:
inxsible wrote:
egc wrote:
We can help you better if you follow the forum guidelines, link in my signature at the bottom of this post.
Like always stating router model and build number.
The build number is listed in the code block above, but here it is nonetheless: DD-WRT v24-sp2 vpn (c) 2013 NewMedia-NET GmbH
Release: 03/25/13 (SVN revision: 21061)
there seems a difference between v1 and v2 but even the v1 has 8 MB flash so consider upgrading to recent build to begin with.
It's strange, but I tried the WebUI to move port4 to VLAN 10 & VLAN11. I clicked Apply Settings and then I telnet again into the router and the port#vlans are set up correctly.
So in short, doing it via CLI reset them on reboot, but doing it in WebUI saved them? OR will they disappear again when I click 'Reboot Router' in the WebUI ?
I assume that I have the v2 version. Since I am using the vpn version, would it be a problem to flash it with a non-vpn version as I am not using the VPN functionality anymore. I checked the Supported Routers --> Netgear and see that my router is listed but I don't know which version I should flash with because my Chip number doesn't match with either of the 4 listings
Thanks,
Last edited by inxsible on Sat Sep 05, 2020 15:25; edited 1 time in total
See the forum guidelines where you can download and how to research.
I am using 44251 on my linksys E2000 and Netgear R6400
Yes, but my confusion is that the build that I have 21061 is already higher than 3 of the listings where my cpu chip is close to the listed cpu chip.
the WNR3500L v2 version has a completely different chip number -- which is why I was asking the question if it would be safe to flash it with that version.
I rebooted the router via the WebUI and I lost my port#vlans configuration again. Not sure how these settings will stick when the CLI and WebUI, both don't seem to work on reboot.
Any help on this please? It would be really difficult if the vlans stop working just due to a router reboot. A reboot could happen for many reasons. I wouldn't want to keep setting up vlans over and over in case the power goes out for a few minutes.
I rebooted the router via the WebUI and I lost my port#vlans configuration again. Not sure how these settings will stick when the CLI and WebUI, both don't seem to work on reboot.
Any help on this please? It would be really difficult if the vlans stop working just due to a router reboot. A reboot could happen for many reasons. I wouldn't want to keep setting up vlans over and over in case the power goes out for a few minutes.
thanks. My router doesn't spell out v2 -- So I'll stick to the build that I have installed and instead focus on why the port$vlans get reset every time I reboot the device.
I rebooted the router via the WebUI and I lost my port#vlans configuration again. Not sure how these settings will stick when the CLI and WebUI, both don't seem to work on reboot.
Any help on this please? It would be really difficult if the vlans stop working just due to a router reboot. A reboot could happen for many reasons. I wouldn't want to keep setting up vlans over and over in case the power goes out for a few minutes.
I still have this problem. How would I make the port*vlans settings stick across a reboot ?
and it is still reset then other then to try a recent build I have no advice for you, unfortunately I am not familiar with your router, some have a different switch layout and need special tweaking
Yes I did the nvram commit, but the reboot then brings the port#vlans back to the following: