RT-AX86U and network issue or ISP (Rogers) Issue?

[Keyser-_-soze]

Hi there,

We have had major issues working from home, with connections dropping. We think it's Rogers (ISP), but proving it to them has been hard. Another tech is coming to our home at the end of the week, and I would like to have some more evidence for them.

I do not believe our router(s) are causing the issue. I have removed all the nodes from Mesh and only had the main AX86 running, but I still have issues.
We get many of these post in the router logs:

Oct 16 11:22:01 WAN_Connection: WAN was restored.​

Oct 16 11:32:39 WAN_Connection: WAN was restored.​

Oct 16 11:46:10 WAN_Connection: WAN was restored.

Here is a snapshot of the info around one of these posts, does anything here show that it's my network or the ISP service?

Oct 16 11:44:14 wlceventd: wlceventd_proc_event(662): eth6: Disassoc EC:DA:3B:A6:AB:B8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0[/INDENT]
[INDENT]Oct 16 11:44:59 roamast: sta[FE:9A:9C:91:77:85] on ap[24:4B:FE:30:16:48], rcpi is 122 and rssi is -49[/INDENT]
[INDENT]Oct 16 11:45:05 roamast: sta[FE:9A:9C:91:77:85] on ap[24:4B:FE:30:16:48], rcpi is 118 and rssi is -51[/INDENT]
[INDENT]Oct 16 11:45:16 roamast: sta[FE:9A:9C:91:77:85] on ap[24:4B:FE:30:16:48], rcpi is 120 and rssi is -50[/INDENT]
[INDENT]Oct 16 11:45:21 roamast: sta[FE:9A:9C:91:77:85] on ap[24:4B:FE:30:16:48], rcpi is 122 and rssi is -49[/INDENT]
[INDENT]Oct 16 11:45:34 roamast: sta[FE:9A:9C:91:77:85] on ap[24:4B:FE:30:16:48], rcpi is 120 and rssi is -50[/INDENT]
[INDENT]Oct 16 11:45:38 roamast: sta[FE:9A:9C:91:77:85] on ap[24:4B:FE:30:16:48], rcpi is 120 and rssi is -50[/INDENT]
[INDENT]Oct 16 11:45:44 roamast: sta[FE:9A:9C:91:77:85] on ap[24:4B:FE:30:16:48], rcpi is 122 and rssi is -49[/INDENT]
[INDENT]Oct 16 11:45:55 roamast: sta[FE:9A:9C:91:77:85] on ap[24:4B:FE:30:16:48], rcpi is 122 and rssi is -49[/INDENT]
[INDENT]Oct 16 11:45:59 roamast: sta[FE:9A:9C:91:77:85] on ap[24:4B:FE:30:16:48], rcpi is 122 and rssi is -49[/INDENT]
[INDENT]Oct 16 11:46:09 roamast: sta[1A:46:A4:2F:7F:1B] on ap[24:4B:FE:30:16:48], rcpi is 94 and rssi is -63[/INDENT]
[INDENT]Oct 16 11:46:10 WAN_Connection: WAN was restored.[/INDENT]
[INDENT]Oct 16 11:46:10 dnsmasq[23263]: read /etc/hosts - 24 names[/INDENT]
[INDENT]Oct 16 11:46:10 dnsmasq[23263]: using nameserver 8.8.8.8#53[/INDENT]
[INDENT]Oct 16 11:46:10 dnsmasq[23263]: using nameserver 8.8.4.4#53[/INDENT]
[INDENT]Oct 16 11:46:10 dnsmasq[23263]: using only locally-known addresses for mask-h2.icloud.com[/INDENT]
[INDENT]Oct 16 11:46:10 dnsmasq[23263]: using only locally-known addresses for mask.icloud.com[/INDENT]
[INDENT]Oct 16 11:46:10 dnsmasq[23263]: using only locally-known addresses for _dns.resolver.arpa[/INDENT]
[INDENT]Oct 16 11:46:10 dnsmasq[23263]: using only locally-known addresses for use-application-dns.net[/INDENT]
[INDENT]Oct 16 11:46:10 dnsmasq[23263]: using nameserver 8.8.8.8#53[/INDENT]
[INDENT]Oct 16 11:46:10 dnsmasq[23263]: using nameserver 8.8.4.4#53

Thank you for the help!

 

[Tech9]

Rogers won’t care much what your router’s log is saying. What is the modem’s log saying? I have CODA56 on Rogers cable and current modem uptime is 1.5 months or since it was installed.

 

[Keyser-_-soze]

Thank you, What logs would be the best to help identify network drops?

Event or System? Or are these logs not capturing disconnects?

rogers has identified that they are losing packets and have come out a few times trying different things, but never seem to get to the root of the issue.

 

[Tech9]

Most likely there will be indication for lost sync, when and for how long. Rogers tech support sees the modem stats and will fix the line if the problem is on their end.

 

[Keyser-_-soze]

Ok, thank you. I have gotten some good techs (via chat) who say they can see it's bad and others who say they can't since it's in bridge mode.

so I was just trying to compile my own information - since I have already done so much past their modem to fix the issues - new routers, only one device connected to remove some IOT device or switch causing the issue, but everything seems to point to it being their issue.

 

[Tech9]

Run your ISP device in Gateway mode and see if the issue is still there. If it disappears - it's your router.

RT-AX86U-Pro, WAN disconnect every 36 hours

Try the suggested above change - ISP Gateway in Router mode. I'm surprised you never tried it by now. Your Asus router is most likely the issue. Some folks around replaced their own router with different brand/model after fighting with the same issue for months just like you.

www.snbforums.com

Unfortunately, Asus routers are known for WAN issues, most likely modem to router compatibility related.

 

[Keyser-_-soze]

Thank you so very much for this! It really helped reduce our daily drop rate to one or two drops from double digits.

I changed the Modem to Gateway mode, and the WAN issues stopped; I left the AX connected to the Gateway using the same ports.

Then, I took one of my AC86U nodes and made it the new main Router with the Rogers Modem still in Gateway mode. There are still no disconnects.

Put Modem/Router into Bridge mode, Leaving the AC86U connected—still no WAN drops.

Lastly, I added the AX back into the mix as a Hardware mesh node, and everything works great.

Other than not utilizing my full downstream bandwidth, I will take a fairly stable connection (only 2 disconnects a day) over unnecessary speed any day!!


From these steps, it does seem like a compatibility issue between the AX and the Rogers Modem, but only in Bridge mode. Does that make sense? It does not seem like the AX's WAN port is defective, as it works great as a Hardwired Node and worked well played well when I used the Rogers modem in Gateway mode. Thoughts?

Or maybe it's all a coincidence, and they fixed something on Rogers's end! LOL.

 

[Tech9]

Does that make sense?

Yes, similar issues were reported with different ISP equipment to different models Asus routers. DHCP Query Frequency change (in firmware), modem replacement (when modem is suspected), modem/router in Gateway mode (some Gateways are more stable this way), switch between the ISP equipment and the router (when port incompatibility is suspected), own router replacement with different brand and model (last resort)... I've seen all possible fixes or workarounds mentioned. Glad you found what works better in your case.

 

[Don Draper]

Rogers ISP as well. Had them come out twice, new modem etc etc. Exchanged Asus router for a new one - same issues. Disabling AiCloud 2.0 has "so far" fixed all issues. I have had a solid connection for 24hrs now. Not sure why ...but it's worked for now.

 

[Tech9]

Disabling AiCloud 2.0 has "so far" fixed all issues.

Perhaps related to this recently discovered issue and not the ISP?

RT-AX88U maxing out a core and regularly showing 60+ MB/s upload

I had Diversion and Skynet running but have since disabled them, suspecting that may be the culprit. Essentially, I can't see any device connected to my network that is sending large amounts of data, but when I look at the traffic monitor (Analyzer) it shows this: I only have ~30Mbps of...

www.snbforums.com

 

[Don Draper]

Perhaps related to this recently discovered issue and not the ISP?

RT-AX88U maxing out a core and regularly showing 60+ MB/s upload

I had Diversion and Skynet running but have since disabled them, suspecting that may be the culprit. Essentially, I can't see any device connected to my network that is sending large amounts of data, but when I look at the traffic monitor (Analyzer) it shows this: I only have ~30Mbps of...

www.snbforums.com

Very likely.

 

[Keyser-_-soze]

Rogers ISP as well. Had them come out twice, new modem etc etc. Exchanged Asus router for a new one - same issues. Disabling AiCloud 2.0 has "so far" fixed all issues. I have had a solid connection for 24hrs now. Not sure why ...but it's worked for now.

Thanks for this; I did not have it on, but I was thinking about using AiCloud since it was there. I will hold off, and I don't want to introduce a new issue now that I am finally stable lol. *knock on wood*