Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Fri Aug 27, 2010 2:04 Post subject:
phuzi0n wrote:
Dark_Shadow wrote:
=Routers that WON'T support VLAN= ===BCM5395 switch===
* Linksys WRT150N v1.0 (waiting for confirmation)
* Linksys WRT150N v1.1 (waiting for confirmation)
* Linksys WRT160N v1.0 (waiting for confirmation)
* Linksys WRT160N v1.1 (waiting for confirmation)
* Linksys WRT300N v1.0 (waiting for confirmation)
===BCM5397 switch===
* Linksys WRT310N v1.0 (waiting for confirmation)
* Linksys WRT350N v1.0 (waiting for confirmation)
* Linksys WRT600N v1.0 (waiting for confirmation)
* Linksys WRT600N v1.1 (waiting for confirmation)
You've mucked up the switch chips in these lists.
The italic models all have VLAN interfaces by default afaik so they need to be tested to see if they can be reconfigured. It is very likely that they can.
The others all have 4704 CPU's which need deeper investigation.
??? How has it been mucked up? are you saying that the BCM5397 switch is supposed to support vlans and we just need confirmation? _________________ Peacock Thread-FAQ -- dd-wrt Wiki
Also before i try this, and waste alot of time doing so, you guys know if Atheros has any kind of VLAN support? I have a WRT160NL and WRT400N i can throw at these tests as well.
There is afaik no vlan support for the Atheros builds even if the switch driver itself supports vlan's because the Atheros boot loaders doesn't read nvram variables when doing the switch config as the Broadcom cfe does.
WRT160N has an RTL8306SD switch with vlan supoort in the driver but dd-wrt doesn't have a way of talking with the driver in order to configure it.
The same is valid for the RTL8366 gigabit switch used in many Ralink and Atheros based routers.
Other switches for Atheros routers are Atheros AR8216 fast ethernet switch (WRT400N) and AR8316 gigabit switch, I haven't checked if their drivers has vlan support. _________________ Kernel panic: Aiee, killing interrupt handler!
=Routers that WON'T support VLAN= ===BCM5395 switch===
* Linksys WRT150N v1.0 (waiting for confirmation)
* Linksys WRT150N v1.1 (waiting for confirmation)
* Linksys WRT160N v1.0 (waiting for confirmation)
* Linksys WRT160N v1.1 (waiting for confirmation)
* Linksys WRT300N v1.0 (waiting for confirmation)
===BCM5397 switch===
* Linksys WRT310N v1.0 (waiting for confirmation)
* Linksys WRT350N v1.0 (waiting for confirmation)
* Linksys WRT600N v1.0 (waiting for confirmation)
* Linksys WRT600N v1.1 (waiting for confirmation)
You've mucked up the switch chips in these lists.
The italic models all have VLAN interfaces by default afaik so they need to be tested to see if they can be reconfigured. It is very likely that they can.
The others all have 4704 CPU's which need deeper investigation.
??? How has it been mucked up? are you saying that the BCM5397 switch is supposed to support vlans and we just need confirmation?
If I'm not mistaken the 150/160/300v1 all use BCM5325 and 600's have BCM5395. _________________ 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: Fri Aug 27, 2010 3:56 Post subject:
phuzi0n wrote:
If I'm not mistaken the 150/160/300v1 all use BCM5325 and 600's have BCM5395.
I have confirmed those switch chips on
===BCM5325F switch===
* Linksys WRT150N v1.0 (waiting for confirmation)
* Linksys WRT150N v1.1 (waiting for confirmation)
* Linksys WRT160N v1.0 (waiting for confirmation)
* Linksys WRT160N v1.1 (waiting for confirmation)
* Linksys WRT300N v1.0 (waiting for confirmation)
EDIT: Honestly I don't know what I was thinking.
I have not taken the Heat Sink off the switch chip on my 600 v1.1 but the FCC pic show a BCM5397K Switch here. _________________ Peacock Thread-FAQ -- dd-wrt Wiki
WRT160N has an RTL8306SD switch with vlan support in the driver but dd-wrt doesn't have a way of talking with the driver in order to configure it.
You referring to the v2.0 WRT160N?
No, the 160NL. I somehow dropped the "L" but the post was a reply mainly about Atheros routers.. _________________ Kernel panic: Aiee, killing interrupt handler!
The wndr3300 has a 4704 CPU so if it does support VLAN's then it's going to require more work than just setting some nvram variables because it doesn't create any by default.
The cpu shouldn't matter unless it is a cpu (SOC) with built-in switch like the BCM535x series SOC's.
The WNDR3300 has a BCM5325F switch so it should be possible to use VLAN's on it.
AFAIK all of the models with 4704 CPU's don't create VLAN's by default in dd-wrt though. They have an eth# interface for the WAN port and another eth# interface for the LAN ports. My wrt150n v1.1 and wndr3300 have nvram variables set by default, changing them doesn't do anything, and I haven't figure out any way to get them to work.
buddee wrote:
Port based vlans seems no problem with the wndr3300, but since its an F and not an E switch chip, 802.1Q based VLANs is not seeming to happen
Really? You get vlan interfaces to show up in ifconfig? What exactly did you do and was it on a k2.4 build or k2.6? I've currently got a k2.4 build on mine. _________________ 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)
Port based vlans seems no problem with the wndr3300, but since its an F and not an E switch chip, 802.1Q based VLANs is not seeming to happen
Really? You get vlan interfaces to show up in ifconfig? What exactly did you do and was it on a k2.4 build or k2.6? I've currently got a k2.4 build on mine.
The E and F types of 5325 may be the culprit, I don't fully understand why..
Oleg who did the robocfg software and who has some good knowledge about vlan configuration once wrote:
" As I just saw one seemingly has to pay attention to the letter following the model number, 5325F in case of the WL-500W, 5325E in case of the WL-500gP v1. The "F"-model only implements port-based VLAN, whereas the "E"-model additionally implements 802.1Q based VLAN - which is what we need here - and even IGMP layer 3 snooping - which is what we even did not dare to dream of .. "
If I decipher that correct then it means that the E version supports vlan tagging but the F version doesn't. _________________ Kernel panic: Aiee, killing interrupt handler!
The E and F types of 5325 may be the culprit, I don't fully understand why..
Oleg who did the robocfg software and who has some good knowledge about vlan configuration once wrote:
" As I just saw one seemingly has to pay attention to the letter following the model number, 5325F in case of the WL-500W, 5325E in case of the WL-500gP v1. The "F"-model only implements port-based VLAN, whereas the "E"-model additionally implements 802.1Q based VLAN - which is what we need here - and even IGMP layer 3 snooping - which is what we even did not dare to dream of .. "
If I decipher that correct then it means that the E version supports vlan tagging but the F version doesn't.
Oh yeah, I recall reading that before. If that is part of the reason why the 4704 models don't have VLAN's by default, port based VLAN's would still be better than none at all. _________________ 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: Fri Aug 27, 2010 5:20 Post subject:
The following link has some Tomato Firmware VLAN commands for the Asus RT-N16. Hepefully someone can figure out how to use them to get DD-WRT VLAN to work with the RT-N16.
I can see from my hardware list that almost all 4704 routers are using the F version of the switch, exception being the Asus WL500gpv1 using the E, and a few older routers from various mfgrs using the 5325A2.
The WRT300 v1.0 with a 4704 cpu has the F switch while a WRT300 v1.1 with 4785 cpu has the E switch.
The 160v3 also has the E switch and so has the newer Linksys M10 and E-1000 models. (no surprise since they are 160v3 under a new name) _________________ Kernel panic: Aiee, killing interrupt handler!
The following link has some Tomato Firmware VLAN commands for the Asus RT-N16. Hepefully someone can figure out how to use them to get DD-WRT VLAN to work with the RT-N16.
The RT-N16 just needs the nvram commands set correctly as I explained on the switched ports page. I know I've seen at least one case of someone configuring VLAN's with dd-wrt on the RT-N16 using nvram commands but it was in another thread. _________________ 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)
