Posted: Sun Jan 07, 2018 13:16 Post subject: "AP Isolation" always active
I'm using the firmware DD-WRT v3.0-r34311 mega (12/29/17) on an Asus RT-N66U.
Under Wireless - Basic Settings a Virtual Interface (wl0.1) is created for a seperate WiFi network. The option "AP Isolation" is set to "Disable".
Even with AP Isolation set to disable, the devices in the WiFi cannot reach each other.
Any ideas? Where can I check inside the DD-WRT Linux system if the option is set correctly? (for the case it is only an issue with the visualization)
I am running Firmware: DD-WRT v3.0-r34311 big (12/29/17) on an Asus RT-N66U. I appear to be having the exact same issue as you are having. This was not an issue with the previous version of ddwrt I had on there (a couple years old). I have tried disabling/enabling/re-disabling AP isolation. It also appears to be a *bit* sporadic. I can occasionally ping some devices on the wireless network just after the router boots, and can sometimes even operate my Sonos speakers, but anything that uses multicast is totally out, and I cannot connect between devices via ssh/anything else I have tried.
It is a bit frustrating to debug since *sometimes* a few pings will make it to some random subset of devices, and then not a few minutes later, or after another reboot. All devices appear to have no issue connecting out to the internet.
I'm also running 34311 on an RT-AC66U, and I can confirm that AP isolation appears to be occurring; I can't cast to my Chromecast (on my 2.4GHz AP) from my laptop (on my 5GHz AP). If my laptop connects to my 2.4GHz network, casting works fine.
I'm running v3.0-r34411 mega on e3000 and also cannot cast to my chromecast, even after rebooting both devices. HP wireless printer goes offline while wifi connection is maintained and nothing in sys/kern logs. The chromecast gets its weather updates and wallpapers, just can't cast to it on the network.
Just an update with the things I tried recently - The entire point of the upgrade was to join the world of devices not vulnerable to KRACK, however, I tried each and every build since the one that fixed KRACK (that were supported for my device) - and each one of them failed to allow my devices on wifi to chat with each other. I also tried a couple from the Oct '17 timeframe before the KRACK patch, also... no luck.
Finally I jumped *all* the way back to the Aug 3 build, and that works. Unfortunately.. I guess that (or maybe I can find a slightly newer one) is where I will have to stay since none of the KRACK fixed versions allow my network to work
Wanted to post in case anyone else wants to fall back - since the aug 3 versions actually DO WORK.
I can confirm that the same issue occurs on my Linksys E2500 v3 with build dd-wrt.v24-34311_NEWD-2_K3.x_mega-e2500.bin. Weirdly, I found that if I disconnected any two devices from the wireless lan and then reconnected both of them, each of those two devices could reach the other without problems for usually an hour or two; then all of a sudden pings to any wireless client on the lan resulted in "Destination Host Unreachable" even though they all still showed up in the webGUI's list of active clients. If memory serves, I did not have this problem with devices that had a wired ethernet connection to the router (to be expected I guess, if it's somehow AP isolation-related). My (port forwarded) LAMP server remained accessible from the public internet throughout all this, and all devices had outgoing internet access with no issues. AP isolation was turned off in the GUI and nvram show | grep _ap_isolate returned wl0.1_ap_isolate=0.
As others have said, downgrading to build dd-wrt.v24-33006_NEWD-2_K3.x_mega-e2500.bin fixed this issue and seems to be running fine. I haven't tried any builds more recent than that.
I recently installed DD-WRT on my Linksys E3000 to fix the KRACK bug. I previously had other custom firmware installed.
Everything seemed to be working perfectly but yesterday I realized could not access my Chromecast. It has been connected to the network since I set everything up. It has Internet access and is receiving screen/version updates. However, I can't access it from the Google Home app or any other device on my network.
I've changed every setting I can think of and just when I think I have the issue fixed, the Chromecast disappears again. It could be an AP isolation issue but my gut tells me it's a multicast issue. I've tried IGMP snooping but it doesn't help.
Does anyone have any ideas about what the exact issue is and/or how to fix it?