Yes I was using the gui because I thought that was the point.
Yep, that's the whole point of Eko's test build. #3 is strange and makes me think you should hard reset multiple times and then try again. It's also worth trying the nvram settings if the GUI still fails. _________________ 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)
Yes I was using the gui because I thought that was the point.
Yep, that's the whole point of Eko's test build. #3 is strange and makes me think you should hard reset multiple times and then try again. It's also worth trying the nvram settings if the GUI still fails.
My point is that the BCM539x gigabit switches may not have driver support for GUI vlan tagging in K26.
No one else in this thread has tested a K26 build with that switch.
BCM 539x routers are normally running K24, K26 routers have BCM53115 as gigabit switch, so is there support for BCM539x vlan GUI tagging in K26? _________________ Kernel panic: Aiee, killing interrupt handler!
I have successfully move a LAN port to WAN VLAN.
However, it is done by setting vlan.ports, not new_vlan.ports, new_vlan.ports does not work.
This is opposite to the previous findings.
Port assignemnt:
W 4 3 2 1 | Case labels
0 1 2 3 4 | NVRAM ports
Is some way you can provide pics of working examples? To my knowing, Atheros will not do VLANs by standard broadcom methods IE the same commands you use to do them in broadcom is not the same commands you use to do them in Atheros.
AFAIK Atheros has the ability to do VLANs, atleast with my WRT400N, the chips used in it, according to atheros site, states that it can in fact do VLANs both port and trunking, just do not know how to set that in atheros, and no, the webgui does not work for this. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
BS is talking about using 802.1q tagging with the kernel which is much more limiting. It won't allow you to do port based VLAN's so you'll still be stuck with all your LAN ports connected to each other. All it will allow is for you to tag an interface on the networking page so that the interface uses an 802.1q tag. You can then bridge the tagged interface with others so that their traffic gets trunked to another device.
This thread is more-so about hardware VLAN support to be able to do port based VLAN's. _________________ 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)
Yep, right. In K26 builds. But please be careful, I only tested on routers with bcm53115 switch and there it works. (I don't have any 5395, 5397, 5398 to test with.) So if you loss LAN, just flash back over wireless.
He posted a test build over a month ago but only a couple people have given feedback.
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=485277#485277 _________________ 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)
Ok, so far on the E2000, using the webgui works until i reboot, after a reboot though, it looses settings. I moved the WAN port into LAN, and port 4 of LAN moved to WAN, it did indeed function, until reboot :|
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Wed Oct 27, 2010 22:05 Post subject:
Ok, further testing today with the E2000 using 15508 produced success, even after reboot. I hard reset 2 times before testing again.
I moved the WAN port into LAN and it indeed functioned as a LAN port, then i rebooted, moved port 4 of then LAN into WAN and it functioned as a WAN port, once again, another reboot and nothing changed, seems to be working fine. All of this was of course performed from the webgui.
I also tested this on my converted WRT320N>E2000 and it also keeps the settings after reboot.
Yep, right. In K26 builds. But please be careful, I only tested on routers with bcm53115 switch and there it works. (I don't have any 5395, 5397, 5398 to test with.) So if you loss LAN, just flash back over wireless.
Does it mean that VDSL tagged VID7 may work? I could test it! :)
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)?