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

[stephenspann27]

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:FB4: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:FB4:0B, status: Successful (0), rssi:0
Aug 3 01:55:28 syslog: wlceventd_proc_event(556): eth1: Assoc 9C:7B:EF:FB4:0B, status: Successful (0), rssi:0
Aug 3 01:55:29 kernel: 9C:7B:EF:FB4: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_check7179)]periodic_check AM 5:13
Aug 3 02:27:44 WATCHDOG: [FAUPGRADE][auto_firmware_check7243)]retrieve firmware information
Aug 3 02:27:44 WATCHDOG: [FAUPGRADE][auto_firmware_check7257)]fimrware update check first time
Aug 3 02:27:44 WATCHDOG: [FAUPGRADE][auto_firmware_check7285)]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%

 

[stephenspann27]

Is there any other info I can provide to help? Looking for suggestions on a fix... I'm pulling my hair out.

 

[L&LD]

Have you ever fully reset it since receiving it?

 

[stephenspann27]

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]

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.

 

[stephenspann27]

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.

Argh, I was afraid of that. What a pain.

 

[jsteinm1]

Did you ever find the solution? I'm having the same problem with my RT-AC86U - it's most notable when trying to print from a wireless device to a printer that is also on wifi. When the issue is present, I can see on Windows that the printer is not part of the arp table and unable to ping the printer (but able to ping both devices from router). But once it starts working, an entry shows up in the arp table and its good to go for a while until it happens again.

 

[Frank Monroe]

I have had the same issue on my AC5300 running Merlin code. The issue was discussed in several other threads. I have attached one example of one thread below. I'm not sure if the issue is specific to Merlin or to the native ASUS firmware. However, revering back to Merlin 386.3_2 immediately fiedx the issue for me. I tested every Merlin release for the AC5300 since 386.3_2 and all of them had the issue.

arp problem between wifi devices on RT-AC88u

Hello, Sorry if this subject has already been discussed but I did not find an answer to my question, I have an RT-AC88U, and I have big problems of communication between wifi devices. It seems that it is a problem of propagation of ARP request between wifi equipments via the AC88U. Indeed, the...

www.snbforums.com

 

[jsteinm1]

I have had the same issue on my AC5300 running Merlin code. The issue was discussed in several other threads. I have attached one example of one thread below. I'm not sure if the issue is specific to Merlin or to the native ASUS firmware. However, revering back to Merlin 386.3_2 immediately fiedx the issue for me. I tested every Merlin release for the AC5300 since 386.3_2 and all of them had the issue.

arp problem between wifi devices on RT-AC88u

Hello, Sorry if this subject has already been discussed but I did not find an answer to my question, I have an RT-AC88U, and I have big problems of communication between wifi devices. It seems that it is a problem of propagation of ARP request between wifi equipments via the AC88U. Indeed, the...

www.snbforums.com

Thanks I'll try downgrading. Given the nature of the issue I'm not sure exactly when it started but might have been around the time I switched to Merlin FW (or just upgrading past that version if ASUS stock is affected too).

 

[bscabl]

I have had the same issue on my AC5300 running Merlin code. The issue was discussed in several other threads. I have attached one example of one thread below. I'm not sure if the issue is specific to Merlin or to the native ASUS firmware. However, revering back to Merlin 386.3_2 immediately fiedx the issue for me. I tested every Merlin release for the AC5300 since 386.3_2 and all of them had the issue.

arp problem between wifi devices on RT-AC88u

Hello, Sorry if this subject has already been discussed but I did not find an answer to my question, I have an RT-AC88U, and I have big problems of communication between wifi devices. It seems that it is a problem of propagation of ARP request between wifi equipments via the AC88U. Indeed, the...

www.snbforums.com

Im having the same issues on my ac3100 with 386.5_2 .. i lose arp, cant ping devices and cant ssh to them [no route to host] - i ssh into the router, ssh into the device, ping back to my desktop till it works, then everything works as normal. i wonder if downgrading will fix this as well

 

[wouterv]

Without knowing your exact setup:
In case of unexplained router behavior:

1. If there are, disconnect all USB devices.
2. Install the latest available firmware version.
3. Reset to factory defaults.
4. Do not load an old configuration backup file.
5. Manual configure the router with the bare minimum, as:
   • Router Login Name.
   • Router Login Password.
   • WAN Connection Type, and what is required to connect to the Internet.
   • Wireless SSID's and WPA Pre-Shared Key's.
   • Leave everything else default.
6. Test the router behavior:
   1. Test with a wired connection first.
   2. Test with a wireless connection.
7. After the above works all well you can consider more manual router configuration changes.

As said: restoring a configuration might bring back old issues, that is why the manual configuration is advised.
While making configuration changes: write them down, so you do have a list of changes you made from factory default.
And whenever you restore a configuration only restore to exactly the same firmware branch and version as it was made with.

 

[bscabl]

Downgrade solved my issue as well.. no arp/lost ping/ssh issues since going back to 386.3_2 - did the downgrade Thursday.

 

[mentaal]

Hi there,
Thank you very much for providing this information. I was a long time trying to figure out what was going on before discovering this site.
Do you know if this issue is tracked anywhere specifically so that it can be resolved in the more recent firmware images from Asus or within the AsusWrt Merlin firmware?
I am also using a wireguard VPN which looks to be, at the very minimum more cumbersome to setup with 386.3_2 and anyway I'd like to use the most recent image to avail of general security fixes as well.
In the meantime I will use this version and confirm if it resolves the problem for me too.
I am using an RT-AX86S router.
Thanks

 

[mentaal]

Hi Again,
Can anyone tell me me if this issue has been resolved in newer versions of the merlin firmware (or stock firmware for that matter)?
I have tried all the subsequent releases for the RT-AX86S router and I am still experiencing this problem.
Is there another location where this issue is tracked?
I don't really want to use an old version of the firmware.
Thank you!