Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Thu Sep 02, 2010 3:32 Post subject:
Sheeeew, 4 for routers to go in my collection. Then I get to start all over again when phuzi0n explains 802.1q vlans. _________________ Peacock Thread-FAQ -- dd-wrt Wiki
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.
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Sat Sep 04, 2010 3:37 Post subject:
Confirmed working with the Asus WL-500gP v2. Before and after pics included. After moving port 3 into WAN port it of course no longer functioned like a LAN port.
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Sat Sep 04, 2010 13:15 Post subject:
Also ran tests and both Asus 500gp v2 and 520gU support 802.1q, so it does not matter about the E or F model of the chip, it was probably the users trying to do it from the webgui instead of the shell, which in most cases, the gui port arrangement is different per model, i have not even tried the webgui in any of my tests, so i could not tell you if it will work that. BTW I am using 14853 NEWD with no extra switch commands to get it working on those units.
Also with both those Asus units... ls /proc/switch does exist with eth0
At some point today i am going to test a 'real' E2000 and my RT-N16 and try 802.1q with those as well. Not to discredit those who have found it working with those units, but i am not going to edit the wiki entries for those unless i see it myself, but for those who are confident that it is indeed working for those units, feel free to add the info _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
When it comes to converted models they should be counted as whatever actual model they are and not what they've been converted to. It's possible that there's unknown hardware differences that could affect capabilities. _________________ 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: Sat Sep 04, 2010 22:41 Post subject:
phuzi0n wrote:
When it comes to converted models they should be counted as whatever actual model they are and not what they've been converted to. It's possible that there's unknown hardware differences that could affect capabilities.
Yes, such would be the case with the converted wrt320n into the e2000, as they have diff board revisions i am finding.
I am guessing diff board revisions due to the muck up on the reset button with the wrt320n. Nonetheless i am finding the E2000 supports VLANs just as the WRT320N does. Will post pics of tests after dinner with my family.
Also off topic, i am also guessing this is why some of the wrt320n boards do support reset button functionality, as i have read in the wrt320n supported post, some unit's reset button (which i am guessing is the 1305 revision) does work, others does not (probably the first run mucked up 1304 boards) _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
You should probably remove the insmod commands, they'll just waste nvram and RAM. On my wrt320n loading the modules creates the directory but the /proc/switch/[eth#]/vlan/[#]/ports files are empty and echoing port configurations to them doesn't have any affect. You can cat them and check if there's anything there but I doubt there will be. Also, afaict it's useless to load the modules unless you're going to change the port configuration live. _________________ 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)
To make dot1q trunking work with Cisco equipment you have to avoid using vlan1 in your trunk. Vlan1 is used as the management vlan in most Cisco routers and switches. I got dot1q trunking working with my Linksys routers, Cisco 870 router and Cisco SLM2008 switch using settings below. Basicly I have 2 seperate subnets, one in vlan3 and the other in vlan4.
On the SLM2008 switch I only had to add vlans 3 and 4 and make all ports a member. Then I set the PVID for all ports to vlan 4. This way a trunk can use any port, and a normal connection will be in vlan4