RT-AC3100 - Intermittently can't ping devices on the Network

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

stephenspann27

New Around Here
I have a RT-AC3100. It's a replacement system that Asus sent me after my 2900 failed while under warranty. I'm running 3.0.0.4.386_43129 code. I've been using the router about 4 weeks. The issue I'm having is, I intermittently cannot ping between certain devices on the network. No device ever looses connectivity to the router or the WAN, but devices do loose the ability to talk to one another. I've spent a lot of time trying to find something common about the issue,
is it wired to wireless pinging or wireless to wired?
is it devices with ip reservations?
is it devices with poor signal strength?
is it related to IP lease time?

I've never been able to find a common theme. When I'm experiencing the problem, if I reboot the router, the issue will go away for a time. The main way I'm noticing the symptom is from my blue iris server, which is a laptop, connected to 6 cameras. Yesterday, only 5 out of 6 cameras were communicating with the blue iris laptop. I could not ping the "missing" camera from the laptop. I could ping that camera though, from the router, and my cell phone could connect directly to the camera over wifi. I rebooted the blue iris (windows) laptop, and after it came up, the laptop couldn't talk to any of the 6 cameras. I rebooted the router next, and after the router came up, 1 of the 6 cameras connected, then a second camera. It was sitting at 2 out of 6 cameras working, about 10 mins after the router reboot. I was trying to ping the cameras from other computer on the network, doing troubleshooting, then suddenly, the rest of the cameras came online.
I know this is a long post, but I'm trying to give as much info as possible. I was running QOS, with a streaming profile, but it was causing terrible performance from my iphone, I've disabled QOS and that issue is resolved.

I couple more bullet points:
I can ALWAYS ping all devices from the router.
Device A may not be able to ping Device B, but I can go to Device C and ping Device B. There is though, no pattern that I can spot. I've gone through the logs and can't find anything meaningful.

00:22:53 syslog: wlceventd_proc_event(556): eth1: Assoc D8:28:C9:5F:76:44, status: Successful (0), rssi:0
Aug 3 00:22:54 kernel: D8:28:C9:5F:76:44 not mesh client, can't update it's ip
Aug 3 00:55:45 syslog: wlceventd_proc_event(491): eth1: Deauth_ind 22:9A:28:61:54:14, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-70
Aug 3 01:12:28 syslog: wlceventd_proc_event(527): eth1: Auth 22:9A:28:61:54:14, status: Successful (0), rssi:0
Aug 3 01:12:28 syslog: wlceventd_proc_event(537): eth1: ReAssoc 22:9A:28:61:54:14, status: Successful (0), rssi:0
Aug 3 01:31:53 kernel: E8:AB:FA:6E:4D:C9 not mesh client, can't update it's ip
Aug 3 01:35:15 miniupnpd[1353]: upnp_event_process_notify: connect(192.168.1.99:2869): Connection timed out
Aug 3 01:35:20 miniupnpd[1353]: upnp_event_process_notify: connect(192.168.1.99:2869): Connection timed out
Aug 3 01:35:20 miniupnpd[1353]: upnpevents_processfds: 0x2d998, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-d45d644286a7 after an ERROR cb: http://192.168.1.99:2869/upnp/eventing/oswypydppq
Aug 3 01:55:20 syslog: wlceventd_proc_event(491): eth1: Deauth_ind 7C:A7:B0:CF:02:82, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-61
Aug 3 01:55:20 syslog: wlceventd_proc_event(491): eth1: Deauth_ind 9C:7B:EF:FB:D4:0B, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-55
Aug 3 01:55:22 miniupnpd[1353]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Aug 3 01:55:23 syslog: wlceventd_proc_event(527): eth1: Auth 7C:A7:B0:CF:02:82, status: Successful (0), rssi:0
Aug 3 01:55:24 syslog: wlceventd_proc_event(556): eth1: Assoc 7C:A7:B0:CF:02:82, status: Successful (0), rssi:0
Aug 3 01:55:27 miniupnpd[1353]: upnp_event_process_notify: connect(192.168.1.12:2869): Connection timed out
Aug 3 01:55:27 miniupnpd[1353]: upnpevents_processfds: 0x2d998, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-d45d6442c68e after an ERROR cb: http://192.168.1.12:2869/upnp/eventing/fothlsszup
Aug 3 01:55:28 syslog: wlceventd_proc_event(527): eth1: Auth 9C:7B:EF:FB:D4:0B, status: Successful (0), rssi:0
Aug 3 01:55:28 syslog: wlceventd_proc_event(556): eth1: Assoc 9C:7B:EF:FB:D4:0B, status: Successful (0), rssi:0
Aug 3 01:55:29 kernel: 9C:7B:EF:FB:D4:0B not mesh client, can't update it's ip
Aug 3 01:55:42 syslog: wlceventd_proc_event(491): eth1: Deauth_ind 22:9A:28:61:54:14, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-69
Aug 3 02:06:36 syslog: wlceventd_proc_event(527): eth1: Auth 22:9A:28:61:54:14, status: Successful (0), rssi:0
Aug 3 02:06:36 syslog: wlceventd_proc_event(537): eth1: ReAssoc 22:9A:28:61:54:14, status: Successful (0), rssi:0
Aug 3 02:11:50 syslog: wlceventd_proc_event(508): eth1: Disassoc D8:28:C9:5F:76:44, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 3 02:11:50 syslog: wlceventd_proc_event(527): eth1: Auth D8:28:C9:5F:76:44, status: Successful (0), rssi:0
Aug 3 02:11:50 syslog: wlceventd_proc_event(556): eth1: Assoc D8:28:C9:5F:76:44, status: Successful (0), rssi:0
Aug 3 02:11:51 kernel: D8:28:C9:5F:76:44 not mesh client, can't update it's ip
Aug 3 02:12:18 kernel: D8:28:C9:5F:76:44 not mesh client, can't update it's ip
Aug 3 02:20:14 kernel: watchdog/12289: potentially unexpected fatal signal 11.
Aug 3 02:20:14 kernel: Pid: 12289, comm: watchdog
Aug 3 02:20:14 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Aug 3 02:20:14 kernel: PC is at 0x2b121afc
Aug 3 02:20:14 kernel: LR is at 0x2b1218fc
Aug 3 02:20:14 kernel: pc : [<2b121afc>] lr : [<2b1218fc>] psr: 20000010
Aug 3 02:20:14 kernel: sp : 7ecd7298 ip : 2b139704 fp : 00000000
Aug 3 02:20:14 kernel: r10: 00000000 r9 : 000142e0 r8 : 0017319c
Aug 3 02:20:14 kernel: r7 : 00000000 r6 : 00000000 r5 : 00000010 r4 : 00000000
Aug 3 02:20:14 kernel: r3 : 00000000 r2 : 2b13e4e8 r1 : 00000000 r0 : 00000000
Aug 3 02:20:14 kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Aug 3 02:20:14 kernel: Control: 10c53c7d Table: 55bb804a DAC: 00000015
Aug 3 02:25:39 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Aug 3 02:25:39 rc_service: check_watchdog 442:notify_rc restart_watchdog
Aug 3 02:27:41 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7179)]periodic_check AM 5:13
Aug 3 02:27:44 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7243)]retrieve firmware information
Aug 3 02:27:44 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7257)]fimrware update check first time
Aug 3 02:27:44 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7285)]no need to upgrade firmware
Aug 3 02:55:32 syslog: wlceventd_proc_event(491): eth1: Deauth_ind 22:9A:28:61:54:14, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-68
Aug 3 02:55:32 syslog: wlceventd_proc_event(527): eth1: Auth 22:9A:28:61:54:14, status: Successful (0), rssi:0
Aug 3 02:55:32 syslog: wlceventd_proc_event(537): eth1: ReAssoc 22:9A:28:61:54:14, status: Successful (0), rssi:0
Aug 3 03:55:23 syslog: wlceventd_proc_event(491): eth1: Deauth_ind 22:9A:28:61:54:14, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-70
Aug 3 03:55:23 syslog: wlceventd_proc_event(527): eth1: Auth 22:9A:28:61:54:14, status: Successful (0), rssi:0
Aug 3 03:55:23 syslog: wlceventd_proc_event(537): eth1: ReAssoc 22:9A:28:61:54:14, status: Successful (0), rssi:0
- syslog.log-1 2179/2179 100%
 

L&LD

Part of the Furniture
Have you ever fully reset it since receiving it?
 

stephenspann27

New Around Here
I have not tried that yet. I guess as a first step, I could back up the config, wipe it, restore the config, and if that doesn't fix it, try it again without restoring the config.
 

L&LD

Part of the Furniture
Restoring the configuration via a backup after fully resetting the router is equivalent to not resetting the router. Particularly a backup of its current state.
 

Sign Up For SNBForums Daily Digest

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