Aha! that did it man, thanks. I am also guessing (seen in the VLAN supported wiki) that tagging with the wndr3300 aint happening. I have tried to get tagging working as well, no such luck thus far, but i can atleast now get it working at the port lvl.
I made a 802.1q trunk just fine on the wndr3300 and listed it in the "802.1q VLAN's" column.
I create two trunk ports on all my routers and can create a daisy chain from the gateway router all the way to my PC and use my nic's tagging to switch between VLAN's. The routers can all ping each other on every VLAN's subnet and connecting to certain ports/VAP's will limit the client to only communicating with that subnet unless it sends it through the gateway which will then route it if allowed by the firewall.
It's not something easy to test if you're not already familiar with how it works so maybe wait for me to write a guide about trunking. The confusion with VLAN support needs to settle a bit more before I approach how to explain it well. _________________ 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)
Nothing changed and the firmware couldn't change which # is mapped to which port if it wanted to; an if statement was just split to two lines. _________________ 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: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Wed Sep 01, 2010 23:05 Post subject:
phuzi0n wrote:
buddee wrote:
Aha! that did it man, thanks. I am also guessing (seen in the VLAN supported wiki) that tagging with the wndr3300 aint happening. I have tried to get tagging working as well, no such luck thus far, but i can atleast now get it working at the port lvl.
I made a 802.1q trunk just fine on the wndr3300 and listed it in the "802.1q VLAN's" column.
I create two trunk ports on all my routers and can create a daisy chain from the gateway router all the way to my PC and use my nic's tagging to switch between VLAN's. The routers can all ping each other on every VLAN's subnet and connecting to certain ports/VAP's will limit the client to only communicating with that subnet unless it sends it through the gateway which will then route it if allowed by the firewall.
It's not something easy to test if you're not already familiar with how it works so maybe wait for me to write a guide about trunking. The confusion with VLAN support needs to settle a bit more before I approach how to explain it well.
Excellent, i know how it works somewhat, in pfsense anyhow, that is why i was very interested in this subject, i am trying to get my dd-wrt unit to do, atleast on the basic lvl, what i could get some of the boxes i actually turned into wired routers to do.
Just got my Asus RT-N16 back from RMA and can test command to get VLANs working properly. I want to set LAN Port 4 on separate VLAN with DHCP IP Address assigned in the 192.168.3.1 range. What command would I need to use in Telnet.
This should either put port 1 or port 4 into VLAN 3.
nvram set vlan1ports="4 3 2 8*"
nvram set vlan3ports="1 8"
nvram set vlan3hwname=et0
nvram set port5vlans="1 2 3 16"
nvram commit
reboot
After it reboots you should have a new interface called vlan3 that you can configure on the networking page to have an IP address and DHCP pool. I know people have confirmed RT-N16 supports VLAN's but it was in other threads in the past. _________________ 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)
@ phuzi0n the trunking examples in the switched ports wiki are for gigabit units?
Edit: pretty sure they are, time to break out the E2000 and see if this is like the wrt320n
Yes they're examples for a gigabit model, but as with all of the examples you can't just copy+paste them due to port numbering differences anyways. The examples are mainly to show all the variables that have to be set, but you still have to think about how they should be set for your model.
Trunking with 100mbps models can be a bit more work because you should avoid tagging VLAN 0. If you want to remove VLAN 0 completely then there's several things that have to be done so that the firmware doesn't reset the VLAN's that I'll explain later. _________________ 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: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Thu Sep 02, 2010 0:11 Post subject:
phuzi0n wrote:
buddee wrote:
@ phuzi0n the trunking examples in the switched ports wiki are for gigabit units?
Edit: pretty sure they are, time to break out the E2000 and see if this is like the wrt320n
Yes they're examples for a gigabit model, but as with all of the examples you can't just copy+paste them due to port numbering differences anyways. The examples are mainly to show all the variables that have to be set, but you still have to think about how they should be set for your model.
Trunking with 100mbps models can be a bit more work because you should avoid tagging VLAN 0. If you want to remove VLAN 0 completely then there's several things that have to be done so that the firmware doesn't reset the VLAN's that I'll explain later.
Just got my Asus RT-N16 back from RMA and can test command to get VLANs working properly. I want to set LAN Port 4 on separate VLAN with DHCP IP Address assigned in the 192.168.3.1 range. What command would I need to use in Telnet.
This should either put port 1 or port 4 into VLAN 3.
nvram set vlan1ports="4 3 2 8*"
nvram set vlan3ports="1 8"
nvram set vlan3hwname=et0
nvram set port5vlans="1 2 3 16"
nvram commit
reboot
After it reboots you should have a new interface called vlan3 that you can configure on the networking page to have an IP address and DHCP pool. I know people have confirmed RT-N16 supports VLAN's but it was in other threads in the past.
Code:
RT-N16 VLAN.jpg
Description:
Filesize:
186.71 KB
Viewed:
41962 Time(s)
_________________ Asus RT-N16 [Build King Kong 18050M NEWD-2 K2.6 + Optware + My Page]
Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Thu Sep 02, 2010 1:26 Post subject:
phuzi0n wrote:
Nothing changed and the firmware couldn't change which # is mapped to which port if it wanted to; an if statement was just split to two lines.
Gotchya, was through of by a line that wasn't changed "//fix lan port numbering on CSE41, CSE51". Guess I should have read a little closer. _________________ Peacock Thread-FAQ -- dd-wrt Wiki