VLAN Support

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 02:08, 28 August 2010 (edit)
Buddee (Talk | contribs)
m (BCM5354 Switch)
← Previous diff
Revision as of 09:19, 28 August 2010 (edit) (undo)
Phuzi0n (Talk | contribs)
(Majority of reformatting finished - help fill in the tables please)
Next diff →
Line 1: Line 1:
-by ''fggs''+==Introduction==
- +
-Reference: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=62838+
- +
-Hello all,+
- +
-I decided to open this thread to help people find routers with VLAN capabilities and with help of you all, we gonna make a great list. I will try to keep it updated.+
First let's see what VLAN is: First let's see what VLAN is:
Line 15: Line 9:
- Create different subnets for each router's lan port - Create different subnets for each router's lan port
- Change lan/wan port order - Change lan/wan port order
 +- 802.1q tagging so that a single port can carry frames for multiple VLAN's
-And lots of things that I will be adding as soon as I have the information+==General Information==
- +
- +
- +
-''[http://www.dd-wrt.com/phpBB2/viewtopic.php?p=477637#477637 phuzi0n wrote]'': When you test VLAN's you need to try to reconfigure them with the nvram variables. Put a port into the WAN VLAN and see if it starts functioning as a WAN port, add a port to a new VLAN and after rebooting set up the VLAN with an IP and DHCP on the networking page, and if you have multiple VLAN capable routers then try to make a trunk between them with at least 2 tagged VLAN's on each and make sure both VLAN's can communicate with a single cable using the trunk ports.+
- +
-Trunking is a rather high level concept and it hasn't really been explained in detail in any guides that I'm aware of so that might be tough to test yet. I hope I explained it decently on the [[dd-wrt:Switched_Ports|switch ports page]] but I do plan on writing a guide to extend multiple WLAN's with a VLAN trunk. I'm just not sure how exactly I want to write it with all the variety of nvram variables that can exist and the nonfunctional VLAN GUI on all k2.6 builds...+
- +
- +
-=Routers that WILL support VLAN=+
- +
-* All G spec routers supported by dd-wrt (waiting for confirmation)+
- +
-===BCM5354 switch===+
- +
-* Asus WL-520gU+
- +
-===BCM5325E switch===+
- +
-* Linksys WRT54GS v2.0 [http://www.dd-wrt.com/phpBB2/viewtopic.php?p=477637#477637 Confirmed including trunking]+
- +
- +
-* Linksys WRT160N v3.0 (latest build) (waiting for confirmation)+
-* Linksys WRT300N v1.1 [http://www.dd-wrt.com/phpBB2/viewtopic.php?p=477637#477637 Confirmed including trunking]+
- +
-===BCM53115 switch===+
- +
-You will have to add these lines to Startup Script:+
- +
- insmod switch-core+
- insmod switch-robo+
- +
-and don't trust the webgui, use telnet/ssh to set them (specifically for this switch).+
- +
-* Asus RT-N16 (waiting for confirmation)+
-* Linksys WRT320N v1.0 [http://www.dd-wrt.com/phpBB2/viewtopic.php?p=477637#477637 Confirmed including trunking]+
-* Linksys WRT610N v1.0 (waiting for confirmation)+
-* Linksys WRT610N v2.0 (waiting for confirmation)+
-* Netgear WNR3500L [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=77865 Confirmed]+
-* Netgear WNR3500v2/U (waiting for confirmation)+
- +
-=Routers that WON'T support VLAN=+
-* Any router with a non broadcom switch chip.+
- +
-===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)+
-* Netgear WNDR3300 (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)+
- +
-PS: Thanks to redhawk0 for the inspiration of the subject+Here are some broad generalizations about what hardware is believed to be able to support VLAN's in DD-WRT currently:
- +
-==Introduction==+
- +
-==General Information==+
-(section for generalizations of what hardware is believed to be supported+# Only Broadcom based devices, no Atheros or Ralink devices.
 +# No devices with BCM4704 CPU ([http://www.dd-wrt.com/phpBB2/viewtopic.php?t=62838 see this thread] to discuss)
 +# Any other devices that don't create vlan# interfaces by default.
 +# If vlan# interfaces are created then they likely can be reconfigured and tagged using nvram settings as explained on the [[Switched Ports]] page because the VLAN GUI is unreliable on modern devices.
==VLAN Support Tables== ==VLAN Support Tables==
Line 90: Line 25:
* Port-based VLAN's means that you can reconfigure ports to be in different VLAN's. Port-based VLAN's do not confirm 802.1q VLAN support. * Port-based VLAN's means that you can reconfigure ports to be in different VLAN's. Port-based VLAN's do not confirm 802.1q VLAN support.
* 802.1q VLAN's means that you can tag VLAN's with 802.1q headers to create a trunk between two devices that carries frames for multiple VLAN's. 802.1q VLAN's confirm that there is also Port-based VLAN support. * 802.1q VLAN's means that you can tag VLAN's with 802.1q headers to create a trunk between two devices that carries frames for multiple VLAN's. 802.1q VLAN's confirm that there is also Port-based VLAN support.
-* Always put a Confirmation Link when confirming that there '''is''' ("Yes") or '''is not''' ("No") support for either type of VLAN support. If you can not link to any confirmation then put a question mark ("?").+* Always put a Confirmation Link when confirming that there '''is''' ("Yes") or '''is not''' ("No") support for either type of VLAN support. If you can not link to any confirmation then put a question mark ("?") for the VLAN types that can't be confirmed.
 +* Multiple links for the same model are encouraged to help provide better reference.
---- ----
 +
 +===Asus===
 +
 +{| style="font-size:85%; text-align:center;" border=1 cellspacing=0 cellpadding=3 class="wikitable"
 +|-style="background-color:#d2d2d2;"
 +! Model
 +! H.W. rev
 +! Switch Chip
 +! Port-based VLAN's
 +! 802.1q VLAN's
 +! Confirmation Links
 +|-
 +
 +|-
 +| RT-N16
 +| -
 +| BCM53115
 +| ?
 +| ?
 +|
 +|-
 +
 +|}
===Cisco Linksys=== ===Cisco Linksys===
Line 130: Line 89:
|- |-
| WRT320N | WRT320N
-| v1+| -
| BCM53115 | BCM53115
| Yes | Yes
| Yes | Yes
| [http://www.dd-wrt.com/phpBB2/viewtopic.php?p=477637#477637] | [http://www.dd-wrt.com/phpBB2/viewtopic.php?p=477637#477637]
 +|-
 +
 +|}
 +
 +===Netgear===
 +
 +{| style="font-size:85%; text-align:center;" border=1 cellspacing=0 cellpadding=3 class="wikitable"
 +|-style="background-color:#d2d2d2;"
 +! Model
 +! H.W. rev
 +! Switch Chip
 +! Port-based VLAN's
 +! 802.1q VLAN's
 +! Confirmation Links
 +|-
 +
 +|-
 +| WNR3500L
 +| -
 +| BCM53115
 +| Yes
 +| ?
 +| [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=77865]
|- |-
Line 142: Line 124:
==Testing== ==Testing==
-(section for instructions to test for support)+''[http://www.dd-wrt.com/phpBB2/viewtopic.php?p=477637#477637 phuzi0n wrote]'': When you test VLAN's you need to try to reconfigure them with the nvram variables. Put a port into the WAN VLAN and see if it starts functioning as a WAN port, add a port to a new VLAN and after rebooting set up the VLAN with an IP and DHCP on the networking page, and if you have multiple VLAN capable routers then try to make a trunk between them with at least 2 tagged VLAN's on each and make sure both VLAN's can communicate with a single cable using the trunk ports.
 + 
 +Trunking is a rather high level concept and it hasn't really been explained in detail in any guides that I'm aware of so that might be tough to test yet. I hope I explained it decently on the [[Switched_Ports|switch ports page]] but I do plan on writing a guide to extend multiple WLAN's with a VLAN trunk. I'm just not sure how exactly I want to write it with all the variety of nvram variables that can exist and the nonfunctional VLAN GUI on all k2.6 builds...
==References== ==References==
* [[Switched_Ports|Switched Ports]] - Explains how to configure VLAN's using NVRAM variables. * [[Switched_Ports|Switched Ports]] - Explains how to configure VLAN's using NVRAM variables.
 +* [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=62838 Routers that will and won't support VLAN] - Forum thread that sparked discussion of this topic.
* [[Default Configuration Overview|VLAN Default Configuration]] * [[Default Configuration Overview|VLAN Default Configuration]]
* [[VLAN Configuration|VLAN Configuration]] * [[VLAN Configuration|VLAN Configuration]]

Revision as of 09:19, 28 August 2010

Contents

Introduction

First let's see what VLAN is:

"A virtual LAN, commonly known as a VLAN, is a group of hosts with a common set of requirements that communicate as if they were attached to the same Broadcast domain, regardless of their physical location. A VLAN has the same attributes as a physical LAN, but it allows for end stations to be grouped together even if they are not located on the same network switch. Network reconfiguration can be done through software instead of physically relocating devices." (Quoted from wikipedia)

What you can do with VLAN support in dd-wrt:

- Create different subnets for each router's lan port - Change lan/wan port order - 802.1q tagging so that a single port can carry frames for multiple VLAN's

General Information

Here are some broad generalizations about what hardware is believed to be able to support VLAN's in DD-WRT currently:

  1. Only Broadcom based devices, no Atheros or Ralink devices.
  2. No devices with BCM4704 CPU (see this thread to discuss)
  3. Any other devices that don't create vlan# interfaces by default.
  4. If vlan# interfaces are created then they likely can be reconfigured and tagged using nvram settings as explained on the Switched Ports page because the VLAN GUI is unreliable on modern devices.

VLAN Support Tables

Some notes about the tables:

  • Port-based VLAN's means that you can reconfigure ports to be in different VLAN's. Port-based VLAN's do not confirm 802.1q VLAN support.
  • 802.1q VLAN's means that you can tag VLAN's with 802.1q headers to create a trunk between two devices that carries frames for multiple VLAN's. 802.1q VLAN's confirm that there is also Port-based VLAN support.
  • Always put a Confirmation Link when confirming that there is ("Yes") or is not ("No") support for either type of VLAN support. If you can not link to any confirmation then put a question mark ("?") for the VLAN types that can't be confirmed.
  • Multiple links for the same model are encouraged to help provide better reference.




Asus

Model H.W. rev Switch Chip Port-based VLAN's 802.1q VLAN's Confirmation Links
RT-N16 - BCM53115  ?  ?

Cisco Linksys

Model H.W. rev Switch Chip Port-based VLAN's 802.1q VLAN's Confirmation Links
WRT54GS v2.0 BCM5325E Yes Yes [1]
WRT300N v1.1 BCM5325E Yes Yes [2]
WRT320N - BCM53115 Yes Yes [3]

Netgear

Model H.W. rev Switch Chip Port-based VLAN's 802.1q VLAN's Confirmation Links
WNR3500L - BCM53115 Yes  ? [4]


Testing

phuzi0n wrote: When you test VLAN's you need to try to reconfigure them with the nvram variables. Put a port into the WAN VLAN and see if it starts functioning as a WAN port, add a port to a new VLAN and after rebooting set up the VLAN with an IP and DHCP on the networking page, and if you have multiple VLAN capable routers then try to make a trunk between them with at least 2 tagged VLAN's on each and make sure both VLAN's can communicate with a single cable using the trunk ports.

Trunking is a rather high level concept and it hasn't really been explained in detail in any guides that I'm aware of so that might be tough to test yet. I hope I explained it decently on the switch ports page but I do plan on writing a guide to extend multiple WLAN's with a VLAN trunk. I'm just not sure how exactly I want to write it with all the variety of nvram variables that can exist and the nonfunctional VLAN GUI on all k2.6 builds...

References