I have the same issue with other devices, Nest, Alexa, Dyson fans, to name but a few.
Exactly the same issue and results.
In some dire need of assistance (AX86U)
- Thread starter shadowfiber
- Start date
I have the same issue with other devices, Nest, Alexa, Dyson fans, to name but a few.
Exactly the same issue and results.
KsWoodsMan
Regular Contributor
What did your DNS logs show for these clients ?
Any blocked domains ? especialy blocked google gomains ? or amazon-aws ?
Nothing in DNS at all to show any issues.
It was all about these devices not managing to renew their IPs from DHCP
KsWoodsMan
Regular Contributor
Was the checking done on the router ?
Or the dns logs on the pihole ?
To me this would seem more like a finicky set of client devices, rather than a flakey connection to them.
One person mentioned his devices in question will go 2 -5 days without a problem before they all seem to go down about the same time. Coincidence ?
Last edited:
My DNS/DHCP is on a Windows PC, DNS logs are the windows ones and my wired devices dont have the issue.
Maybe the 2~5 days could be something to do with the DHCP lease time.
KsWoodsMan
Regular Contributor
Or the time it takes to fill up their filesystem with conversations it's been eves dropping on.
One of the comonalities does seem to be that DNS is not being served from the router itself
and DNS filtering/protection is taking place on the local network.
I may be going in the wrong direction but thought to add it to the possibilities of things to address.
Last edited:
Not quite sure what you mean by filling up file systems and eves dropping on what ?
Well, I can see nothing DNS here, it all seems to be DHCP and the fact that devices cannot get IPs allocated to them.
I can even see this on a phone on my guest network, it will attempt to attached to the network, but never gets an IP from the DHCP server and there is nothin in the logs showing an attempt has even been made to get an IP address.
KsWoodsMan
Regular Contributor
I missunderstood you then that
you were having the same problem with your google devices and the ones listed.
evesdropping ... if it has a microphone or a mic and camera it has the capacity to record and store/forward anything within it's range.
I might be a bit paranoid over this.
But then again I might not be paranoid enough.
I do hope someone is able to figure it.
I'm out.
you were having the same problem with your google devices and the ones listed.
evesdropping ... if it has a microphone or a mic and camera it has the capacity to record and store/forward anything within it's range.
I might be a bit paranoid over this.
But then again I might not be paranoid enough.
I do hope someone is able to figure it.
I'm out.
shadowfiber
Regular Contributor
My devices were running over 7 days with no issues - then all of a sudden all lost connectivity around the same time. Router doesn't report any issue other than the DHCP offer's again. It's been stable for 16 days on Merlin Beta 4.
Sigh
Sigh
shadowfiber
Regular Contributor
Beta 5 - even worse - disconnects every few hours again.
shadowfiber
Regular Contributor
I don't feel like it's very customized...
Wired house - to a patch panel - goes into an unmanaged D-Link 24port switch ... Router plugged into that... along with a NAS that has a pihole docker container for DNS. Removed the pihole completely for testing - no change... So to me, its a bunch of devices and nothing special. Open to suggestions and thoughts though!!
The Router is Merlin firmware with no addons or plugins or customized scripts.
L&LD
Part of the Furniture
Pihole docker sounds pretty 'advanced' to me.
The router's LAN port is plugged into the switch, or the WAN?
Have you tried powering down the entire network? All infrastructure and wired clients too, for at least 10 - 20 minutes?
I would disconnect all power cords, adaptors, Ethernet cables, USB cables and devices from all equipment after the power was off. And plug, connect and attach everything before you powered up the network again.
How much do you trust that switch? Maybe test by powering it off and on first (as quick test).
Maybe test with a couple of new cables too from the WAN and the LAN. While you're at it, try different LAN ports too (if you're only using one to the switch).
Try different WAN port too, by making a LAN port for WAN.
The router's LAN port is plugged into the switch, or the WAN?
Have you tried powering down the entire network? All infrastructure and wired clients too, for at least 10 - 20 minutes?
I would disconnect all power cords, adaptors, Ethernet cables, USB cables and devices from all equipment after the power was off. And plug, connect and attach everything before you powered up the network again.
How much do you trust that switch? Maybe test by powering it off and on first (as quick test).
Maybe test with a couple of new cables too from the WAN and the LAN. While you're at it, try different LAN ports too (if you're only using one to the switch).
Try different WAN port too, by making a LAN port for WAN.
shadowfiber
Regular Contributor
Great suggestions and thoughts; I'd like to pass one piece back to you though that may have been missed from the beginning. (before I do them)
If I put the AC66U (non b1) back into place. Everything works fine.
Makes me think that the switch, the pihole, the everything else is fine; and there's something with the router. Let me know if you think I may be missing something there.
L&LD
Part of the Furniture
I don't think you answered my question(s)? 
Nothing is fine until proven otherwise. Working 'okay' with other equipment doesn't automatically get a 'pass' with new hardware in the loop.
Can you give us a sketch/drawing of the way everything is wired? It will answer the questions I asked and be easier to visualize any other issues too.
Nothing is fine until proven otherwise. Working 'okay' with other equipment doesn't automatically get a 'pass' with new hardware in the loop.
Can you give us a sketch/drawing of the way everything is wired? It will answer the questions I asked and be easier to visualize any other issues too.
This is the essence of it.
384 has no issues with Google home minis or Sonos. 386 is broken for them.
No setting is going to fix that and as Merlin mentioned, the wifi code is closed source, so it's going to be the same regardless of whether stock firmware or merlinwrt.
Doesnt sound like Asus have had any luck in fixing it in a couple of months of people reporting it.
Plausible it could get fixed in future firmware, but no guarantees. So I guess the options are to either run old 384 firmware, get rid of the devices it can't handle, or use a different router.
ColinTaylor
Part of the Furniture
@shadowfiber Did you ever work out what was causing these crashes?
SenorClean
New Around Here
Glad to hear I'm not alone, but I'm pulling my hair out here too.
Have been running an RT-AC68U for about 6 years, just upgraded to an AX86U this week and of course flashed it with Merlin firmware before doing anything else.
It's generally running well, but crazy unstable with the nest minis.
I've tried every trick I could find mentioned in here (Shift to 2.4ghz, remove AImesh, manually assigned IP with unique hostname) - nothing seems to solve it. My Plan B is to plug in an old router and run a dedicated AP for them - hardly elegant, but I'm running out of options.
EDIT: I think I've solved it - I had DNS over TLS enabled with the 'Strict' profile - shifting to Opportunistic (or disabling DOT) seems to fix it. Maybe there's some sort of phoning home that was being blocked?
Have been running an RT-AC68U for about 6 years, just upgraded to an AX86U this week and of course flashed it with Merlin firmware before doing anything else.
It's generally running well, but crazy unstable with the nest minis.
I've tried every trick I could find mentioned in here (Shift to 2.4ghz, remove AImesh, manually assigned IP with unique hostname) - nothing seems to solve it. My Plan B is to plug in an old router and run a dedicated AP for them - hardly elegant, but I'm running out of options.
EDIT: I think I've solved it - I had DNS over TLS enabled with the 'Strict' profile - shifting to Opportunistic (or disabling DOT) seems to fix it. Maybe there's some sort of phoning home that was being blocked?
Last edited:
shadowfiber
Regular Contributor
Hey there,
I wouldn't say it's "FIXED" per se, but the frequency of the issues has drastically reduced. Generally all the mini's will drop off the network once a month, need a reset and be good to go for another month. DNS over TLS hasn't resolved it permanently for me as it has for @SenorClean unfortunately. I have shifted everything to Quad9 with DNSSEC as my primary outbound through the pihole at this point. The amount of "phoning home" has been ridiculous, now i have a good handle on how frequently the minis speak to Google's servers, and it's quite ridiculous. Unfortunately, they all dropped off again yesterday. /rollseyes
Regardless, once a month is better than several times a day, the only thing I can contribute that for at this point is firmware changes.
ColinTaylor
Part of the Furniture
Thanks for the update @shadowfiber. I recently got an RT-AX86U also and am seeing the same crashes. In my case one of the trigger conditions is if radar is detected and the router changes the 5GHz WiFi channel. That always results in an endless loop of crashing.
Similar threads
Similar threads
Similar threads
-
Need help with bwdpi command
- Started by leoxp9515
- Replies: 0
-
Desperate need for help, packet loss on Asus ax11000, no solution.
- Started by Mittenz
- Replies: 10
-
ASUS XT8 w/ 2.5G multigig switch +XT8 nodes not working (need help)
- Started by Moaf
- Replies: 3
-
Need help designing & building AIMESH system
- Started by Osage
- Replies: 11
-
Late to the Squarespace domain cutover, need a new DDNS solution...
- Started by SolidSonicTH
- Replies: 9
-
-
Asus DSL-AX82U problems need tech help please
- Started by SamT98
- Replies: 24
-
Fios, AXE11000 2 pack, TP link switch, and do I need vlan iptv?
- Started by Nelson57
- Replies: 8
-
Need help getting RT-AX86U set up.
- Started by Malini
- Replies: 19