Posted: Sun Dec 03, 2017 22:52 Post subject: Can't connect multiple Chromecasts/r33772 RT-N66U
Running an Asus RT-N66U using r33772 and cannot get my 3 chromecasts to connect at the same time. (Either 2.4 GHz or 5.0 GHz radio).
One can connect fine, but as soon as I add a 2nd one, both get kicked off and disappear leaving me unable to connect to them. The only fix is reboot one of them, which works fine until the 2nd one is rebooted.
The problem has been tracked-down to what I believe is a bug in the DD-WRT itself. That statement is based on subsequent downgrading flashing (clearing settings between). I walked through the list shown below until arriving at r33555 which works as expected.
r33772 = bad (dd-wrt.v24-33772_NEWD-2_K3.x-big-RT-N66U)
r33607 = bad (dd-wrt.v24-33607_NEWD-2_K3.x-big-RT-N66U.trx)
r33492 = bad (dd-wrt.v24-33492_NEWD-2_K3.x-big-RT-N66U.trx)
r33555 = good (dd-wrt.v24-33555_NEWD-2_K3.x-big-RT-N66U.trx)
Not sure how to help developers debug this. Was unable to see any errors from DD-WRT, just the chromecasts falling off the network.
Chromecast requires IPv6 and 33555 definitely broke IPv6 for a lot of people so clearly some messing about was done in the build with IPv6. If you go further backwards than 33492 does it work? Do you have IPv6 disabled?
Chromecast requires IPv6 and 33555 definitely broke IPv6 for a lot of people so clearly some messing about was done in the build with IPv6. If you go further backwards than 33492 does it work? Do you have IPv6 disabled?
If I am reading the OP's post correctly, r33555 is the one that works whereas newer ones do not work. If you're correct that the CCs require IPv6, I am a little confused by your reply. Can you provide a source to backup your statement that CCs require IPv6? I am using a single chromecast with it disabled and it works without issue.
I would suggest reset both the Chromecast and start over.
I have two connected ...both on the guests network never a problem thru many many builds ...then again I'm not using a brcm router... don't know that it matters.
No IPv6 here at all and currently everything goes thru dnscrypt DNS soooo the old myth about them needing Google DNS ain't true either
I did reset all chromecasts one at a time but that did not help. I just updated to r33986 but that killed the chromecasts. Downgrading back to r33555 fixed them so there is clearly something in the firmware causing this problem. I will post my settings if it helps, just need some time to get back home.
So something happened between r33555 and r33607... 52 commits to review. I don't know how to nor would I know what I'm looking at.
Yes, I agree. Is someone with expertise and a little time willing to review and give an opinion? I would like to open a TT but I have no relevant debugging info or a guess as to what might be the cause.
I can confirm that the issue is present in the E3000. I'm on build 34411 (Jan 7, 2018). I'm new to DD-WRT and I only installed it to fix the KRACK bug. I hope this gets fixed soon. The firmware has doubled my WAN speed.
FYI, my CC is connected and receiving software/screen image updates but seems to be isolated from other clients. I've performed a CC factory reset but once I reconnect it to the wireless network, I can no longer see/cast to it from any other device on my network (wired desktop included).