Gt-ac5300 random red wan.

[Elvis7]

Good day,

I've had my gt-ac5300 since December 2018, I have all the ethernet cables as cat8, and one going to the basement to a gigabyte switch. The cable from the modem Is also cat8.

Occasionally, I'd get a message from my n'est doorbell saying it went offline. I always thought it to be a defective unit or firmware issue, however, I've been at home more often these days and have notice my phone loses wifi connection at the same time, so I've gone to look at the router, and every time all wifi devices get dropped, the wan light is red, then after a minute or so goes back to white.

Tonight the wifi dropped at 23:30 so I saved the router log but cannot see why the disconnect.

Apr 2 23:30:58 rc_service: ntp 1023:notify_rc restart_diskmon
Apr 2 23:30:58 rc_service: waitting "start_firewall" via udhcpc ...
Apr 2 23:30:58 WLCEVENTD: eth8: Assoc 38:8B:59:8E:77:0B
Apr 2 23:30:58 BONDING: not linked
Apr 2 23:30:58 kernel: ubi1: attaching mtd9
Apr 2 23:30:58 kernel: ubi1: scanning is finished
Apr 2 23:30:58 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
Apr 2 23:30:58 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Apr 2 23:30:58 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Apr 2 23:30:58 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Apr 2 23:30:58 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Apr 2 23:30:58 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Apr 2 23:30:58 kernel: ubi1: max/mean erase counter: 23/12, WL threshold: 4096, image sequence number: 180405051
Apr 2 23:30:58 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Apr 2 23:30:58 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1237
Apr 2 23:30:59 WLCEVENTD: eth6: Assoc 00:25:42:72:99:19
Apr 2 23:30:59 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Apr 2 23:30:59 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Apr 2 23:30:59 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Apr 2 23:30:59 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Apr 2 23:30:59 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID ABA6F10C-0F1C-4B89-AD25-4B74DEC12700, small LPT model
Apr 2 23:30:59 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Apr 2 23:30:59 kernel: ubi1: detaching mtd9
Apr 2 23:30:59 kernel: ubi1: mtd9 is detached
Apr 2 23:31:01 kernel: SCSI subsystem initialized

 

[L&LD]

Cat8? Cool.

It looks like something is failing (hardware). What firmware are you running? When was the last time you did a full reset to factory defaults on this router and then configure the router minimally and manually to secure it and connect to your ISP?

 

[Elvis7]

Cat8? Cool.

It looks like something is failing (hardware). What firmware are you running? When was the last time you did a full reset to factory defaults on this router and then configure the router minimally and manually to secure it and connect to your ISP?

Asus firmware 3.0.0.4. 384_45149 (up to date)

Full reset was done at the firmware update. My settings are mostly minimal these days, just enable the ai to sort out traffic, set up password, and rename devices. I'm considering that Mac add allow list but I'm not always home and the wife is tech illiterate so she wouldn't know what to do when people visit.

 

[L&LD]

Asus firmware 3.0.0.4. 384_45149 (up to date)

Full reset was done at the firmware update. My settings are mostly minimal these days, just enable the ai to sort out traffic, set up password, and rename devices. I'm considering that Mac add allow list but I'm not always home and the wife is tech illiterate so she wouldn't know what to do when people visit.

This should still be under warranty with Asus, correct? Open up a support ticket with them. I think you may need a new router.

 

[ColinTaylor]

Tonight the wifi dropped at 23:30 so I saved the router log but cannot see why the disconnect.

Apr 2 23:30:58 rc_service: ntp 1023:notify_rc restart_diskmon
Apr 2 23:30:58 rc_service: waitting "start_firewall" via udhcpc ...

Looks like something happened just before this point. Were there any prior messages?

 

[Elvis7]

The log starts on April 1st, jumps to may 5 then jumps to April 2 at 23:30 hrs. I copied some of the prior code but there's a lot more for may 5. I'm confused as to why.

______________________________________________________
May 5 01:05:09 kernel: Unable to handle kernel NULL pointer dereference at virtual address 000000eepgd = ffffffc000789000[000000ee] *pgd=000000003e806003, *pud=000000003e806003, *pmd=000000003e807003, *pte=0060000081001707Internal error: Oops: 96000007 [#1] PREEMPT SMPModules linked in: tdts_udbfw(O) init_addr( (null) - (null)), core_addr(ffffffbffc159000 - ffffffbffc15e480) tdts_udb(PO) init_addr( (null) - (null)), core_addr(ffffffbffc2c3000 - ffffffbffc2e6538) t
May 5 01:05:09 kernel: ____________________________________________________________________________
May 5 01:05:09 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,202: Could not rdpa_ucast_ipv6_host_address_table_find^[[0m
May 5 01:05:10 kernel: Bonding Port enabled mask 0x000c
May 5 01:05:10 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1 --> 5 ] [ 2, 3, 7 --> 8 ]
May 5 01:05:10 nat: apply redirect rules
May 5 01:05:13 dnsmasq[842]: warning: no upstream servers configured
May 5 01:05:13 GT-AC5300: start https:8443
May 5 01:05:13 GT-AC5300: start httpd:80
May 5 01:05:13 httpd: Generating SSL certificate...
May 5 01:05:13 httpds: Generating SSL certificate...
May 5 01:05:13 avahi-daemon[869]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 5 01:05:13 NAT Tunnel: AAE Service is stopped
May 5 01:05:13 disk monitor: be idle
May 5 01:05:13 AAE: AAE Service is started
May 5 01:05:13 hour monitor: daemon is starting
May 5 01:05:13 jffs2: valid logs(1)
May 5 01:05:13 miniupnpd[916]: version 1.9 started
May 5 01:05:13 ERP: The model isn't under EU SKU!
May 5 01:05:13 miniupnpd[916]: HTTP listening on port 33861
May 5 01:05:13 miniupnpd[916]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 01:05:14 lldpd[925]: cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted
May 5 01:05:14 avahi-daemon[869]: Alias name "GT-AC5300" successfully established.
May 5 01:05:15 WAN Connection: ISP's DHCP did not function properly.
May 5 01:05:16 rc_service: udhcpc 1004:notify_rc start_firewall
May 5 01:05:17 wan: finish adding multi routes
May 5 01:05:17 rc_service: udhcpc 1004:notify_rc stop_upnp
May 5 01:05:17 rc_service: waitting "start_firewall" via udhcpc ...
May 5 01:05:17 Mastiff: init
May 5 01:05:17 WLCEVENTD: eth6: Assoc 18:B4:30:E6:64:57
May 5 01:05:18 kernel: ubi1: attaching mtd9
May 5 01:05:18 kernel: ubi1: scanning is finished
May 5 01:05:18 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
May 5 01:05:18 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 5 01:05:18 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 5 01:05:18 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 5 01:05:18 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 5 01:05:18 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 5 01:05:18 kernel: ubi1: max/mean erase counter: 23/12, WL threshold: 4096, image sequence number: 180405051
May 5 01:05:18 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 5 01:05:18 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1092
May 5 01:05:18 WLCEVENTD: eth6: Assoc 68:C6:3A:BB:0B:29
May 5 01:05:20 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
May 5 01:05:20 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 5 01:05:20 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
May 5 01:05:20 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
May 5 01:05:20 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID ABA6F10C-0F1C-4B89-AD25-4B74DEC12700, small LPT model
May 5 01:05:20 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 5 01:05:20 kernel: ubi1: detaching mtd9
May 5 01:05:20 kernel: ubi1: mtd9 is detached
May 5 01:05:20 WAN Connection: WAN was restored.
May 5 01:05:21 kernel: ubi1: attaching mtd9
May 5 01:05:21 kernel: ubi1: scanning is finished
May 5 01:05:21 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
May 5 01:05:21 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 5 01:05:21 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 5 01:05:21 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 5 01:05:21 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 5 01:05:21 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 5 01:05:21 kernel: ubi1: max/mean erase counter: 23/12, WL threshold: 4096, image sequence number: 180405051
May 5 01:05:21 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 5 01:05:21 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1150
May 5 01:05:22 WLCEVENTD: eth7: Assoc 18:B4:30:CE:77:71
May 5 01:05:22 WLCEVENTD: eth8: Disassoc 18:B4:30:CE:77:71
May 5 01:05:22 WLCEVENTD: eth8: Assoc CC:6E:A4:E7:80:3C
May 5 01:05:22 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
May 5 01:05:22 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 5 01:05:22 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
May 5 01:05:22 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
May 5 01:05:22 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID ABA6F10C-0F1C-4B89-AD25-4B74DEC12700, small LPT model
May 5 01:05:22 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 5 01:05:22 kernel: ubi1: detaching mtd9
May 5 01:05:22 kernel: ubi1: mtd9 is detached
May 5 01:05:22 WLCEVENTD: eth8: Assoc 20F:B9:B9:A1:1A
May 5 01:05:23 WLCEVENTD: eth8: Assoc E4:F0:42:5F:98:7F
May 5 01:05:23 ntp: start NTP update
May 5 01:05:23 WLCEVENTD: eth6: Assoc 64:52:99:75:67:F0
Apr 2 23:30:58 rc_service: ntp 1023:notify_rc restart_diskmon

 

[ColinTaylor]

The log starts on April 1st, jumps to may 5 then jumps to April 2 at 23:30 hrs. I copied some of the prior code but there's a lot more for may 5. I'm confused as to why.

The May 5 date and time are the default values of the clock when the router boots up, before it's able to contact an NTP server. This indicates that your router has rebooted. From the first messages it looks like the router's kernel crashed, possibly because of a problem with the packet runner and/or IPv6. Try disabling IPv6.

 

[Elvis7]

Ipv6 is already disabled. Here is some code log prior to the one posted .


May 5 01:05:09 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
May 5 01:05:09 kernel: Creating CPU ring for queue number 2 with 128 packets descriptor=0xffffffbffc27cec8
May 5 01:05:09 kernel: Done initializing Ring 2 Base=0xffffff8000260000 End=0xffffff8000260800 calculated entries= 128 RDD Base=0x3ea0f000K descriptor=0xffffffbffc27cec8
May 5 01:05:09 kernel: RDPA returned tx wakeup reg = <0x82299004>, val = <0x12000000>^M
May 5 01:05:09 kernel: RDPA returned rx wakeup reg = <0x8229a004>, val = <0x2a000000>^M
May 5 01:05:09 kernel: Scratch pad is not initialized.
May 5 01:05:09 kernel: dhd_runner_attach: Rx Offload - Enabled, Ring Size = 1024
May 5 01:05:09 kernel: dhd_attach(): thread:dhd_watchdog_thread:268 started
May 5 01:05:09 kernel: Creating CPU ring for queue number 4 with 1024 packets descriptor=0xffffffbffc54bd80
May 5 01:05:09 kernel: Creating CPU ring for queue number 5 with 1024 packets descriptor=0xffffffbffc54bdb0
May 5 01:05:09 kernel: ^[[1m^[[34m wfd_bind: Dev eth%d wfd_idx 2 wl_radio_idx 2 Type fkb configured WFD thread wfd2-thrd minQId/maxQId (12/13), status (0) qmask 0x30^[[0m
May 5 01:05:09 kernel: Instantiating WFD 2 thread
May 5 01:05:09 kernel: Scratch pad is not initialized.
May 5 01:05:09 kernel: dhd_runner_profile_init: N+M profile = 3 01:1024 -1:2048 -1:1024 -1:0512 00:0512^M
May 5 01:05:09 kernel: Scratch pad is not initialized.
May 5 01:05:09 kernel: dhd_runner_policy_init: N+M Policy = 0 1 (HW)
May 5 01:05:09 kernel: ^[[0;33;40mRunner DHD PCIE: vendor<0x14e4> device<0x4365> bus<1> slot<0>^[[0m
May 5 01:05:09 kernel: Initial configuration
May 5 01:05:09 kernel: =================================
May 5 01:05:09 kernel: rx_post_flow_ring_base_addr : ffffffc02ef40000
May 5 01:05:09 kernel: tx_post_flow_ring_base_addr : ffffffc00c3c4000
May 5 01:05:09 kernel: rx_complete_flow_ring_base_addr : ffffffc02ef48000
May 5 01:05:09 kernel: tx_complete_flow_ring_base_addr : ffffffc02ef2c000
May 5 01:05:09 kernel: r2d_wr_arr_base_addr : ffffff8001359000
May 5 01:05:09 kernel: d2r_rd_arr_base_addr : ffffff8001359402
May 5 01:05:09 kernel: r2d_rd_arr_base_addr : ffffff8001359c00
May 5 01:05:09 kernel: d2r_wr_arr_base_addr : ffffff8001359802
May 5 01:05:09 kernel: tx_post_mgmt_arr_base_addr : ffffff800135a000
May 5 01:05:09 kernel: tx_post_mgmt_arr_base_phys_addr : 0x2ef29000
May 5 01:05:09 kernel: r2d_wr_arr_base_phys_addr : 0x2ef28000
May 5 01:05:09 kernel: d2r_rd_arr_base_phys_addr : 0x2ef28402
May 5 01:05:09 kernel: r2d_rd_arr_base_phys_addr : 0x2ef28c00
May 5 01:05:09 kernel: d2r_wr_arr_base_phys_addr : 0x2ef28802
May 5 01:05:09 kernel: Doorbell ISR : ffffffbffc647278
May 5 01:05:09 kernel: Doorbell CTX : ffffffc032357400
May 5 01:05:09 kernel: ^[[0;33;40mRunner DHD Offload initialization complete^[[0m
May 5 01:05:09 kernel: Dongle Host Driver, version 1.363.45.84015 (r676423)
May 5 01:05:09 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 23 2018 at 17:54:52
May 5 01:05:09 kernel: wfd_registerdevice Successfully registered dev eth8 ifidx 0 wfd_idx 2
May 5 01:05:09 kernel: Register interface [eth8] MAC: 40:b0:76:12:79:08
May 5 01:05:09 kernel: ++++ Powering up USB blocks
May 5 01:05:09 kernel: usb3 reseting..........
May 5 01:05:09 kernel: release usb3 reseting..........
May 5 01:05:09 kernel: jffs2: notice: (635) check_node_data: wrong data CRC in data node at 0x02c81768: read 0xbed1e795, calculated 0xfb1d263d.
May 5 01:05:09 kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
May 5 01:05:09 kernel: usb3 reseting..........
May 5 01:05:09 kernel: _ Reboot message ... _______________________________________________________

 

[ColinTaylor]

I think those are the normal startup messages that you always get. If you go back further you should see a message similar to "kernel: klogd started: BusyBox v1.24.1......". There might be some clues just before this message to indicate why it rebooted, but usually not .

TBH these random reboots seem to have plagued this model and the RT-AC86U. And as far as I know nobody has gotten to the bottom of it. The best I can suggest is that you progressively disable features (like AiProtection, QOS, etc.) and see if you can isolate the source.

It might be worth installing Merlin's firmware instead of Asus' (assuming you don't use AiMesh) and see if that's any better.

https://rog.asus.com/forum/showthread.php?105552-GT-AC5300-random-reboots/page2#post744356

 

[Elvis7]

I have a 4 year warranty on this guy from best buy. So I may just opt in to get it replaced. no issue for 3 days, then today the wifi completely went down, would pop up and disappear not allowing anything to connect to it, even though all the led's were white, so I dont know anymore.



Apr 8 22:58:11 rc_service: ntp 1034:notify_rc restart_diskmon
Apr 8 22:58:11 rc_service: waitting "start_firewall" via udhcpc ...
Apr 8 22:58:12 kernel: ubi1: attaching mtd9
Apr 8 22:58:12 kernel: ubi1: scanning is finished
Apr 8 22:58:12 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
Apr 8 22:58:12 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Apr 8 22:58:12 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Apr 8 22:58:12 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Apr 8 22:58:12 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Apr 8 22:58:12 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Apr 8 22:58:12 kernel: ubi1: max/mean erase counter: 23/12, WL threshold: 4096, image sequence number: 180405051
Apr 8 22:58:12 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Apr 8 22:58:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1236
Apr 8 22:58:13 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Apr 8 22:58:13 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Apr 8 22:58:13 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Apr 8 22:58:13 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Apr 8 22:58:13 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID ABA6F10C-0F1C-4B89-AD25-4B74DEC12700, small LPT model
Apr 8 22:58:13 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Apr 8 22:58:13 kernel: ubi1: detaching mtd9
Apr 8 22:58:13 kernel: ubi1: mtd9 is detached
Apr 8 22:58:14 WLCEVENTD: eth7: Assoc 00:09:B0:BC:37F
Apr 8 22:58:14 WLCEVENTD: eth8: Disassoc 00:09:B0:BC:37F
Apr 8 22:58:14 modprobe: module scsi_wait_scan not found in modules.dep
Apr 8 22:58:14 kernel: SCSI subsystem initialized
Apr 8 22:58:14 WLCEVENTD: eth6: Assoc 18:B4:30:AE:7E8
Apr 8 22:58:14 modprobe: module mbcache not found in modules.dep
Apr 8 22:58:14 modprobe: module jbd not found in modules.dep
Apr 8 22:58:14 modprobe: module ext3 not found in modules.dep
Apr 8 22:58:14 modprobe: module ext4 not found in modules.dep
Apr 8 22:58:14 modprobe: module ext2 not found in modules.dep
Apr 8 22:58:15 modprobe: module btusbdrv not found in modules.dep
Apr 8 22:58:15 miniupnpd[921]: shutting down MiniUPnPd
Apr 8 22:58:15 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Apr 8 22:58:15 miniupnpd[1347]: version 1.9 started
Apr 8 22:58:15 miniupnpd[1347]: HTTP listening on port 46804
Apr 8 22:58:15 miniupnpd[1347]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 8 22:58:15 disk_monitor: Finish
Apr 8 22:58:15 disk monitor: be idle
Apr 8 22:58:15 rc_service: udhcpc 1015:notify_rc start_upnp
Apr 8 22:58:15 rc_service: waitting "stop_upnp" via udhcpc ...
Apr 8 22:58:15 miniupnpd[1347]: shutting down MiniUPnPd
Apr 8 22:58:16 WLCEVENTD: eth6: Assoc 64:1C:AE:72:15:19
Apr 8 22:58:16 miniupnpd[1352]: version 1.9 started
Apr 8 22:58:16 miniupnpd[1352]: HTTP listening on port 55359
Apr 8 22:58:16 miniupnpd[1352]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 8 22:58:16 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Apr 8 22:58:16 ddns update: ez-ipupdate: starting...
Apr 8 22:58:16 ddns update: asus_private() interface =eth0
Apr 8 22:58:16 ddns update: g_asus_ddns_mode == 2
Apr 8 22:58:17 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Apr 8 22:58:18 WLCEVENTD: eth6: Assoc 64:52:99:75:67:F0
Apr 8 22:58:19 WLCEVENTD: eth6: Assoc 18:B4:30:E6:64:57
Apr 8 22:58:19 WLCEVENTD: eth6: Disassoc 68:C6:3A:BB:0B:29
Apr 8 22:58:19 kernel: SHN Release Version: 2.0.1 890c91d
Apr 8 22:58:19 kernel: UDB Core Version: 0.2.18
Apr 8 22:58:19 kernel: sizeof forward pkt param = 280
Apr 8 22:58:19 BWDPI: fun bitmap = 17f
Apr 8 22:58:20 ddns update: Asus update entry:: return: HTTP/1.1 299 |Invalid IP format| 192.168.0.11^M Date: Tue, 09 Apr 2019 02:58:17 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Content-Type: text/html; charset=UTF-8^M ^M
Apr 8 22:58:20 ddns update: retval= 1, ddns_return_code (,299)
Apr 8 22:58:20 ddns update: asusddns_update: 1
Apr 8 22:58:20 ddns update: exit_main
Apr 8 22:58:20 WLCEVENTD: eth8: Assoc E4:F0:42:5F:98:7F
Apr 8 22:58:21 WLCEVENTD: eth6: Assoc 18:B4:30:B0D:31
Apr 8 22:58:21 rc_service: udhcpc 1015:notify_rc start_firewall
Apr 8 22:58:21 dhcp client: bound 192.168.0.11 via 192.168.0.1 during 604800 seconds.
Apr 8 22:58:22 miniupnpd[1352]: shutting down MiniUPnPd
Apr 8 22:58:22 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Apr 8 22:58:22 miniupnpd[1575]: version 1.9 started
Apr 8 22:58:22 miniupnpd[1575]: HTTP listening on port 33065
Apr 8 22:58:22 miniupnpd[1575]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 8 22:58:22 WLCEVENTD: eth6: Assoc 68:C6:3A:BB:0B:29
Apr 8 22:58:23 WLCEVENTD: eth6: Assoc 18:B4:30:AB:8C:A1
Apr 8 22:58:23 WLCEVENTD: eth6: Assoc 00:04:20:FC:6B:AC
Apr 8 22:58:30 WLCEVENTD: eth8: Assoc 0C:8B:FD:39:7E:0C
Apr 8 22:58:31 kernel: ubi1: attaching mtd9
Apr 8 22:58:31 kernel: ubi1: scanning is finished
Apr 8 22:58:31 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
Apr 8 22:58:31 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Apr 8 22:58:31 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Apr 8 22:58:31 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Apr 8 22:58:31 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Apr 8 22:58:31 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Apr 8 22:58:31 kernel: ubi1: max/mean erase counter: 23/12, WL threshold: 4096, image sequence number: 180405051
Apr 8 22:58:31 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Apr 8 22:58:31 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1653
Apr 8 22:58:32 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Apr 8 22:58:32 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Apr 8 22:58:32 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Apr 8 22:58:32 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Apr 8 22:58:32 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID ABA6F10C-0F1C-4B89-AD25-4B74DEC12700, small LPT model
Apr 8 22:58:32 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Apr 8 22:58:32 kernel: ubi1: detaching mtd9
Apr 8 22:58:32 kernel: ubi1: mtd9 is detached
Apr 8 22:58:32 watchdog: start ddns.
Apr 8 22:58:32 rc_service: watchdog 868:notify_rc restart_ddns
Apr 8 22:58:32 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Apr 8 22:58:32 ddns update: ez-ipupdate: starting...
Apr 8 22:58:32 ddns update: asus_private() interface =eth0
Apr 8 22:58:32 ddns update: g_asus_ddns_mode == 2
Apr 8 22:58:33 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Apr 8 22:58:36 ddns update: Asus update entry:: return: HTTP/1.1 299 |Invalid IP format| 192.168.0.11^M Date: Tue, 09 Apr 2019 02:58:33 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Content-Type: text/html; charset=UTF-8^M ^M
Apr 8 22:58:36 ddns update: retval= 1, ddns_return_code (,299)
Apr 8 22:58:36 ddns update: asusddns_update: 1
Apr 8 22:58:36 ddns update: exit_main
Apr 8 22:58:48 crond[855]: time disparity of 488033 minutes detected
Apr 8 23:00:01 hour monitor: ntp sync fail, will retry after 120 sec
Apr 8 23:00:04 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
Apr 8 23:00:05 lldpd[930]: cannot get ethtool link information with GSET (requires 2.6.19+): Operation not permitted
Apr 8 23:00:07 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link UP 1000 mbps full duplex
Apr 8 23:00:14 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.

 

[Elvis7]

Okay, so I've gone ahead and exchanged the router. I updated it and reset it. Was working fine for a few days but today at 1046 (prior) the wifi shut down again and rebooted. I've saved the system log.

Could this just be a firmware issue?

 

[OzarkEdge]

Okay, so I've gone ahead and exchanged the router. I updated it and reset it. Was working fine for a few days but today at 1046 (prior) the wifi shut down again and rebooted. I've saved the system log.

Could this just be a firmware issue?

Did you restore previous settings from file or configure from scratch?

OE

 

[Elvis7]

Did you restore previous settings from file or configure from scratch?

OE

Yes but I've left it at basic settings,

I've only changed the lan ip, put the wifi name to what it was before so my device have seamless reconnect, and enabled aimesh. This time around I've enabled ipv6 on the router to see if it fixed the issue but I guess not.

 

[OzarkEdge]

Okay, so I've gone ahead and exchanged the router. I updated it and reset it. Was working fine for a few days but today at 1046 (prior) the wifi shut down again and rebooted. I've saved the system log.

Could this just be a firmware issue?

Are all of those Cat8 cables new? I wonder if it would make sense to disconnect most everything from the router and see how it behaves bare bones Maybe even swap out the WAN Cat8 for an older cable you trust. Just an idea.

OE

 

[Elvis7]

Are all of those Cat8 cables new? I wonder if it would make sense to disconnect most everything from the router and see how it behaves bare bones Maybe even swap out the WAN Cat8 for an older cable you trust. Just an idea.

OE

Yes they are all new, I've already passed them through the walls and to the basement rooms (cctv pc) (xbox one) (4 port switch)

But I can probably connect them all to the modem and leave the router unplugged from ethernet cables, and use a cat 6a from modem to router?

Also, I forgot to add that this issue was going on before ever having cat8 cables installed. My nest door cam would notify be of it going offline since week one? Could it be causing the Asus routers to fail?

 

[OzarkEdge]

Also, I forgot to add that this issue was going on before ever having cat8 cables installed. My nest door cam would notify be of it going offline since week one? Could it be causing the Asus routers to fail?

My thought was that it is odd that two routers fail, so was looking for some external trouble, such as connected equipment... cabling, switches, etc.

An IoT device/cam going offline is not the most certain diagnostic since those 'things' are troublesome on their own. Better to look for confirming evidence, cause, affect.

OE