What's new

Desperate: Internet keeps crapping out. Need help understanding System log

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

mac_angel

Regular Contributor
I've been having problems with my Internet for a long time now. I bought a new Asus RT-AX86U, and tried the new firmware. Lately it seems I'm having even more issues and I noticed that when I start to have problems, a bunch of log entries show up in the General Log, but I have no idea what they mean. It does seem to be network related, not Internet specifically because I noticed that sometimes when things start acting funky, I tried logging into the Asus router to check the logs, and it won't let me log in either; the page times out. This is with a wired connection, and when I look at my connection status within Windows, it shows that I am still connected, and for X amount of time (so no recent re-connections). What's also odd is that I have a server in the basement for Plex, and I use Windows Remote Access for it all the time. I sometimes lose connection with that, but not all the time (Internet will give me problems, can't log into the Asus router, but I'm still connected to the server). And other times, will connected to it, it will be extremely slow, even though it says the connection is excellent.
This is a bit, copy and pasted from the log:

Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 16 tid 3
Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 16 tid 4
Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 16 tid 5
Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 16 tid 6
Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 16 tid 7
Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1: random key value: 77ECC50855DFF6151CC60129AC954586E255E5C8DEEB03208C4BA98D8E79B476
Dec 26 13:12:04 kernel: CONSOLE: 326074.106 wl1: wlc_txbf_delete_link_serve failed for 14:f6:d8:d8:6f:a3
Dec 26 13:12:04 kernel: CONSOLE: 326074.111 iov:SCB_DEAUTH
Dec 26 13:12:04 kernel: CONSOLE: 326074.112 iov:SCB_DEAUTH
Dec 26 13:12:05 wlceventd: wlceventd_proc_event(505): eth7: Auth 14:F6:D8:D8:6F:A3, status: Successful (0)
Dec 26 13:12:05 wlceventd: wlceventd_proc_event(534): eth7: Assoc 14:F6:D8:D8:6F:A3, status: Successful (0)
Dec 26 13:12:05 kernel: CONSOLE: 326075.336 wlc_ap_authresp: status 0
Dec 26 13:12:05 kernel: CONSOLE: 326075.336 wl1: turn sta MFP setting on with sha1
Dec 26 13:12:05 kernel: CONSOLE: 326075.337 wlc_ap_process_assocreq_done status 0
Dec 26 13:12:05 kernel: CONSOLE: 326075.337 wl1: STA 14:f6:d8:d8:6f:a3 has associated tx_type 2
Dec 26 13:12:05 kernel: CONSOLE: 326075.339 iov:SCB_DEAUTH
Dec 26 13:12:05 kernel: CONSOLE: 326075.340 tx:prep:802.1x
Dec 26 13:12:05 kernel: CONSOLE: 326075.343 tx:prep:802.1x
Dec 26 13:12:05 kernel: CONSOLE: 326075.631 iov:SCB_AUTH
Dec 26 13:12:05 kernel: CONSOLE: 326075.672 wl1: wlc_is_publicaction: rx frame has category 9, pub action field 0; should have cat 4
Dec 26 13:12:05 kernel: CONSOLE: 326075.672 wl1: wlc_recvfilter: bad frame control 0x40d0
Dec 26 13:12:06 kernel: CONSOLE: 326075.692 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 0
Dec 26 13:12:07 kernel: CONSOLE: 326076.539 wl1: 14:f6:d8:d8:6f:a3: addba timed out 0
Dec 26 13:12:07 kernel: CONSOLE: 326076.539 wl1: 14:f6:d8:d8:6f:a3: addba timed out 0
Dec 26 13:12:07 kernel: CONSOLE: 326076.539 wl1: 14:f6:d8:d8:6f:a3: addba timed out 0
Dec 26 13:12:07 kernel: CONSOLE: 326076.540 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x3 tid 6
Dec 26 13:12:07 kernel: CONSOLE: 326077.513 wl1: 14:f6:d8:d8:6f:a3: addba timed out 1
Dec 26 13:12:07 kernel: CONSOLE: 326077.513 wl1: 14:f6:d8:d8:6f:a3: addba timed out 1
Dec 26 13:12:07 kernel: CONSOLE: 326077.514 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x2 tid 5
Dec 26 13:12:08 kernel: CONSOLE: 326077.620 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 1
Dec 26 13:12:08 kernel: CONSOLE: 326078.291 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 3
Dec 26 13:12:08 kernel: CONSOLE: 326078.487 wl1: 14:f6:d8:d8:6f:a3: addba timed out 2
Dec 26 13:12:08 kernel: CONSOLE: 326078.490 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x0 tid 2
Dec 26 13:12:09 kernel: CONSOLE: 326079.272 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 4
Dec 26 13:12:09 kernel: CONSOLE: 326079.406 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 7
 
The most recent Asus firmware is: Version 3.0.0.4.384.9318
There is also an Asus beta at: https://drive.google.com/drive/folders/1D4X3k9GXxkiRQkaO1huQGnCAsQeIvokC just be sure to pick the correct model nimber
There is also a custom Merlin beta at: https://www.snbforums.com/threads/asuswrt-merlin-386-1-beta-is-now-available.68205/

The standard recommendation for router issues is to do a hard factory reset. See: https://www.asus.com/support/FAQ/1039074/ and use Methos 2
After a hard factory reset configure the router manually. Do not use saved settings. You may want to use a different SSID and set the 2.4 and 5 GHZ bands to fixed channels.

As for the beta firmwares, the Asus beta may fix some of the stability issues you are having. The Merlin firmware is also good but still being worked on. Merlin's firmware will give you some great options.
 
The most recent Asus firmware is: Version 3.0.0.4.384.9318
There is also an Asus beta at: https://drive.google.com/drive/folders/1D4X3k9GXxkiRQkaO1huQGnCAsQeIvokC just be sure to pick the correct model nimber
There is also a custom Merlin beta at: https://www.snbforums.com/threads/asuswrt-merlin-386-1-beta-is-now-available.68205/

The standard recommendation for router issues is to do a hard factory reset. See: https://www.asus.com/support/FAQ/1039074/ and use Methos 2
After a hard factory reset configure the router manually. Do not use saved settings. You may want to use a different SSID and set the 2.4 and 5 GHZ bands to fixed channels.

As for the beta firmwares, the Asus beta may fix some of the stability issues you are having. The Merlin firmware is also good but still being worked on. Merlin's firmware will give you some great options.

Forgot to mention, I've tried the latest Asus firmware, as well as running the latest from Merlin. I do get that it's in Beta, but I still don't know what those logs mean.
 
I've been having problems with my Internet for a long time now. I bought a new Asus RT-AX86U, and tried the new firmware. Lately it seems I'm having even more issues and I noticed that when I start to have problems, a bunch of log entries show up in the General Log, but I have no idea what they mean. It does seem to be network related, not Internet specifically because I noticed that sometimes when things start acting funky, I tried logging into the Asus router to check the logs, and it won't let me log in either; the page times out. This is with a wired connection, and when I look at my connection status within Windows, it shows that I am still connected, and for X amount of time (so no recent re-connections). What's also odd is that I have a server in the basement for Plex, and I use Windows Remote Access for it all the time. I sometimes lose connection with that, but not all the time (Internet will give me problems, can't log into the Asus router, but I'm still connected to the server). And other times, will connected to it, it will be extremely slow, even though it says the connection is excellent.
This is a bit, copy and pasted from the log:

Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 16 tid 3
Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 16 tid 4
Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 16 tid 5
Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 16 tid 6
Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 16 tid 7
Dec 26 13:12:04 kernel: CONSOLE: 326074.105 wl1: random key value: 77ECC50855DFF6151CC60129AC954586E255E5C8DEEB03208C4BA98D8E79B476
Dec 26 13:12:04 kernel: CONSOLE: 326074.106 wl1: wlc_txbf_delete_link_serve failed for 14:f6:d8:d8:6f:a3
Dec 26 13:12:04 kernel: CONSOLE: 326074.111 iov:SCB_DEAUTH
Dec 26 13:12:04 kernel: CONSOLE: 326074.112 iov:SCB_DEAUTH
Dec 26 13:12:05 wlceventd: wlceventd_proc_event(505): eth7: Auth 14:F6:D8:D8:6F:A3, status: Successful (0)
Dec 26 13:12:05 wlceventd: wlceventd_proc_event(534): eth7: Assoc 14:F6:D8:D8:6F:A3, status: Successful (0)
Dec 26 13:12:05 kernel: CONSOLE: 326075.336 wlc_ap_authresp: status 0
Dec 26 13:12:05 kernel: CONSOLE: 326075.336 wl1: turn sta MFP setting on with sha1
Dec 26 13:12:05 kernel: CONSOLE: 326075.337 wlc_ap_process_assocreq_done status 0
Dec 26 13:12:05 kernel: CONSOLE: 326075.337 wl1: STA 14:f6:d8:d8:6f:a3 has associated tx_type 2
Dec 26 13:12:05 kernel: CONSOLE: 326075.339 iov:SCB_DEAUTH
Dec 26 13:12:05 kernel: CONSOLE: 326075.340 tx:prep:802.1x
Dec 26 13:12:05 kernel: CONSOLE: 326075.343 tx:prep:802.1x
Dec 26 13:12:05 kernel: CONSOLE: 326075.631 iov:SCB_AUTH
Dec 26 13:12:05 kernel: CONSOLE: 326075.672 wl1: wlc_is_publicaction: rx frame has category 9, pub action field 0; should have cat 4
Dec 26 13:12:05 kernel: CONSOLE: 326075.672 wl1: wlc_recvfilter: bad frame control 0x40d0
Dec 26 13:12:06 kernel: CONSOLE: 326075.692 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 0
Dec 26 13:12:07 kernel: CONSOLE: 326076.539 wl1: 14:f6:d8:d8:6f:a3: addba timed out 0
Dec 26 13:12:07 kernel: CONSOLE: 326076.539 wl1: 14:f6:d8:d8:6f:a3: addba timed out 0
Dec 26 13:12:07 kernel: CONSOLE: 326076.539 wl1: 14:f6:d8:d8:6f:a3: addba timed out 0
Dec 26 13:12:07 kernel: CONSOLE: 326076.540 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x3 tid 6
Dec 26 13:12:07 kernel: CONSOLE: 326077.513 wl1: 14:f6:d8:d8:6f:a3: addba timed out 1
Dec 26 13:12:07 kernel: CONSOLE: 326077.513 wl1: 14:f6:d8:d8:6f:a3: addba timed out 1
Dec 26 13:12:07 kernel: CONSOLE: 326077.514 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x2 tid 5
Dec 26 13:12:08 kernel: CONSOLE: 326077.620 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 1
Dec 26 13:12:08 kernel: CONSOLE: 326078.291 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 3
Dec 26 13:12:08 kernel: CONSOLE: 326078.487 wl1: 14:f6:d8:d8:6f:a3: addba timed out 2
Dec 26 13:12:08 kernel: CONSOLE: 326078.490 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x0 tid 2
Dec 26 13:12:09 kernel: CONSOLE: 326079.272 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 4
Dec 26 13:12:09 kernel: CONSOLE: 326079.406 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 7
I am having some of the issues you are having and have narrowed it down to a PC on my primary router (AX86U) causing my 2nd router setup with a wired backhaul (AIMESH) to disconnect. 2nd router is a ac1900.
 
I am having some of the issues you are having and have narrowed it down to a PC on my primary router (AX86U) causing my 2nd router setup with a wired backhaul (AIMESH) to disconnect. 2nd router is a ac1900.

I have it happen on different computers, wired and wireless, connected to my Asus RT-AX86U. As soon as I have a problem with a web page taking a long time to load, I go into the system log and see a whole bunch of entries just like that one. I don't understand what those logs mean though.
 
I'm still having this happen randomly on all computers. Can anyone tell me what these error messages mean? Or how to fix it?


Jan 8 11:52:15 kernel: CONSOLE: 866020.088 iov:SCB_DEAUTH
Jan 8 11:52:15 kernel: CONSOLE: 866020.088 iov:SCB_DEAUTH
Jan 8 11:52:21 kernel: CONSOLE: 866026.615 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x2 tid 7
Jan 8 11:52:21 kernel: CONSOLE: 866026.670 wl1.0: wlc_send_bar: for 14:f6:d8:d8:6f:a3 seq 0x1 tid 4
Jan 8 11:52:21 kernel: CONSOLE: 866026.712 wl1: r0hole: tx_exp_seq 0x13, seq 0x14
Jan 8 11:52:21 kernel: CONSOLE: 866026.729 wl1: r0hole: tx_exp_seq 0x7e1, seq 0x7e2
Jan 8 11:52:49 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 14:F6:D8:D8:6F:A3, status: 0, reason: Unspecified reason (1)
Jan 8 11:52:49 kernel: CONSOLE: 866054.352 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 19 tid 0
Jan 8 11:52:49 kernel: CONSOLE: 866054.352 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 19 tid 1
Jan 8 11:52:49 kernel: CONSOLE: 866054.352 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 19 tid 2
Jan 8 11:52:49 kernel: CONSOLE: 866054.352 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 19 tid 3
Jan 8 11:52:49 kernel: CONSOLE: 866054.352 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 19 tid 4
Jan 8 11:52:49 kernel: CONSOLE: 866054.352 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 19 tid 5
Jan 8 11:52:49 kernel: CONSOLE: 866054.352 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 19 tid 6
Jan 8 11:52:49 kernel: CONSOLE: 866054.352 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 14:f6:d8:d8:6f:a3 AID 19 tid 7
Jan 8 11:52:49 kernel: CONSOLE: 866054.352 wl1: random key value: 04CEDDD047494F7C079502DFC817D99C2796E14F122807E84C8D19F613762E9F
Jan 8 11:52:49 kernel: CONSOLE: 866054.354 wl1: wlc_txbf_delete_link_serve failed for 14:f6:d8:d8:6f:a3
Jan 8 11:52:49 kernel: CONSOLE: 866054.359 iov:SCB_DEAUTH
Jan 8 11:52:49 kernel: CONSOLE: 866054.359 iov:SCB_DEAUTH
Jan 8 11:53:03 kernel: CONSOLE: 866068.639 wl1: r0hole: tx_exp_seq 0x8e, seq 0x8f
Jan 8 11:53:06 kernel: CONSOLE: 866071.469 wl1: r0hole: tx_exp_seq 0xfcc, seq 0xfcd
 
Can anyone answer? My fiance works from home and it's interfering with her work. Our son is now doing home schooling since Ontario is under lock down, and he can't keep connected either.
 
Can anyone answer? My fiance works from home and it's interfering with her work. Our son is now doing home schooling since Ontario is under lock down, and he can't keep connected either.

Did you reset the firmware before configuring it from scratch?

OE
 
Did you reset the firmware before configuring it from scratch?

OE

Yes. I actually created another post with a different title this morning, but it got deleted.
I've tried all firmwares, Asus's and Merlin, Beta 1-4.
I've changed the cable modem a couple of times. I've tried running the cable modem in bridged mode and non-bridged mode (the modem as the DHCP server, or the router as the DHCP server).
This happens on wired and wireless connections. While the Asus router was the DHCP server, it actually happened at a couple of specific times, as well as randomly. It would do it at around 9am every morning, and about 11:50am every morning. I just switched it back to the modem being the DHCP server, resetting the router back to defaults and starting over a couple of days ago. So far it's not doing it at those specific times, that I know of (it was my fiance and son that were noticing those since she was working, and he was logged in to school, but it also happened on weekends). But it is still happening numerous times a day. I need to know if it is the router, the modem, or the ISP. My fiance's work and our son's school is being affected.
 
Yes. I actually created another post with a different title this morning, but it got deleted.
I've tried all firmwares, Asus's and Merlin, Beta 1-4.
I've changed the cable modem a couple of times. I've tried running the cable modem in bridged mode and non-bridged mode (the modem as the DHCP server, or the router as the DHCP server).
This happens on wired and wireless connections. While the Asus router was the DHCP server, it actually happened at a couple of specific times, as well as randomly. It would do it at around 9am every morning, and about 11:50am every morning. I just switched it back to the modem being the DHCP server, resetting the router back to defaults and starting over a couple of days ago. So far it's not doing it at those specific times, that I know of (it was my fiance and son that were noticing those since she was working, and he was logged in to school, but it also happened on weekends). But it is still happening numerous times a day. I need to know if it is the router, the modem, or the ISP. My fiance's work and our son's school is being affected.

What type of Internet service do you have?

Did you have Internet connection issues before you installed the new AX86U?

Is there a log in the ISP gateway/modem box? Have you asked your ISP tech support to inspect your service from their end for issues?

OE
 
What type of Internet service do you have?

Did you have Internet connection issues before you installed the new AX86U?

Is there a log in the ISP gateway/modem box? Have you asked your ISP tech support to inspect your service from their end for issues?

OE

Roger's Cable modem.
We have had issues on and off for a couple of years. Not as regular as this though. I do not remember if it was regular before or after I got the Asus router because last summer Rogers also implemented a new program that they didn't even inform their employees about called the "Extreme Upload Usage Program". Basically means that if some computer somewhere decides if you are uploading too much, they start throttling you. They would not, and according to them, could not tell me what that threshold was. I asked many, many times, saying if I knew the number, then I could make sure I didn't cross that line. Their response was that it's up to me to do trial and error. If I notice my internet being throttled, stop what I'm doing, wait three days and try again. They also said that it was only suppose to affect our upload speeds, but our whole internet was affected where even Netflix and Youtube would either time out or stream at a very, very low resolution (Youtube going down to 240p). We haven't had that happen as much the past few months, only rarely. But the whole internet disconnecting for a couple of minutes at a time with the errors I posted above.
I'm logged into the modem now and trying to find the system logs. I can't find the logs. I'm on the phone with tier 2 support now, but he doesn't know either. I think I know what you were getting to about that; to check the corresponding times. Not to be an butt, but most times when I call in to tech support, I know way more than they do. I'm a retired IT tech myself, though from a long time ago, and retired because I'm on disability. I have easily forgotten quite a bit, but still know enough to get around, and use Google for most of the rest. I just can't find out what those logs mean.
 
Roger's Cable modem.
We have had issues on and off for a couple of years. Not as regular as this though. I do not remember if it was regular before or after I got the Asus router because last summer Rogers also implemented a new program that they didn't even inform their employees about called the "Extreme Upload Usage Program". Basically means that if some computer somewhere decides if you are uploading too much, they start throttling you. They would not, and according to them, could not tell me what that threshold was. I asked many, many times, saying if I knew the number, then I could make sure I didn't cross that line. Their response was that it's up to me to do trial and error. If I notice my internet being throttled, stop what I'm doing, wait three days and try again. They also said that it was only suppose to affect our upload speeds, but our whole internet was affected where even Netflix and Youtube would either time out or stream at a very, very low resolution (Youtube going down to 240p). We haven't had that happen as much the past few months, only rarely. But the whole internet disconnecting for a couple of minutes at a time with the errors I posted above.
I'm logged into the modem now and trying to find the system logs. I can't find the logs. I'm on the phone with tier 2 support now, but he doesn't know either. I think I know what you were getting to about that; to check the corresponding times. Not to be an butt, but most times when I call in to tech support, I know way more than they do. I'm a retired IT tech myself, though from a long time ago, and retired because I'm on disability. I have easily forgotten quite a bit, but still know enough to get around, and use Google for most of the rest. I just can't find out what those logs mean.

I would work the problem from the ISP connection inward. Convince yourself the ISP provisioned service, cables/connections, and gateway (in bridge mode) are operating well.

Throttling by Rogers might suggest that they have/had capacity/infrastructure issues that they may be/have been working to improve. So, not steady state service that may need some attention. But you'll have to convince yourself it's ok before focusing on your new router.

I prefer using my own cable modem... they have always been trouble free (Motorola, now just Arris SBs).

Sorry, I don't know what the AX86U log entries mean. What concerns me most is "I've been having problems with my Internet for a long time now."

You could also try changing your SSIDs and gradually adding clients to your network to see if one of them is messing with your network.

If you remove your router and only use the ISP gateway, are your clients happy?

OE
 
Last edited:
I would work the problem from the ISP connection inward. Convince yourself the ISP provisioned service, cables/connections, and gateway (in bridge mode) are operating well.

Throttling by Rogers might suggest that they have/had capacity/infrastructure issues that they may be/have been working to improve. So, not steady state service that may need some attention. But you'll have to convince yourself it's ok before focusing on your new router.

I prefer using my own cable modem... they have always been trouble free (Motorola, now just Arris SBs).

Sorry, I don't know what the AX86U log entries mean. What concerns me most is "I've been having problems with my Internet for a long time now."

You could also try changing your SSIDs and gradually adding clients to your network to see if one of them is messing with your network.

If remove your router and only use the ISP gateway, are your clients happy?

OE

We have been having a lot of problems with our Internet for a long time now that they've even proven themselves is directly connected to our account specifically. We had a system engineer come out one day to test the lines because the problem had been going on for so long. The lines test fine, in and out of the house. We took our modem out of the house and connected it to the junction box for the neighbourhood, and it had problems. Changed our modem, connected to our account again, it hand problems. The system engineer hooked up his own work modem, within our home, no problems. In fact, got really fantastic speeds and stability, way above advertised. So, it's not anything to do with the lines, and not anything to do with the modem since we've changed that a number of times. From what I remember, the problems at that time were more random and more speed/stability related, not completely crapping out (though my memory sucks because of personal health issues, and there are numerous issues with Rogers over the years and the whole argument about the "Extreme Upload Usage Program" that they didn't even tell their employees about, and took me 7 weeks to find out about).

While I was on the phone, I did just have the Asus router pop up a bunch of those system logs. My son and fiance said they were still connected, so it wasn't one of them, and I asked the guy from Rogers if he noticed anything with the modem and he said no. So, I am definitely leaning towards it being a problem with the router. When I reset the modem a couple of days ago, switching it back to being the DHCP server, I changed the SSID at the same time. I did a reset on the router and started from scratch, setting it to AP mode. Disconnected clients and adding them one at a time is definitely going to be problematic since these happen rather randomly, and we have a LOT of wireless devices. Only thing that I can think of is anything AC, connect to the Rogers modem for the time being, and only have the handful of AX devices connect to the Asus. Keep in mind, this is also happening with wired devices, too.
 
We have been having a lot of problems with our Internet for a long time now that they've even proven themselves is directly connected to our account specifically. We had a system engineer come out one day to test the lines because the problem had been going on for so long. The lines test fine, in and out of the house. We took our modem out of the house and connected it to the junction box for the neighbourhood, and it had problems. Changed our modem, connected to our account again, it hand problems. The system engineer hooked up his own work modem, within our home, no problems. In fact, got really fantastic speeds and stability, way above advertised. So, it's not anything to do with the lines, and not anything to do with the modem since we've changed that a number of times. From what I remember, the problems at that time were more random and more speed/stability related, not completely crapping out (though my memory sucks because of personal health issues, and there are numerous issues with Rogers over the years and the whole argument about the "Extreme Upload Usage Program" that they didn't even tell their employees about, and took me 7 weeks to find out about).

While I was on the phone, I did just have the Asus router pop up a bunch of those system logs. My son and fiance said they were still connected, so it wasn't one of them, and I asked the guy from Rogers if he noticed anything with the modem and he said no. So, I am definitely leaning towards it being a problem with the router. When I reset the modem a couple of days ago, switching it back to being the DHCP server, I changed the SSID at the same time. I did a reset on the router and started from scratch, setting it to AP mode. Disconnected clients and adding them one at a time is definitely going to be problematic since these happen rather randomly, and we have a LOT of wireless devices. Only thing that I can think of is anything AC, connect to the Rogers modem for the time being, and only have the handful of AX devices connect to the Asus. Keep in mind, this is also happening with wired devices, too.

Remove the new AX86u and only use the ISP gateway. Are the clients happy?

OE
 
I would suggest a full system/network reset to see if you can get a handle on any solution possible here.

The following link is where I would start on all the main/node routers you may be using.

Flash the latest RMerlin 386.1 Beta 4 or later on all supported routers, this firmware is working extremely well, even at the Beta stage.

Fully Reset Router and Network

Then, I would set up the network following the suggested steps below.


After following all the steps above precisely and in order, I would only introduce new features, options, or scripts one by one and fully testing the network (including rebooting it too and testing again) before adding anything else new.
 
^^^ This.

so, update on that, and others.
I started disconnecting devices from the Asus router and connecting them directly to the Rogers modem. Right now there is only my gaming computer (wired), a server in the basement (wired), my Samsung S10+ phone (wireless), and I believe my Logitech Harmony remote using 2.4GHz still connected to to the router. All other WIFI, as well as my NVidia Shield Pro (wired) are connected to the modem itself. Still having problems. It went down a few times yesterday and called in to tech support. The modem shows that it stays connected, and been connected for over 7 days now (since I had it reset to run as the DHCP server, and factory reset my Asus router to rebuild my network, using the Asus as an Access Point at that time). They ordered a service tech to come out yet again (I think that's about 10 in less than a year now). They test the lines, don't find anything wrong, in or out of the home. The modem always stays connected to the Internet, but at times, the whole house loses internet. So, this probably does lead to something at home not playing nice with the rest. But I have a LOT of devices. This will literally take weeks to try using trial and error to figure out what device it is.
Another problem that could help a LOT for that situation is figuring out what these logs mean. I don't know what is going on, what devices may be causing problems (and that's just an assumption now, that some device is crapping out our whole internet), and why it is happening. It's rather annoying that there are all these logs on the Asus router that show a bunch of information, specifically when the internet craps out on us, but no one can understand what the logs mean. Also, for some reason the Rogers modem is not keeping system logs at all.
 
All other WIFI, as well as my NVidia Shield Pro (wired) are connected to the modem itself. Still having problems. It went down a few times yesterday...
What went down? Just the devices connected to the Asus router or also the devices connected directly to the Rogers modem/router?
 
What went down? Just the devices connected to the Asus router or also the devices connected directly to the Rogers modem/router?

All outside connection. All internal is still fine. Drive sharing, streaming from one computer to another, even Windows Remote Access. But all devices in the home lose internet access. And it's not for very long, maybe a minute or two. Most of the time streaming services like SoundCloud don't even pause. Not sure if it's because of it being buffered, or different gateway. But web browsing, online gaming, and my fiance's vpn connection to work go down.
 
Then if it's effecting devices that are connected to the Rogers modem that pretty much eliminates the Asus as the cause of the problem.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top