RE-EDIT: Port 4 in the GUI is still check on the LAN vlan.
I should also add that the GUI worked before this update for moving port 4 to the WAN vlan and it acted like a wan port and pulled a wan IP from the source router. _________________ Peacock Thread-FAQ -- dd-wrt Wiki
Eko, Is it also possible for you to get the Asus RT-N16 VLANs working through the GUI?
Not for any Gbit switch right now...
Why not? There's been many confirmations that setting nvram variables works on gigabit switches. The problem for most gigabit models is that on k2.6 builds the VLAN GUI doesn't set the nvram variables properly regardless of what kind of ports the router has.
http://svn.dd-wrt.com:8000/dd-wrt/ticket/1701 _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Mon Aug 30, 2010 20:33 Post subject:
Eko wrote:
@Dark_shadow:
I don't understand - if GUI worked, what was the problem then.... again?
Was testing for phuzi0n. setting nvram wouldn't stick or rendered the router unconnectable, hard reset required before the test build.
Hey, I'm fine. I don't even require vlan. I had this device and decided to test for it. phuzi0n said that the GUI as just an indicator of how the vlan's were set.
phuzi0n wrote:
Dark_Shadow wrote:
Should I reset the GUI vlan's to default before testing?
No, they're pretty much only for a visual reference AFAICT. I overemphasized the importance of port5vlans, iirc only one model needed it set correctly. You're not adding any VLAN's so you don't need to do anything with it though.
Was testing for phuzi0n. setting nvram wouldn't stick or rendered the router unconnectable, hard reset required.
Hey, I'm fine. I don't even require vlan. I had this device and decided to test for it. phuzi0n said that the GUI as just an indicator of how the vlan's were set.
So it was your settings in the GUI that were allowing port 4 to work as a LAN port until you rebooted, and setting the nvram variables always caused you to need to hard reset? I was under the impression that the nvram variables were working after a reboot but that they also reset to default. Eko's change only made it so that the nvram variables don't reset after a reboot, so if the GUI was working before then it should still be working, and you should now be able to change the nvram variables and not have them reset. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Mon Aug 30, 2010 21:19 Post subject:
phuzi0n wrote:
Dark_Shadow wrote:
Was testing for phuzi0n. setting nvram wouldn't stick or rendered the router unconnectable, hard reset required.
Hey, I'm fine. I don't even require vlan. I had this device and decided to test for it. phuzi0n said that the GUI as just an indicator of how the vlan's were set.
So it was your settings in the GUI that were allowing port 4 to work as a LAN port until you rebooted, and setting the nvram variables always caused you to need to hard reset? I was under the impression that the nvram variables were working after a reboot but that they also reset to default. Eko's change only made it so that the nvram variables don't reset after a reboot, so if the GUI was working before then it should still be working, and you should now be able to change the nvram variables and not have them reset.
Nope, I did a hard reset before trying to configure your setting, despite what you said. After a hard reset the gui works fine.
No, the nvram variables never worked until eko's test build. When I tried to change the nvram settings, ether they would reset to default upon reboot or the router was un-accessible upon reboot. So I did a hard reset on the last time the router became un-accessible and tested the GUI from a fresh hard reset.
I have not tried the GUI with eko's nvram settings on the test build.
with 14929 the GUI worked as far as moving port 4 to the WAN's vlan. I didn't try anything else. setting the nvram variable did not work at all, ether resetting to default even after commit and reboot or rendering the router un-accessible and no internet. _________________ Peacock Thread-FAQ -- dd-wrt Wiki
Alright, well with the nvram variables still set to what Eko said (port 4 in vlan2) could you check the output of all these commands please.
lsmod
ls /proc/switch #I think this will be eth2, if it's not then fix the paths in the next commands
cat /proc/switch/eth2/vlan/0/ports
cat /proc/switch/eth2/vlan/1/ports
cat /proc/switch/eth2/vlan/2/ports
nvram show | grep vlan.ports
As long as switch-core and switch-robo are listed in lsmod then you should be able to set the VLAN's live without rebooting by echoing the vlan#ports to /proc/switch directories like this.
ps. I think I've gotten VLAN's to work on wrt150n v1.1 by setting the boardflag to 0x110 but I need to test how much functionality there is. Right now vlan0 is handling the LAN port that I'm posting this through. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
I have 2 WLANs, primary WLAN is connected to br0/vlan1 and the additional WLAN is connected to br1/vlan3. Switchport 3 is also on br1/vlan3. Vlan3 has a seperate subnet. I can access Internet from both subnets, either via LAN or WLAN.
After e reboot, vlans still work as they should. _________________ Netgear R7000 DD-WRT v3.0-r28072 std (11/02/15)
Cisco 1941/K9 Version 15.2(4)M6a
2x Cisco SG 200-08 1.0.8.3
