- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello. I just recently upgraded from my old 50 mpbs FIOS to 200 mbps. The tech told me that now that connection was done through ethernet and not coax to router, I could use 3rd party and better routers. So i read the good reviews on ASUS RT-AX3000 router, and bought that.
I replaced my Verizon G1100 router with the new ASUS. Speeds and coverage seemed fantastic with new ASUS. But i started to get dropped connection to internet over and over. Would usually drop and then connect back a minute later. But happens a LOT. Like 10 times overnight. No discernable pattern. Sometimes 50 mins apart...sometimes 10 mins apart. (I know this is happening, because my alarm system through WIFI lets me know when it loses and gains connections. So i get tons of notifications with timestamps). When i see it happen real-time, i lose the connection (even wired ethernet connection to my computer...so i know its not a wireless issue. Its the router itself that loses connection to internet). I see the red LED symbol for internet on router that lets me know internet went dead. A minute later its white again, and our devices reconnect again. This is causing havoc with streaming, online gaming, video conferences for work, etc.
I'm curious if anyone here has had problems with their ASUS routers on FIOS. If so, any settings on the router I should be changing? anything to note as possible problem area? If you are using FIOS with no problem on your ASUS router, please let me know the model.
Yes, it was new in box, not refurb router. Yes, firmware is up to date. I feel like its an issue with our FIOS connection and not the router. Somehow FIOS is not playing well with router? But how can one confirm whether its the router or FIOS that is misbehaving? Something you can verify in the logs?
Any help, or confirmation of people successfully using newish ASUS routers is greatly appreciated. Thanks.
Solved! Go to Correct Answer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see your WAN link goes up and down. Do you have a cabling issue? Could you swap out your Ethernet cable to see? Also, is ONT's power stable? Is ONT rebooting itself from time to time?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you check the internal clock on your router? Verizon layer 3 now does DHCP renewal every hour, instead of 2 hours in the past. If your router's clock is off by seconds or so, the DHCP lease could be expired before the router requests to renew.
Do you have logging enabled on your router? Those logs are especially handy in diagnosing the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, i have looked at logs, but cannot decipher what is happening. Look at an example below. Look at Jun 3 21:58....you can see what happens apparently after the connection comes back on. The mystery is why does the log RIGHT BEFORE IT SHOW MAY 5! I didnt even have the router then. Bought it a week ago. How can log go from May 5, to June 3? When i scroll up past what i posted here ( too many lines to post, ther are a ton of "crashlog" lines in the May 5 area of log, which dont sound good. I'm assuming this May 5 date is a glitch, and these items are what happens right before it loses the internet connection? You can see in bold text where the router log starts after a drop in internet connection. (Note, i removed actual numbers and replaced with XXX in certain areas, just to protect myself. Not sure if they are mac addresses or what, but i figure they are irrelevant to this log).
May 5 01:05:15 WAN Connection: WAN was restored.
May 5 01:05:16 wlceventd: wlceventd_proc_event(527): wl0.1: Auth XX:XX:XX:XX:XX 1, status: Successful (0), rssi:0
May 5 01:05:16 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc XX:XX:XX:XX:XX , status: Successful (0), rssi:0
May 5 01:05:17 roamast: ROAMING Start...
May 5 01:05:18 ntp: start NTP update
May 5 01:05:18 wlceventd: wlceventd_proc_event(527): wl0.1: Auth XX:XX:XX:XX:XX , status: Successful (0), rssi:0
May 5 01:05:18 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc XX:XX:XX:XX:XX , status: Successful (0), rssi:0
Jun 3 21:58:48 rc_service: ntp 1934:notify_rc restart_diskmon
Jun 3 21:58:48 disk_monitor: Finish
Jun 3 21:58:48 disk monitor: be idle
Jun 3 21:58:48 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Jun 3 21:58:48 ddns update: ez-ipupdate: starting...
Jun 3 21:58:49 wlceventd: wlceventd_proc_event(527): eth5: Auth XX:XX:XX:XX:XX status: Successful (0), rssi:0
Jun 3 21:58:49 wlceventd: wlceventd_proc_event(556): eth5: Assoc XX:XX:XX:XX:XX , status: Successful (0), rssi:0
Jun 3 21:58:49 wlceventd: wlceventd_proc_event(527): wl0.1: Auth XX:XX:XX:XX:XX , status: Successful (0), rssi:0
Jun 3 21:58:50 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc XX:XX:XX:XX:XX , status: Successful (0), rssi:0
Jun 3 21:58:50 wlceventd: wlceventd_proc_event(527): wl0.1: Auth XX:XX:XX:XX:XX , status: Successful (0), rssi:0
Jun 3 21:58:50 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc XX:XX:XX:XX:XX ,status: Successful (0), rssi:0
Jun 3 21:58:52 ddns update: asus_private() interface =eth4
Jun 3 21:58:52 ddns update: g_asus_ddns_mode == 2
Jun 3 21:58:52 httpd: Succeed to init SSL certificate...80
Jun 3 21:58:52 httpd: Succeed to init SSL certificate...8443
Jun 3 21:58:52 ddns update: connected to nwsrv-ns1.asus.com (XX:XX:XX:XX:XX ) on port 443.
Jun 3 21:58:52 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Fri, 04 Jun 2021 01:58:52 GMT^M Server: Apache^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Jun 3 21:58:52 ddns update: retval= 0, ddns_return_code (,200)
Jun 3 21:58:52 ddns update: asusddns_update: 0
Jun 3 21:58:52 ddns: ddns update ok
Jun 3 21:58:52 ddns update: exit_main
Jun 3 21:58:54 cfg_server: event: wl_chanspec_changed_action
Jun 3 21:58:54 cfg_server: skip event due no re
Jun 3 21:58:54 wlceventd: wlceventd_proc_event(491): wl0.1: Deauth_ind XX:XX:XX:XX:XX , status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jun 3 21:58:56 kernel: SHN Release Version: 2.0.1 c03f6c5
Jun 3 21:58:56 kernel: UDB Core Version: 0.2.20
Jun 3 21:58:56 kernel: sizeof forward pkt param = 192
Jun 3 21:58:56 BWDPI: fun bitmap = 47f
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
These logs seem OK. I am wondering do you have logs right before and after a disconnection?
I do see some NTP notices there, but they should not be a concern. NTP is Network Time Protocol for computers to synchronize with atomic clocks around the globe. The weird date change you observed should be a result of NTP time synchronization.
Do you specifically have WAN DHCP logs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm having the same issue with the same router, but I'm on gigabit. Seems to happen very intermittently, sometimes a couple times in a day but then could be fine for a week or two. Decided to check out the logs today (May 18, 14:49) right after the router finished rebooting.
May 5 01:05:17 WAN Connection: WAN was restored.
May 5 01:05:17 wlceventd: wlceventd_proc_event(527): eth5: Auth [REDACTED], status: Successful (0), rssi:0
May 5 01:05:17 wlceventd: wlceventd_proc_event(556): eth5: Assoc [REDACTED], status: Successful (0), rssi:-68
May 5 01:05:17 wlceventd: wlceventd_proc_event(527): eth5: Auth [REDACTED], status: Successful (0), rssi:0
May 5 01:05:17 wlceventd: wlceventd_proc_event(556): eth5: Assoc [REDACTED], status: Successful (0), rssi:-67
May 5 01:05:18 roamast: ROAMING Start...
May 5 01:05:18 ntp: start NTP update
May 18 14:49:31 rc_service: ntp 2500:notify_rc restart_diskmon
May 18 14:49:31 disk_monitor: Finish
May 18 14:49:31 disk monitor: be idle
May 18 14:49:31 wlceventd: wlceventd_proc_event(527): eth5: Auth [REDACTED], status: Successful (0), rssi:0
May 18 14:49:31 wlceventd: wlceventd_proc_event(556): eth5: Assoc [REDACTED], status: Successful (0), rssi:-33
May 18 14:49:32 wlceventd: wlceventd_proc_event(527): eth5: Auth [REDACTED], status: Successful (0), rssi:0
May 18 14:49:32 wlceventd: wlceventd_proc_event(556): eth5: Assoc [REDACTED], status: Successful (0), rssi:-62
May 18 14:49:33 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 😎 Link DOWN.
May 18 14:49:33 cfg_server: event: wl_chanspec_changed_action
May 18 14:49:33 cfg_server: current chansp(unit0) is 100a
May 18 14:49:33 cfg_server: current chansp(unit1) is e02a
May 18 14:49:34 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind [REDACTED], status: 0, reason: Unspecified reason (1), rssi:0
May 18 14:49:34 wlceventd: wlceventd_proc_event(527): eth6: Auth [REDACTED], status: Successful (0), rssi:0
May 18 14:49:36 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 😎 Link Up at 1000 mbps full duplex
May 18 14:49:36 kernel: SHN Release Version: 2.0.2 d2ff630
May 18 14:49:36 kernel: UDB Core Version: 0.2.20
May 18 14:49:36 kernel: sizeof forward pkt param = 192
May 18 14:49:36 BWDPI: fun bitmap = 57f
May 18 14:49:36 wlceventd: wlceventd_proc_event(527): eth5: Auth [REDACTED], status: Successful (0), rssi:0
May 18 14:49:36 wlceventd: wlceventd_proc_event(556): eth5: Assoc [REDACTED], status: Successful (0), rssi:-69
May 18 14:49:38 wlceventd: wlceventd_proc_event(527): eth6: Auth [REDACTED], status: Successful (0), rssi:-37
May 18 14:49:38 wlceventd: wlceventd_proc_event(556): eth6: Assoc [REDACTED], status: Successful (0), rssi:-37
May 18 14:49:40 kernel: Archer TCP Pure ACK Enabled
May 18 14:49:40 dhcp client: bound [REDACTED]/[REDACTED] via [REDACTED] for 7200 seconds.
May 18 14:49:40 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 😎 Link DOWN.
May 18 14:49:42 wlceventd: wlceventd_proc_event(508): eth6: Disassoc [REDACTED], status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 18 14:49:42 wlceventd: wlceventd_proc_event(508): eth6: Disassoc [REDACTED], status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 18 14:49:43 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 😎 Link Up at 1000 mbps full duplex
....
May 18 14:51:20 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7565)]periodic_check AM 5:55
May 18 14:51:20 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7604)]do webs_update
May 18 14:51:27 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7622)]retrieve firmware information
May 18 14:51:27 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7637)]fimrware update check first time
May 18 14:51:27 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7670)]no need to upgrade firmware
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see your WAN link goes up and down. Do you have a cabling issue? Could you swap out your Ethernet cable to see? Also, is ONT's power stable? Is ONT rebooting itself from time to time?