I can not change the wan interface.
Does not change either through a Web interface or via the nvram. After rebooting all the value is the default.
failed to add another vlan ports through a Web interface. _________________ Ищу работу системным администратором UNIX/BSD
Posted: Wed Feb 02, 2011 2:00 Post subject: Thanks to buddee and all others on this forum
I just want to say thanks for the info that has been posted on this forum, specifically by buddee, about flashing an E2000 with dd-wrt and then configuring it to be more effective and cooler running. I configured mine last night off-line, ran the changes to tx power and cpu clock via SSH, tweaked a few other items (something new and cool for me), and swapped out my faithful and much-loved WRT-54GL this morning. Sweet, smooth and highly efficient ("excellent" reception throughout a 2200sqft home). Now I just need to find 5ghz adapters for all my toys and I can really make things run swiftly. It did clear up the netflix buffering issue which was one of the main reasons for getting the e2000 in the first place.
Posted: Thu Feb 03, 2011 14:06 Post subject: AP isolation
If I enable AP Isolation on a virtual interface wl0.1 with WPA2-Enterprise security
I assign wl0.1 as well as vlan3 to a br1 interface
I set lan port 4 as tagged 1 and 3
I connect port 4 to a tagged 1 and 3 port in a managed switch
I connect a RADIUS server to a switch port untagged vlan ID 3
wireless clients are UNABLE to authenticate.
If I just disable AP Isolation on the virtual interface wl0.1
all works fine.
Why is that?
I'm running DD-WRT v24-sp2 (10/26/10) mega - build 15508M NEWD-2 K2.6 Eko on a Linksys E3000.
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Thu Feb 03, 2011 17:51 Post subject:
I tried AP isolation with:
DD-WRT v24-sp2 (12/19/10) mega - build 15943M NEWD-2 K2.6 Eko
and I'm still having trouble with WPA2-Enterprise because it's "so isolated" that the AP cannot proxy the authentication request/reply to the Radius server in my LAN.
I believe this is a bug. AP isolation should block all traffic except packets that are meant for authentication.
If an external radius server is not used then AP isolation works as expected.
Is there any way of fixing this somehow? Is it expected behavior or am I doing something wrong?
All AP isolation does is keep wireless users from seeing each other, IE they can browse or share files through any explorer type interface between themselves, they can still see your LAN if you have shares etc setup, just can't see each other over wireless.
I am unsure where the rest of your radius problems are at, but AP isolation doesn't do much except what i listed.
I now understand what AP isolation is and it's what I thought it was, thanks.
I don't have any Radius-specific problems at all but I would like to know if someone can reproduce this so-called bug:
just setup an SSID with WPA2-Enterprise and specify a Radius server in your LAN. Then enable AP isolation for this SSID.
If your wireless clients can't authenticate with AP isolation enabled but CAN if you disable AP isolation then you're hitting the same bug/feature that I am.
Try performing a 30/30/30 and then connect it to your machine via ethernet (any LAN port to your network card), then set a static IP and Subnet of 192.168.1.145 / 255.255.255.0 and then see if you can ping 192.168.1.145. If you can then:
Get the original FW from Linksys.com for your device and use the TFTP utility
pw: admin (I believe)
Then flash back to the appropriate dd-wrt FW after that is successfull.
***When flashing: USE ONLY THE ONES THAT HAVE E3000 or E2000 AT THE END OF THE FILENAME, NOTHING ELSE!!