AX86U v386.4 Samsung Tablet Woes

[Wolfclaw]

Have two Samsung A6 tablets that both now have issues connecting to WIFi since last dirty update.
So reset router to factory defaults wiping out everything and manual reconfigured with settings that have work fine in v386.2 and earlier using WPA2-Personal AES
Using either frequencies, will not connect, so reset tablet to factory fresh and tried connecting to 5ghz CH56 and I'm sitting within arms length of router.
Anybody have a clue, wife moaning

Jan 26 17:42:28 wlceventd: wlceventd_proc_event(505): eth7: Auth 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:42:28 wlceventd: wlceventd_proc_event(534): eth7: Assoc 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:42:28 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: associated
Jan 26 17:42:34 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:42:34 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:42:34 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:42:34 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:42:35 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Disassociated due to inactivity (4)
Jan 26 17:42:35 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:42:50 wlceventd: wlceventd_proc_event(505): eth7: Auth 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:42:50 wlceventd: wlceventd_proc_event(534): eth7: Assoc 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:42:50 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: associated
Jan 26 17:42:56 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:42:56 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:42:56 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:42:56 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:42:57 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Disassociated due to inactivity (4)
Jan 26 17:42:57 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:43:16 wlceventd: wlceventd_proc_event(505): eth7: Auth 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:43:16 wlceventd: wlceventd_proc_event(534): eth7: Assoc 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:43:16 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: associated
Jan 26 17:43:22 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:43:22 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:43:22 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:43:22 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:43:23 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Disassociated due to inactivity (4)
Jan 26 17:43:23 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:43:35 wlceventd: wlceventd_proc_event(505): eth7: Auth 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:43:35 wlceventd: wlceventd_proc_event(534): eth7: Assoc 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:43:35 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: associated
Jan 26 17:43:42 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:43:42 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:43:42 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:43:42 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:43:43 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Disassociated due to inactivity (4)
Jan 26 17:43:43 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:44:01 wlceventd: wlceventd_proc_event(505): eth7: Auth 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:44:01 wlceventd: wlceventd_proc_event(534): eth7: Assoc 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:44:01 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: associated
Jan 26 17:44:07 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:44:07 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:44:07 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:44:07 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:44:08 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Disassociated due to inactivity (4)
Jan 26 17:44:08 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:44:20 wlceventd: wlceventd_proc_event(505): eth7: Auth 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:44:20 wlceventd: wlceventd_proc_event(534): eth7: Assoc 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:44:20 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: associated
Jan 26 17:44:27 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:44:27 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:44:27 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:44:27 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:44:28 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Disassociated due to inactivity (4)
Jan 26 17:44:28 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:44:41 wlceventd: wlceventd_proc_event(505): eth7: Auth 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:44:41 wlceventd: wlceventd_proc_event(534): eth7: Assoc 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:44:41 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: associated
Jan 26 17:44:47 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:44:47 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 26 17:44:47 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:44:47 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:44:48 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:B50:B5:4A:69, status: 0, reason: Disassociated due to inactivity (4)
Jan 26 17:44:48 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: disassociated
Jan 26 17:45:01 wlceventd: wlceventd_proc_event(505): eth7: Auth 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:45:01 wlceventd: wlceventd_proc_event(534): eth7: Assoc 00:B50:B5:4A:69, status: Successful (0)
Jan 26 17:45:01 hostapd: eth7: STA 00:b5:d0:b5:4a:69 IEEE 802.11: associated
Jan 26 17:45:04 hostapd: eth7: STA 00:b5:d0:b5:4a:69 RADIUS: starting accounting session CFED2D407763C09D
Jan 26 17:45:04 hostapd: eth7: STA 00:b5:d0:b5:4a:69 WPA: pairwise key handshake completed (RSN)

 

[heywire]

Welcome to the club: https://www.snbforums.com/threads/386-4-ac86u-losing-2-4-ghz-devices.77018/#post-740169

 

[Lee MacMillan]

FWIW, I haven't had any issues with either of my Samsung tablets: a 5 year old Tab S2 (running Lineage OS 17.1) or my stock Tab A7. Both connect and stay connected to the 5Ghz band on 386.4.

 

[Wolfclaw]

Glad it's not just me, so Asus have drooped the ball and now we have to wait for a fix, if any.

 

[Morris]

Welcome to the club: https://www.snbforums.com/threads/386-4-ac86u-losing-2-4-ghz-devices.77018/#post-740169

This thread is about the RT-AC86U and the OP has a RT-AX86u. There are no known issues with the RT-AX86u

 

[Morris]

Glad it's not just me, so Asus have drooped the ball and now we have to wait for a fix, if any.

No, That thread is about the RT-AC86U and you have a RT-AX86u. There are no known issues with the RT-AX86u which is considered by many on this forum to be the best version. I have no issues at all with it. Are you using the default wireless settings or did you change things after the factory reset and if so what and why?

Morris

 

[heywire]

No, That thread is about the RT-AC86U and you have a RT-AX86u. There are no known issues with the RT-AX86u which is considered by many on this forum to be the best version. I have no issues at all with it. Are you using the default wireless settings or did you change things after the factory reset and if so what and why?

Morris

If you check the links in that thread, you'll find out that the connection-drop issues also extend to the latest AX routers, especially with the last Merlin release.

 

[peng]

My AX56U showing same logs with Samsung devices as well, but actual signal drop only happened one time.

 

[Morris]

If you check the links in that thread, you'll find out that the connection-drop issues also extend to the latest AX routers, especially with the last Merlin release.

Interesting. I don't have drops. It is probably a difference in settings

 

[Morris]

To all those having drops, please make the following changes:
- Disable Smart Connect. Smart connect works by dropping clients and hoping they will reconnect
- Disable Rooming Assistant. It also works by dropping clients
- Universal Beamforming - Non standard based game that can cause issues
- Explicit Beamforming - It is not clear what standard is used. Might cause issues.

Good luck,

Morris

 

[Wolfclaw]

As I said, been using these setting for many a version without a problem with the tablets failing to connect.

 

[Morris]

View attachment 39028View attachment 39029
As I said, been using these setting for many a version without a problem with the tablets failing to connect.

You have a problem and are too stubborn to try suggestions that could fix you issues. Guess you will have to live with them.

Morris

 

[DarkKnight75]

View attachment 39028View attachment 39029
As I said, been using these setting for many a version without a problem with the tablets failing to connect.

If you don't change settings you'll never know if it'll work....btw...on my ac86u, the 2.4ghz pro settings I have disabled the last 4 amd no issues...running Merlin 386.4 with multiple samsung tablets and no drops...going on 25 days uptime.

 

[DroidST]

To all those having drops, please make the following changes:
- Disable Smart Connect. Smart connect works by dropping clients and hoping they will reconnect
- Disable Rooming Assistant. It also works by dropping clients
- Universal Beamforming - Non standard based game that can cause issues
- Explicit Beamforming - It is not clear what standard is used. Might cause issues.

Good luck,

Morris

From memory, without checking my notes and my current AC86U config, I believe this info is correct. I have a new AX86U (delivered 1/22/2022) and will be loading current Merlin and transitioning it to our Primary Router soon, replacing the AC86U. The AC86U will be placed at another corner of the house and configured for AiMesh (The 68U will also be switched from a Repeater to AiMesh node).

 

[Viktor Jaep]

As I said, been using these setting for many a version without a problem with the tablets failing to connect.

I have an AC86U, and I have to say, we have very little in common with these settings that you posted. I also have multiple Samsung tablets in the house, but none are experiencing any connection issues whatsover. I would heed @Morris 's advice.

 

[Wolfclaw]

You misunderstood me, more than happy to change any setting the community suggests and will take onboard Morris suggestions, little or no point asking for assistance otherwise. Just strange issues has shown up now after years of same config.

 

[Wolfclaw]

Did as Morris suggested and issue remains, even disabled the WMM and AMPDU, any other suggestions ?

 

[capncybo]

Did as Morris suggested and issue remains, even disabled the WMM and AMPDU, any other suggestions ?

Have you tried a slower modulation scheme: Wireless>Professional>Modulation Scheme: UP to MCS 7 (802.11n)?

 

[Viktor Jaep]

Did as Morris suggested and issue remains, even disabled the WMM and AMPDU, any other suggestions ?

Please take a look at my settings, @Wolfclaw ... not sure if this will help, but give it a shot? I don't have any issues with our samsung tablets/TVs dropping.

 

[Morris]

Did as Morris suggested and issue remains, even disabled the WMM and AMPDU, any other suggestions ?

I just had a very carful look at your log. The Samsung host is associating and then experiences a deauthorization.

Have the Samsung host forget the network. Then connect as if you never connected to your network. I suspect you are looking at a host that is confused and sending the incorrect security string. This can happen when APs are changed or reconfigured.

Good luck,

Morris