Can't connect multiple Chromecasts/r33772 RT-N66U

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Author Message
gothic
DD-WRT Novice


Joined: 03 Dec 2017
Posts: 5

PostPosted: Sun Dec 03, 2017 22:52    Post subject: Can't connect multiple Chromecasts/r33772 RT-N66U Reply with quote
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.
Sponsor
tedm
DD-WRT User


Joined: 13 Mar 2009
Posts: 281

PostPosted: Mon Dec 04, 2017 1:01    Post subject: Reply with quote
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?
thunderhead
DD-WRT User


Joined: 11 Nov 2017
Posts: 112

PostPosted: Mon Dec 04, 2017 19:44    Post subject: Reply with quote
tedm wrote:
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.

_________________
R7000 on DD-WRT v3.0-r35550M kongac (03/28/2018)
R7800 on LEDE 17.01.4
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 3512
Location: Texas

PostPosted: Mon Dec 04, 2017 20:17    Post subject: Reply with quote
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
gothic
DD-WRT Novice


Joined: 03 Dec 2017
Posts: 5

PostPosted: Tue Dec 05, 2017 1:09    Post subject: Reply with quote
Yes, no IPv6. Never had it, never will Smile

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.
thunderhead
DD-WRT User


Joined: 11 Nov 2017
Posts: 112

PostPosted: Tue Dec 05, 2017 1:19    Post subject: Reply with quote
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.
_________________
R7000 on DD-WRT v3.0-r35550M kongac (03/28/2018)
R7800 on LEDE 17.01.4
d0ug
DD-WRT User


Joined: 31 Jul 2015
Posts: 461

PostPosted: Tue Dec 05, 2017 1:27    Post subject: Reply with quote
tedm wrote:
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?


I am certain this is incorrect. I have 3 chromecasts and two google homes on my network. Lan is all IPV4 and my WAN is IPV4 as well. No issues with any of them working ever.

If this were the case many people would be unable to use chromecasts, as most ISPs in the US aren't giving out IPV6 IPs yet.

I have as of about an hour ago upgraded to r33986 and no issues are seen in this build, but it is on WRT1200AC hardware
gothic
DD-WRT Novice


Joined: 03 Dec 2017
Posts: 5

PostPosted: Wed Dec 06, 2017 19:55    Post subject: Reply with quote
thunderhead wrote:
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.
gothic
DD-WRT Novice


Joined: 03 Dec 2017
Posts: 5

PostPosted: Sun Dec 17, 2017 15:00    Post subject: Reply with quote
I just tested r34080 and got the same problem. Had to revert. Any debugging tips would be well appreciated.

gothic wrote:
DD-WRT v3.0-r34080 big (12/14/17)
Linux 3.10.108 #16936 Thu Dec 14 17:50:58 CET 2017 mips


http://svn.dd-wrt.com/ticket/6120
RobTheGob
DD-WRT Novice


Joined: 03 Jan 2018
Posts: 8

PostPosted: Wed Jan 03, 2018 18:26    Post subject: Reply with quote
I'm having similar issues with three E4200's on DD-WRT v3.0-r33986 mega (12/04/17).

In this thread https://www.dd-wrt.com/phpBB2/viewtopic.php?t=312795 it was indicated that the issue may also be in the E3000's.

For what it's worth - I added my comments to the TRAC bug.
RobTheGob
DD-WRT Novice


Joined: 03 Jan 2018
Posts: 8

PostPosted: Wed Jan 17, 2018 23:24    Post subject: Reply with quote
FYI - I rolled my three E4200's back to:

dd-wrt.v24-33525_NEWD-2_K3.x_mega-e4200.bin

And they've been working great ever since.
crowrt
DD-WRT Novice


Joined: 17 Jan 2018
Posts: 5

PostPosted: Fri Jan 19, 2018 21:37    Post subject: Reply with quote
[quote="RobTheGob"]
In this thread https://www.dd-wrt.com/phpBB2/viewtopic.php?t=312795 it was indicated that the issue may also be in the E3000's.
/quote]

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).
RobTheGob
DD-WRT Novice


Joined: 03 Jan 2018
Posts: 8

PostPosted: Fri Jan 19, 2018 21:46    Post subject: Reply with quote
RobTheGob wrote:
FYI - I rolled my three E4200's back to:

dd-wrt.v24-33525_NEWD-2_K3.x_mega-e4200.bin

And they've been working great ever since.


I read in another thread that r33525 didn't fix KRACK with BROADCOM chipsets - they required a slightly newer build, which breaks the Chromecasts!

So - since the KRACK fix is more important to me than the Chromecast, I've changed my E4200's to r34411...

I'm optimistic that the current "Google Play Services" fix may help - but I doubt it, it appears like a different issue.
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum