Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Tue Aug 31, 2010 21:15 Post subject:
Eko wrote:
phuzi0n wrote:
Dark_Shadow wrote:
@ phuzi0n, Should 2 more column's be added to the charts for "Via GUI" and "Via nvram", so that we can give a better idea of where to go first and users won't have to waist time trying to set the GUI if it doesn't work?
At this time everyone should assume the GUI is broken unless it is said otherwise in the confirmation links. I'll see about coming up with something to make setting the nvram variables easier if I can...
GUI works for "clasic" 100Mbps switches which load switch-core and (switch-robo or switch-adm)
I can confirm that the WRT54GS v5.0 supports port based vlans via the GUI with 14929 micro. I will flash a micro plus SSH, retest via nvram and update this post.
EDIT: vlans via nvram on 14848 NEWD micro plus confirmed.
WRT54GS v5.0's ports are mapped like this:
4 3 2 1 | case labels
3 2 1 0 | nvram port numbers
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Tue Aug 31, 2010 23:06 Post subject:
I got interesting results last night with the WNDR3300, after failing with some of my own settings, i tried the 'basic' examples mentioned in the wiki, which from output on the shell said it was working (tried the block all LAN ports example) but i could still plug into any port and get access.
Also there is no webgui VLANs tab in the WNDR3300 mini test build, so i am guessing this is not a 'classic' 100Mbit. I am gonna flash back to 14853 and do some manual tests once again with the codes that phuzi0n provided in earlier post and see how that does. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
@ phuzi0n, Should 2 more column's be added to the charts for "Via GUI" and "Via nvram", so that we can give a better idea of where to go first and users won't have to waist time trying to set the GUI if it doesn't work?
At this time everyone should assume the GUI is broken unless it is said otherwise in the confirmation links. I'll see about coming up with something to make setting the nvram variables easier if I can...
GUI works for "clasic" 100Mbps switches which load switch-core and (switch-robo or switch-adm)
Also, even with k2.4 builds and a 100mbps switch there are some inconsistencies with certain features that the GUI doesn't always account for, particularly with 802.1q tagging. Some models seem to tag even without the "t" after the port number in vlan#ports variables (the GUI never use "t"), but other models must have "t" set for tagging to work. _________________ 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)
Also there is no webgui VLANs tab in the WNDR3300 mini test build, so i am guessing this is not a 'classic' 100Mbit. I am gonna flash back to 14853 and do some manual tests once again with the codes that phuzi0n provided in earlier post and see how that does.
The VLAN GUI page should show up if you've enabled it. With the test build you need to run these commands.
nvram set force_vlan_supp
nvram commit
reboot _________________ 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)
Decided that my posts were getting a little long and I was gonna include that info on my wiki so just decided to add it there and make a link. _________________ Peacock Thread-FAQ -- dd-wrt Wiki
The VLAN GUI page should show up if you've enabled it. With the test build you need to run these commands.
nvram set force_vlan_supp
nvram commit
reboot
Doh, it should be this:
nvram set force_vlan_supp=enabled
nvram commit
reboot
It's not very important whether /proc/switch exists or if it functions correctly. As I've explained a few times, it is used for updating the running configuration in real time instead of rebooting. You can just echo your port configuration to the files nested deep within the directories to update your VLAN port configuration in real time. I gave a couple examples already so go back and look at them if you're really interested in it. _________________ 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 Jul 2009 Posts: 492 Location: Toronto, ON, CA
Posted: Wed Sep 01, 2010 4:14 Post subject:
Just got my Asus RT-N16 back from RMA and can test command to get VLANs working properly. I want to set LAN Port 4 on separate VLAN with DHCP IP Address assigned in the 192.168.3.1 range. What command would I need to use in Telnet. _________________ Asus RT-N16 [Build King Kong 18050M NEWD-2 K2.6 + Optware + My Page]
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Wed Sep 01, 2010 10:33 Post subject:
phuzi0n wrote:
Doh, it should be this:
nvram set force_vlan_supp=enabled
nvram commit
reboot
It's not very important whether /proc/switch exists or if it functions correctly. As I've explained a few times, it is used for updating the running configuration in real time instead of rebooting. You can just echo your port configuration to the files nested deep within the directories to update your VLAN port configuration in real time. I gave a couple examples already so go back and look at them if you're really interested in it.
Aha! that did it man, thanks. I am also guessing (seen in the VLAN supported wiki) that tagging with the wndr3300 aint happening. I have tried to get tagging working as well, no such luck thus far, but i can atleast now get it working at the port lvl. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ