RT-AX88U Pro - SimpliSafe device DHCP Lease Renewal Fails and is Dropped

[dwhitejazz]

Two days ago we updated our home router to the RT-AX88U Pro replacing our previous ASUS router. We kept the same network name and authentication password.

Everything was fine for 24 hours until the DHCP leases expired. We have 20 devices on our network. All of them renewed properly except the SimpliSafe base station. It would connect and "renew" its lease for about 2-4 seconds. Then the ASUS router would kick it off the network. My reset of the keystation pad and the base station by removing its batteries and waiting 5 minutes did not help. It would connect to the router properly but ASUS would kick it out. The system logs show this:

Aug 14 20:42:38 wlceventd: wlceventd_proc_event(685): eth6: Auth 18:93:7F:D9:82:74, status: Successful (0), rssi:-55
Aug 14 20:42:38 wlceventd: wlceventd_proc_event(722): eth6: Assoc 18:93:7F:D9:82:74, status: Successful (0), rssi:-55
Aug 14 20:42:41 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 4C:11:AE:7E:BF:34, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Aug 14 20:42:41 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 4C:11:AE:7E:BF:34, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Aug 14 20:42:42 wlceventd: wlceventd_proc_event(685): eth6: Auth 4C:11:AE:7E:BF:34, status: Successful (0), rssi:0
Aug 14 20:42:42 wlceventd: wlceventd_proc_event(722): eth6: Assoc 4C:11:AE:7E:BF:34, status: Successful (0), rssi:-23
Aug 14 20:42:47 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 18:93:7F:D9:82:74, status: 0, reason: Unspecified reason (1), rssi:0
Aug 14 20:42:47 wlceventd: wlceventd_proc_event(685): eth6: Auth 18:93:7F:D9:82:74, status: Successful (0), rssi:0
Aug 14 20:42:47 wlceventd: wlceventd_proc_event(722): eth6: Assoc 18:93:7F:D9:82:74, status: Successful (0), rssi:-55
Aug 14 20:42:51 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 4C:11:AE:7E:BF:34, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Aug 14 20:42:51 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 4C:11:AE:7E:BF:34, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Aug 14 20:42:51 wlceventd: wlceventd_proc_event(685): eth6: Auth 4C:11:AE:7E:BF:34, status: Successful (0), rssi:0
Aug 14 20:42:51 wlceventd: wlceventd_proc_event(722): eth6: Assoc 4C:11:AE:7E:BF:34, status: Successful (0), rssi:-23
Aug 14 20:43:01 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 4C:11:AE:7E:BF:34, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Aug 14 20:43:01 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 4C:11:AE:7E:BF:34, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0

There is one other SimpliSafe device, a camera, that was also in this state.

I had used the Merlin firmware on my previous ASUS router, and therefore I decided to update and replace and router's firmware with the Merlin alternative. After the upgrade the SimpliSafe devices were able to stay connected to the router. I don't know why the firmware upgrade "fixed" the issue. I'm waiting to see if the issue returns when the DHCP lease expires.

Does anyone have an explanation for what causes this issue and why the Merlin firmware upgrade appears to have fixed it? Is there a bug in the ASUS firmware that the Merlin firmware has addressed?

 

[dwhitejazz]

Two days ago we updated our home router to the RT-AX88U Pro replacing our previous ASUS router. We kept the same network name and authentication password.

Everything was fine for 24 hours until the DHCP leases expired. We have 20 devices on our network. All of them renewed properly except the SimpliSafe base station. It would connect and "renew" its lease for about 2-4 seconds. Then the ASUS router would kick it off the network. My reset of the keystation pad and the base station by removing its batteries and waiting 5 minutes did not help. It would connect to the router properly but ASUS would kick it out. The system logs show this:
Aug 14 20:42:38 wlceventd: wlceventd_proc_event(685): eth6: Auth 18:93:7F9:82:74, status: Successful (0), rssi:-55
Aug 14 20:42:38 wlceventd: wlceventd_proc_event(722): eth6: Assoc 18:93:7F9:82:74, status: Successful (0), rssi:-55
Aug 14 20:42:41 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 4C:11:AE:7E:BF:34, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Aug 14 20:42:41 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 4C:11:AE:7E:BF:34, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Aug 14 20:42:42 wlceventd: wlceventd_proc_event(685): eth6: Auth 4C:11:AE:7E:BF:34, status: Successful (0), rssi:0
Aug 14 20:42:42 wlceventd: wlceventd_proc_event(722): eth6: Assoc 4C:11:AE:7E:BF:34, status: Successful (0), rssi:-23
Aug 14 20:42:47 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 18:93:7F9:82:74, status: 0, reason: Unspecified reason (1), rssi:0
Aug 14 20:42:47 wlceventd: wlceventd_proc_event(685): eth6: Auth 18:93:7F9:82:74, status: Successful (0), rssi:0
Aug 14 20:42:47 wlceventd: wlceventd_proc_event(722): eth6: Assoc 18:93:7F9:82:74, status: Successful (0), rssi:-55
Aug 14 20:42:51 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 4C:11:AE:7E:BF:34, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Aug 14 20:42:51 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 4C:11:AE:7E:BF:34, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Aug 14 20:42:51 wlceventd: wlceventd_proc_event(685): eth6: Auth 4C:11:AE:7E:BF:34, status: Successful (0), rssi:0
Aug 14 20:42:51 wlceventd: wlceventd_proc_event(722): eth6: Assoc 4C:11:AE:7E:BF:34, status: Successful (0), rssi:-23
Aug 14 20:43:01 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 4C:11:AE:7E:BF:34, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Aug 14 20:43:01 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 4C:11:AE:7E:BF:34, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
... etc ...

There is one other SimpliSafe device, a camera, that was also in this state.

I had used the Merlin firmware on my previous ASUS router, and therefore I decided to update and replace and router's firmware with the Merlin alternative. After the upgrade the SimpliSafe devices were able to stay connected to the router. I don't know why the firmware upgrade "fixed" the issue. I'm waiting to see if the issue returns when the DHCP lease expires.

Does anyone have an explanation for what causes this issue and why the Merlin firmware upgrade appears to have fixed it? Is there a bug in the ASUS firmware that the Merlin firmware has addressed?

Sorry for the emoticons in the log snippet - the web interface is converting this part of the log into emoticons.

 

[wouterv]

Try the AX section of this forum, you are now in AC.
Just as a note: I had a RT-AX86U Pro for 3 days as replacement for my RT-AC68U, and returned it because of frequent disconnects of clients, back to the RT-AC68U and all normal again,

 

[dwhitejazz]

Try the AX section of this forum, you are now in AC.
Just as a note: I had a RT-AX86U Pro for 3 days as replacement for my RT-AC68U, and returned it because of frequent disconnects of clients, back to the RT-AC68U and all normal again,

Did you try the Merlin firmware before returning RT-AX86U Pro?

 

[doczenith1]

Sorry for the emoticons - the web interface is converting some hex entries in the log snippet into emoticons.

I believe if you use the "Code" button/option (</>) for the log text it will format better.

 

[dwhitejazz]

I believe if you use the "Code" button/option (</>) for the log text it will format better.

Thanks!

 

[wouterv]

Did you try the Merlin firmware before returning RT-AX86U Pro?

No, why would I need to try third party firmware to try to make basic functions of the router work?
There are new firmware releases after my trials, specially the one ‘Engineered for Intel® Evo™’ seems interesting as that for quite sure involves updated wireless drivers.