LOM also said he tried to put this info on "Supported devices", but wiki background didn't helped. His post here was deleted somehow..
The wiki edit posts were split out of this thread and moved to the General forum.
I didn't try to put the LAN switch info into the Supported Devices wiki page, there is just not room for it there. _________________ Kernel panic: Aiee, killing interrupt handler!
Does anybody know if WRT310N is supported for vlan yet or has anybody found away to get it to work on this model?
Christian Caldwell
Chief of Information and Technology Services
The Brotherhood
Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Wed Aug 25, 2010 6:37 Post subject:
So anything listed above "BCM53115 switch" the GUI as well as telnet can be used to configure, where as anything listed below "BCM53115 switch" in the supported section should only use telnet? _________________ Peacock Thread-FAQ -- dd-wrt Wiki
Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Wed Aug 25, 2010 13:03 Post subject:
When you say "All G spec routers supported by dd-wrt" does this include the G2 and GS2?
Also
phuzi0n wrote:
It's a messy read because VLAN support is a messy topic. Lately I've come to the conclusion that gigabit models do have functional VLAN's but they have to set the nvram variable for the hardware name like I do on my wrt300n v1.1. So to summarize it, I think if you see a VLAN page then you do indeed have full VLAN support but you may have to get your hands dirty with the nvram variables to get it to do what you want. Most Broadcom hardware does have VLAN's but the BCM4704 is one notable chip that doesn't and is included in a lot of the cheap/old N spec models.
Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Wed Aug 25, 2010 13:45 Post subject:
It's quite clear, if the router is neutered (ie 2MB flash) then it really shouldn't support vlans regardless of the switch due to space restrictions. If one needs vlan support it really should be with a better router.
I have done some research and the BCM4705 cpu routers I have found have the BCM5395 switch. And the 600n v1.0 & v1.1 has a BCM5397 switch. I have been trying to keep up with this and I started with a copy of your wiki page, here is mine.
So anything listed above "BCM53115 switch" the GUI as well as telnet can be used to configure, where as anything listed below "BCM53115 switch" in the supported section should only use telnet?
Just ignore the list entirely because it's not accurate. We won't have an accurate list until people test every model. I think I've explained the nvram variables sufficiently for people to start testing support using the nvram variables, granted it can be a PITA especially if you mess up and have to reset... The nvram variables should always work if the hardware supports VLAN's.
One thing I discovered is that even on models with older switches like BCM5325 (wrt300n v1.1), the VLAN GUI does not function with a k2.6 build. I had noticed that /proc/switch isn't created on k2.6 builds and I just realized that it's because the switch-core and switch-robo modules aren't loaded. The /proc/switch directory is used to control the live VLAN configuration (ie. without rebooting) whereas the nvram variables are read by the switch driver upon boot. Previous comments in this thread indicate that loading these two modules allowed the live configuration to be changed but that it was lost after a reboot in which case you would still want to configure the nvram variables manually. I'll experiment with the kernel modules to verify this... _________________ 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)