First and foremost, ignore this thread if you are not capable of and willing to follow instructions for this very specific test. As with any build, there is a chance that you may brick your router and need to recover it.
I asked Eko to update the switch-robo kernel module in k2.4 builds to match the version in k2.6 builds so that hopefully the VLAN GUI will work for all devices. The updated kernel module is primarily aimed at fixing the GUI for devices with BCM539x (gigabit) switches, but all devices that run k2.4 builds need testing to ensure that it doesn't cause any problems and to vet out any other devices that need the GUI fixed.
There have been reports of various problems in the k2.6 builds when the WAN type is PPPoE with this fix from r15507, but it did not affect the k2.4 devices that I tried with this test build. The problems on k2.6 builds include constant rebooting, loss of Ethernet connectivity (wireless still worked), and new VLAN settings being reverted on reboot. If you encounter any of these problems then a hard reset should regain access.
Now for the testing! Please follow these directions carefully and be very descriptive if you encounter problems. ie. say the exact hardware your using, exactly what you did, exactly what happened.
- Flash the router with the test build using standard upgrade procedures from the Peacock Announcement (hard reset!!!)
- Physically connect to one of the middle LAN ports of the switch.
- Access the WEB UI and set your new username and password.
- If you're testing on a BCM4704 based device then enable VLAN support immediately after flashing: http://www.dd-wrt.com/wiki/index.php/Enabling_VLAN_Support_for_BCM4704
- Telnet to the router and run lsmod to check if switch-core and switch-robo are even loaded and leave telnet open for later. If they are not loaded then the VLAN GUI may still work but any VLAN changes will likely not be applied after rebooting until you Apply something in the GUI again. This happened on my wrt300n v1.1 with the test build and has also happened to people using the recent k2.6 builds.
- Go to the VLAN page, uncheck port 1 from the LAN VLAN (VLAN 0 on 100mbit switches, VLAN 1 on gigabit switches), check port 1 in VLAN 3, and Apply.
- Wait 20 seconds and then go to the Networking page. In the Port Setup section make sure there is now a vlan3 interface listed.
- Set vlan3 to unbridged, assign it address 10.0.0.1/255.255.255.0, and Apply. In telnet run ifconfig vlan3 and check if the IP address was applied. If not then run ifconfig vlan3 10.0.0.1 netmask 255.255.255.0 to apply it (workaround for an unrelated Networking GUI bug).
- Add a new DHCP pool in the Multiple DHCP section, set it to vlan3, and Apply.
- Physically connect to LAN port 1 (an outer LAN port) on the router and see if your PC gets an IP in the 10.0.0.0/24 subnet. If you still get an IP in the 192.168.1.0/24 subnet then try connecting to LAN port 4 (the other outer LAN port) instead. If LAN port 4 gives an IP in the 10.0.0.0/24 subnet, then run nvram show | grep vlan.*ports in telnet and post the output to this thread so that the port numbering can be corrected.
- Go to the Basic Setup page, set the WAN type to PPPoE, and Apply. You do not actually need a PPPoE connection so don't worry if your ISP doesn't use it, just set it to PPPoE anyways.
- Check that you still have access to all LAN ports and that the port in VLAN 3 still gives an IP in the 10.0.0.0/24 subnet.
- Reboot the router and recheck all the LAN ports after it reboots.
- If the port in VLAN 3 no longer gives an IP in the 10.0.0.0/24 subnet (because the modules don't load for you?) then try to Apply the settings again and see if it starts working again.
- Hard reset, reconfigure it however you would for your normal use, and see if you encounter any problems related to the switch.
_________________ 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)
Last edited by phuzi0n on Fri Apr 22, 2011 1:31; edited 1 time in total
Everything worked fine except I had to manually assign an ip with 'ifconfig vlan3 10.0.0.1 netmask 255.255.255.0' because the gui didn't work.
Tested WRT350
Everything worked except I had to manually assign an ip until I tried to use the router after setting the WAN type to 'pppoe'. After that the router rebooted once and I couldn't connect to the router. Also, the wireless light was out.
Everything worked fine except I had to manually assign an ip with 'ifconfig vlan3 10.0.0.1 netmask 255.255.255.0' because the gui didn't work.
Tested WRT350
Everything worked except I had to manually assign an ip until I tried to use the router after setting the WAN type to 'pppoe'. After that the router rebooted once and I couldn't connect to the router. Also, the wireless light was out.
The forum reverted about a day and lost a couple posts here, so in case anyone missed it:
Bird333 said the test3 build worked fine on wrt350n (no more pppoe problem) but that unbridging still doesn't assign an IP right away.
I replied that rebooting will configure the IP correctly so that you don't have to use ifconfig, the bug (unrelated to this VLAN test) only prevents apply from working right away.
Eko, since you seem to have figured out the pppoe bug, could you please provide a k2.6 test build to try to fix pppoe on k2.6 too. _________________ 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)
Last time I attempted to setup a vlan, I had to reset to defaults as I could not access any of the ports.. _________________ Optware, the Right Way
Asus RT-AC68U
Asus RT-N66U
Asus RT-N10
Asus RT-N12
Asus RT-N16 x5
Asus WL520gU
Engenious ECB350
Linksys WRT600Nv1.1
Linksys WRT610Nv1
Linksys E2000
Netgear WNDR3300
SonicWall NSA220W
SonicWall TZ215W
SonicWall TZ205W
SonicWall TZ105W
Masterman you didn't say what all happened. _________________ 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: 24 Aug 2009 Posts: 2070 Location: South Florida
Posted: Thu Apr 28, 2011 12:54 Post subject:
phuzi0n wrote:
Masterman you didn't say what all happened.
I will attempt it again on another router later today. Basically I lost all communication to the router via LAN, WLAN and WAN. Had to do a physical hard reset of my RT-N16. I had no way of logging what happened, but I will attempt to do something about that this time.
It could be perhaps that I did not wait long enough for the change to take place (OTRW takes awhile to reload when a change such as this is performed).
I just don't like the idea of losing my main AP and not having a backup internet source for debugging. _________________ Optware, the Right Way
Asus RT-AC68U
Asus RT-N66U
Asus RT-N10
Asus RT-N12
Asus RT-N16 x5
Asus WL520gU
Engenious ECB350
Linksys WRT600Nv1.1
Linksys WRT610Nv1
Linksys E2000
Netgear WNDR3300
SonicWall NSA220W
SonicWall TZ215W
SonicWall TZ205W
SonicWall TZ105W
Do you recall when exactly you lost connectivity? ie. did PPPoE cause it?
Did you do all my tests before putting OTRW on it as instructed? _________________ 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 didnt make anything big. first i tried some version 15xxx and experienced this error we´re talkin about.
After this, i reverted to stock and than over linksys GUI to mini build of 14896.
Next step was upgrade to BIG version of 17084. Now i have no more problems with using pppoe and its consequences.
the bad thing is: my device ( wrt610n v1 ) has a overvoltage damage. port 1, 2 and WAN are not longer operational. i tried to setup port 4 act as WAN port. Looked good, i hadnt no access to the device through port 4 but still over port 3.
Actually the dialup process didnt work, maybe ´cause i need vlan7 dtag. my workaround didnt seem to work as at my wrt160n. but this is another story. the main thing i qould like to say is:
The device was still accessable using pppoe with last eko build. _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
the bad thing is: my device ( wrt610n v1 ) has a overvoltage damage. port 1, 2 and WAN are not longer operational. i tried to setup port 4 act as WAN port. Looked good, i hadnt no access to the device through port 4 but still over port 3.
Actually the dialup process didnt work, maybe ´cause i need vlan7 dtag. my workaround didnt seem to work as at my wrt160n.
Check that the the VLAN assignments are really working by plugging the port 4 into something with a DHCP server like another router, or assign the WAN a static IP in a different subnet than the LAN IP like 10.0.0.1/24 and connect port 4 to a PC with a static IP in that same subnet. You should then be able to ping from behind the router to the device plugged into port 4. _________________ 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)
Check that the the VLAN assignments are really working by plugging the port 4 into something with a DHCP server like another router..
then i have to setup dhcp instead of pppoe, i guess ?
but this is only for testing, with only two lan ports and no wan port, i cant use this unit at home. my hope is a known friend can fix my 3 lost ports. looks a little burned my unit
btw i have now kernel 2.4 installed. _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
Last edited by BasCom on Fri Jun 10, 2011 22:16; edited 1 time in total
then i have to setup dhcp instead of pppoe, i guess ?
If you're plugging it into something with a DHCP server then yes, set the WAN type to DHCP. _________________ 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)