I unsuccessfully tried VLANs on a RT-N16 running DD-WRT v24-sp2 (06/12/10) mini(SVN revision 14594) but this thread the link below and gave me some hope that it could work now...
http://infodepot.wikia.com/wiki/Asus_RT-N16#vlan_Info
The RT-N16 is running the backend of my gigabit home network and it would be hard for me to do any testing on it.
Were you successful running VLANs on the RT-16N? If so, what version did you use, and how did you do it (GUI vs commands)?
Thank you!
You need build 15508 or higher to use the GUI on that model. You can use the nvram commands explained on the switched ports wiki page on any model/build. _________________ 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)
The trick is to make vlan3 (or any other but vlan1) the native vlan on the trunk on the Cisco. By default vlan1 is the native one, but then vlan1 traffic is not passed to the Linksys. I guess the explanation for this is http://en.wikipedia.org/wiki/IEEE_802.1Q#Trunk_Ports_and_the_Native_VLAN but I don't understand why with vlan3 being native on the Cisco IOS router, egress vlan3 packets (which if I understand correctly are not being tagged) are accepted by the Linksys. However, I'm 100% sure that with vlan1 being the native one, vlan1 did not work between the Cisco IOS router and the Linksys.
does anyone know if this is still the only method to get 802.1q trunks to work on the WRT320N? I have an HP ProCurve 1810-8G switch and the native vlan on every port is 1. You do NOT have the ability to change the default vlan from 1 on the HP switch. So i was curious if this router will still be able to do 802.1q trunks connected to this switch.
does anyone know if this is still the only method to get 802.1q trunks to work on the WRT320N?
You can use the GUI with build 15508 or higher.
kacole2 wrote:
I have an HP ProCurve 1810-8G switch and the native vlan on every port is 1. You do NOT have the ability to change the default vlan from 1 on the HP switch. So i was curious if this router will still be able to do 802.1q trunks connected to this switch.
Thanks in advance!
This is confusing and the way you describe it is as if the switch doesn't allow any configuration at all... Take it to a new thread and be more clear please. _________________ 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)
after a reboot, port 1 (which is labelled '4' on the back) is on the vlan1 network, but packets are not tagged. I'm not sure what to do next to debug this. Can anybody tell me where I should look next? Thanks!
How are you determining that they're not tagged? If you're trying to trunk to another device that uses VLAN 1 as the native VLAN then that device won't be tagging it VLAN 1. If you plug a PC into it without tagging enabled then it shouldn't work, and if you then configure the PC to tag VLAN 1 then it should start working. You could also try tagging another VLAN and testing it. _________________ 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)
I've got a linux box plugged into the port. tcpdump -e -n -i eth0 shows all the packets from vlan1 coming through with their native (IPv4, ARP, etc) ethertype. I expect to see 802.1Q with a vlan number. If I run tcpdump -e -n -i eth0.1 I see nothing at all.
As you suggested, I set up the port to tag vlan 3:
vlan1ports=4 8*
vlan3ports=1t 3 8
tcpdump now shows me the traffic from hosts on vlan3. If I bring up eth0 manually using an IP valid on that segment, I can communicate with hosts there.
Hmmm, in your original configuration was your PC able to communicate in VLAN 1 at all (with or without tagging)?
I did a lot of testing a few months ago which involved a lot of swapping cables around between multiple routers with tagged ports and untagged ports, occasionally there would be inconsistent behavior that would resolve itself by swapping cables around and back... I haven't done any sniffing on a tagged port, but when I connect my PC to a tagged port it isn't able to communicate to the router unless I enable tagging on the PC and set its VLAN ID accordingly.
The subject of native VLAN's (untagged default VLAN on a trunk port) has been coming up lately and you've given me some ideas on how it might be possible. _________________ 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)
This is my first attempt to get tagged vlans working on this network, although I do have experience setting up vlans on a different network with different hardware. I suppose it's possible the hardware is doing something surprising, but I would not expect it to do anything with vlan tags != 1.
I can do some testing later today with another linux box, and see if I can set up a tagged vlan between the two machines.
Is there anything you'd like me to try to test your ideas?
Is there anything you'd like me to try to test your ideas?
Nope, I've got a decent variety of hardware to test with and it will involve playing with the nvram variables a lot to see if anything works. _________________ 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: 22 Jan 2011 Posts: 19 Location: N 1 17.684 E 103 51.533
Posted: Sat Feb 12, 2011 15:26 Post subject:
Hi Guru's
I've flashed my router WRT320N (converted to E2000 build 15943) with firmware 'dd-wrt.v24-15230_NEWD-2_K2.6_mini-vlantest.bin" to test the VLAN functions.
However after rebooting I noticed that blue power LED keep blinking continuously. I could not login to the default IP of 192.168.1.1 anymore. Not sure if I have bricked the router with this update.
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Sat Feb 12, 2011 15:30 Post subject:
scorp588 wrote:
Hi Guru's
I've flashed my router WRT320N (converted to E2000 build 15943) with firmware 'dd-wrt.v24-15230_NEWD-2_K2.6_mini-vlantest.bin" to test the VLAN functions.
However after rebooting I noticed that blue power LED keep blinking continuously. I could not login to the default IP of 192.168.1.1 anymore. Not sure if I have bricked the router with this update.
Is there any way that I could restore the router?
Any help on this matter is much appreciated
Yes this is because you converted it to an E2000 and when you flashed "dd-wrt.v24-15230_NEWD-2_K2.6_mini-vlantest.bin" whereever thats at, it wasn't an E2000 specific build IE it didn't have E2000 or e2k-e3k in the name, so your unit is bricked, you can try recover with tftp, i've read a very few stories of it being fixed that way, or you can fix it via serial cable, which for me is %100 fix rate results. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
Also FYI you didn't need to use that test build because the changes already landed in build 15508 and higher. ie. you could have used the VLAN GUI with build 15943 you originally had.
There is still a bug if the WAN type is PPPoE that causes all VLAN settings to be ignored but it can be worked around...
http://svn.dd-wrt.com:8000/ticket/1930 _________________ 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)
Well as I said in the ticket it affected my wrt320n with build 15778 so it probably affects all builds after the GUI fix. There's a good chance that it might not affect builds prior to the GUI fix since without the kernel modules loaded it shouldn't be able to reconfigure VLAN's while it's running, but I don't care to check... _________________ 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)