VLAN Support

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 22:51, 1 September 2010 (edit)
Dark Shadow (Talk | contribs)
(Cisco Linksys)
← Previous diff
Revision as of 02:20, 2 September 2010 (edit) (undo)
Dark Shadow (Talk | contribs)
(Cisco Linksys)
Next diff →
Line 107: Line 107:
| v5.0 | v5.0
| BCM5325E | BCM5325E
 +| Yes
| ? | ?
-| ?+| [http://www.dd-wrt.com/phpBB2/viewtopic.php?p=480022#480022] [http://infodepot.wikia.com/wiki/Linksys_WRT54G_v5.0#vlan_Info]
-| ?+
|- |-

Revision as of 02:20, 2 September 2010



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. Only LAN ports can do VLAN's on devices with BCM4704 CPU due to the WAN port having a separate MII (connection to the CPU). See the discussion in this thread.
  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.


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

Cisco Linksys

Model H.W. rev Switch Chip Port-based VLAN's 802.1q VLAN's Confirmation Links
E2000 v1.0 BCM53115  ?  ?
WRT54G v2.2 BCM5325E Yes  ? [1] [2]
WRT54G v4.0 BCM5325E Yes  ? [3] [4]
WRT54G v5.0 BCM5325E Yes  ? [5] [6]
WRT54G v6.0 BCM5352E  ?  ?  ?
WRT54G v8.0 BCM5354K  ?  ?  ?
WRT54G v8.2 BCM5354K  ?  ?  ?
WRT54G2 v1.0 BCM5354K Yes  ? [7] [8]
WRT54G-TM v1.1 BCM5352E Yes  ? [9] [10]
WRT54GS v1.1 BCM5325E Yes  ? [11] [12]
WRT54GS v2.0 BCM5325E Yes Yes [13]
WRT54GS v5.0 BCM5325E Yes  ? [14] [15]
WRT54GS v6.0 BCM5325E Yes  ? [16] [17]
WRT54GS v7.0 BCM5354K  ?  ?  ?
WRT54GS v7.2 BCM5354K Yes  ? [18] [19]
WRT150N v1.0 BCM5325F  ?  ?
WRT150N v1.1 BCM5325F LAN ports only LAN ports only [20]
WRT160N v1.0 BCM5325F  ?  ?
WRT160N v1.1 BCM5325F  ?  ?
WRT160N v3.0 BCM5325E Yes  ? [21] [22]
WRT300N v1.0 BCM5325F  ?  ?
WRT300N v1.1 BCM5325E Yes Yes [23]
WRT310N v1.0 BCM5397  ?  ?
WRT320N - BCM53115 Yes Yes [24] [25]
WRT350N v1.0 BCM5397 Yes  ? [26] [27]
WRT600N v1.0 BCM5397  ?  ?
WRT600N v1.1 BCM5397 Yes  ? [28] [29]
WRT610N v1.0 BCM53115  ?  ?
WRT610N v2.0 BCM53115  ?  ?


Model H.W. rev Switch Chip Port-based VLAN's 802.1q VLAN's Confirmation Links
WNR3500L - BCM53115 Yes  ? [30]
WNDR3300 - BCM5325F LAN ports only LAN ports only [31]


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...