VLAN Bridging WAN and a LAN port
From DD-WRT Wiki
(Difference between revisions)
Revision as of 15:04, 10 January 2007 (edit) P1415 (Talk | contribs) (reverted spam by 1168422543) ← Previous diff |
Revision as of 14:35, 19 June 2008 (edit) (undo) JuddMan (Talk | contribs) Next diff → |
||
Line 16: | Line 16: | ||
That's it. No firewall rules or bridging needs to be set up. Port 1 is now a direct WAN port, and your second router/AP/server can use one of your extra public IPs. | That's it. No firewall rules or bridging needs to be set up. Port 1 is now a direct WAN port, and your second router/AP/server can use one of your extra public IPs. | ||
+ | |||
+ | |||
+ | To undo this, make a note of that the values were for vlan0ports and vlan1ports before changing them. For my router they were originally: | ||
+ | vlan0ports=1 2 3 4 5* | ||
+ | vlan1ports=0 5 |
Revision as of 14:35, 19 June 2008
For WRT54GS v2
If your ISP gives you multiple public IPs, and you want to hang a second router or other device on your main router with direct access to the WAN, fear not, it's easy:
Your original VLAN should look like this (among other lines) if you run the command nvram show |grep vlan
vlan0ports=1 2 3 4 5* vlan1ports=0 5
So the following commands move LAN port 1 to the WAN VLAN:
nvram set vlan0ports="2 3 4 5*" nvram set vlan1ports="0 1 5" nvram commit reboot
That's it. No firewall rules or bridging needs to be set up. Port 1 is now a direct WAN port, and your second router/AP/server can use one of your extra public IPs.
To undo this, make a note of that the values were for vlan0ports and vlan1ports before changing them. For my router they were originally:
vlan0ports=1 2 3 4 5*
vlan1ports=0 5