Menu
What's new
By:
Filters Better Search

Smart Connect or AiMesh issue? AX88U has many kernel "signal 11" errors right after roamast: "deauth old sta" or "disconnect weak signal."

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

theirongiant

theirongiant

Regular Contributor
EDIT: I just noticed that 386.8_0 was released last Saturday. I'll try updating...

———

I am seeing errors in the logs that could indicate something going on with Smart Connect or AiMesh.

Symptoms:
  • The Wi-Fi on my AX88U has been very flaky the last couple of days.
  • Some smart devices have dropped off the network.
  • Ethernet seems to be unaffected.
  • Ping time to router is 5-25 ms until the "event" occurs.
  • Then the ping times soar well over 1000ms, and packets are delayed or lost.
Environment:
  • AX88U running build 386.8_alpha1-g09802d268a (just in case there is a known issue being tracked around any of this behavior)
  • One AiMesh node: RT-AC1900P, configured with 5GHz backhaul
  • Smart Connect is enabled
  • No custom scripts installed
  • No guest networks configured
  • IPSEC VPN configured but not active
While many users have posted the logs with the kernel 11 error, I couldn't find clear examples that included messages just before the crash. Personally, when I am reading logs, I find it helpful to have larger context around a specific error. The system may have logged something else that happened just prior.

Between syslog.log-1 and syslog.log, there are ~30 instances of this crash recorded in the last 36 hours.

Many look like this:

Code: 
Aug 14 04:04:14 wlceventd: wlceventd_proc_event(505): eth7: Auth 54:09:10:45:49:00, status: Successful (0)
Aug 14 04:04:14 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 54:09:10:45:49:00, status: 0, reason: Unspecified reason (1)
Aug 14 04:04:14 wlceventd: wlceventd_proc_event(505): eth7: Auth 54:09:10:45:49:00, status: Successful (0)
Aug 14 04:04:14 roamast: [EXAP]Deauth old sta in 0 0: 54:09:10:45:49:00
Aug 14 04:04:14 roamast: eth6: disconnect weak signal strength station [54:09:10:45:49:00]
Aug 14 04:04:14 kernel: potentially unexpected fatal signal 11.
Aug 14 04:04:14 kernel: CPU: 0 PID: 2704 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 04:04:14 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 04:04:14 kernel: task: ffffffc02b41b5c0 ti: ffffffc02b41c000 task.ti: ffffffc02b41c000
Aug 14 04:04:14 kernel: PC is at 0xf6d3072e
Aug 14 04:04:14 kernel: LR is at 0xf6cfc858
--
Aug 14 04:06:44 wlceventd: wlceventd_proc_event(505): eth7: Auth 54:09:10:45:49:00, status: Successful (0)
Aug 14 04:06:44 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 54:09:10:45:49:00, status: 0, reason: Unspecified reason (1)
Aug 14 04:06:44 wlceventd: wlceventd_proc_event(505): eth7: Auth 54:09:10:45:49:00, status: Successful (0)
Aug 14 04:06:45 roamast: [EXAP]Deauth old sta in 0 0: 54:09:10:45:49:00
Aug 14 04:06:45 roamast: eth6: disconnect weak signal strength station [54:09:10:45:49:00]
Aug 14 04:06:45 kernel: potentially unexpected fatal signal 11.
Aug 14 04:06:45 kernel: CPU: 1 PID: 4608 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 04:06:45 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 04:06:45 kernel: task: ffffffc02462f580 ti: ffffffc025018000 task.ti: ffffffc025018000
Aug 14 04:06:45 kernel: PC is at 0xf6b9472e
Aug 14 04:06:45 kernel: LR is at 0xf6b60858
--
Aug 14 04:09:58 hostapd: eth6: STA 54:09:10:45:49:00 IEEE 802.11: disassociated
Aug 14 04:09:59 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 54:09:10:45:49:00, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Aug 14 04:09:59 hostapd: eth6: STA 54:09:10:45:49:00 IEEE 802.11: disassociated
Aug 14 04:13:42 roamast: [EXAP]Deauth old sta in 1 0: 44:73:D6:21:A1:56
Aug 14 04:13:42 roamast: eth7: disconnect weak signal strength station [44:73:d6:21:a1:56]
Aug 14 04:13:42 kernel: potentially unexpected fatal signal 11.
Aug 14 04:13:42 kernel: CPU: 2 PID: 5181 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 04:13:42 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 04:13:42 kernel: task: ffffffc02c85d5c0 ti: ffffffc02474c000 task.ti: ffffffc02474c000
Aug 14 04:13:42 kernel: PC is at 0xf67ff72e
Aug 14 04:13:42 kernel: LR is at 0xf67cb858

And this sample:

Code: 
Aug 14 15:18:39 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 15:18:43 dnsmasq-dhcp[4329]: DHCPREQUEST(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 15:18:43 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 15:18:43 roamast: [EXAP]Deauth old sta in 1 0: 26:E0:DF:D8:CF:93
Aug 14 15:18:43 roamast: eth7: disconnect weak signal strength station [26:e0:df:d8:cf:93]
Aug 14 15:18:43 kernel: potentially unexpected fatal signal 11.
Aug 14 15:18:43 kernel: CPU: 1 PID: 28471 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 15:18:43 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 15:18:43 kernel: task: ffffffc02ff5cac0 ti: ffffffc02b638000 task.ti: ffffffc02b638000
Aug 14 15:18:43 kernel: PC is at 0xf6adb72e
Aug 14 15:18:43 kernel: LR is at 0xf6aa7858
--
Aug 14 15:38:09 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.110 58:d5:0a:b3:f2:f7 GW-58D50AB3F2F7
Aug 14 15:42:27 dnsmasq-dhcp[4329]: DHCPREQUEST(br0) 192.168.11.115 b0:be:83:e1:9b:c2
Aug 14 15:42:27 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.115 b0:be:83:e1:9b:c2 CECEN-HC49HQ6LR
Aug 14 15:42:27 roamast: [EXAP]Deauth old sta in 1 0: B0:BE:83:E1:9B:C2
Aug 14 15:42:27 roamast: eth7: disconnect weak signal strength station [b0:be:83:e1:9b:c2]
Aug 14 15:42:27 kernel: potentially unexpected fatal signal 11.
Aug 14 15:42:27 kernel: CPU: 1 PID: 28016 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 15:42:27 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 15:42:27 kernel: task: ffffffc02f265540 ti: ffffffc02470c000 task.ti: ffffffc02470c000
Aug 14 15:42:27 kernel: PC is at 0xf6ad26a4
Aug 14 15:42:27 kernel: LR is at 0xf6a9e858
--
Aug 14 16:01:06 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 26:E0:DF:D8:CF:93, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9)
Aug 14 16:01:06 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 26:E0:DF:D8:CF:93, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Aug 14 16:01:06 hostapd: eth7: STA 26:e0:df:d8:cf:93 IEEE 802.11: disassociated
Aug 14 16:01:06 roamast: [EXAP]Deauth old sta in 1 0: 26:E0:DF:D8:CF:93
Aug 14 16:01:06 roamast: eth7: disconnect weak signal strength station [26:e0:df:d8:cf:93]
Aug 14 16:01:06 kernel: potentially unexpected fatal signal 11.
Aug 14 16:01:06 kernel: CPU: 3 PID: 31111 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 16:01:06 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 16:01:06 kernel: task: ffffffc02b41abc0 ti: ffffffc028dc8000 task.ti: ffffffc028dc8000
Aug 14 16:01:06 kernel: PC is at 0xf68f572e
Aug 14 16:01:06 kernel: LR is at 0xf68c1858

And this one, showing messages relating to a mesh client that is later deauth'ed and dropped, which precedes the crash.

Code: 
Aug 14 22:21:50 dnsmasq-dhcp[4329]: DHCPREQUEST(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 22:21:50 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 22:21:50 kernel: 26:E0:DF:D8:CF:93 not mesh client, can't update it's ip
Aug 14 22:49:43 dnsmasq-dhcp[4329]: DHCPREQUEST(br0) 192.168.11.166 ac:7a:56:d1:bd:80
Aug 14 22:49:43 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.166 ac:7a:56:d1:bd:80 ucs-wifikit-vr01
Aug 14 22:53:55 dnsmasq-dhcp[4329]: DHCPREQUEST(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 22:53:55 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 22:53:55 kernel: 26:E0:DF:D8:CF:93 not mesh client, can't update it's ip
Aug 14 22:53:57 roamast: [EXAP]Deauth old sta in 1 0: 26:E0:DF:D8:CF:93
Aug 14 22:53:57 roamast: eth7: disconnect weak signal strength station [26:e0:df:d8:cf:93]
Aug 14 22:53:57 kernel: potentially unexpected fatal signal 11.
Aug 14 22:53:57 kernel: CPU: 1 PID: 17995 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 22:53:57 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 22:53:57 kernel: task: ffffffc02cb03500 ti: ffffffc029ba4000 task.ti: ffffffc029ba4000
Aug 14 22:53:57 kernel: PC is at 0xf6a3172e
Aug 14 22:53:57 kernel: LR is at 0xf69fd858

Note the timing of the crashes: it's happening at the same time as a message from "roamast," the Roaming Assistant. The computer I'm on right now is NOT being diverted to the AiMesh node; it's still connected to the primary router.

Is this advice still relevant? https://www.snbforums.com/threads/wifi-aimesh-disconnects-for-a-few-seconds.47472/post-414933

Is there any other data I can collect on the roaming assistant to help analyze this?
 
Last edited:
theirongiant said:
I am seeing errors in the logs that could indicate something going on with Smart Connect or AiMesh.

Symptoms:
  • The Wi-Fi on my AX88U has been very flaky the last couple of days.
  • Some smart devices have dropped off the network.
  • Ethernet seems to be unaffected.
  • Ping time to router is 5-25 ms until the "event" occurs.
  • Then the ping times soar well over 1000ms, and packets are delayed or lost.
Environment:
  • AX88U running build 386.8_alpha1-g09802d268a (just in case there is a known issue being tracked around any of this behavior)
  • One AiMesh node: RT-AC1900P, configured with 5GHz backhaul
  • Smart Connect is enabled
  • No custom scripts installed
  • No guest networks configured
  • IPSEC VPN configured but not active
While many users have posted the logs with the kernel 11 error, I couldn't find clear examples that included messages just before the crash. Personally, when I am reading logs, I find it helpful to have larger context around a specific error. The system may have logged something else that happened just prior.

Between syslog.log-1 and syslog.log, there are ~30 instances of this crash recorded in the last 36 hours.

Many look like this:

Code: 
Aug 14 04:04:14 wlceventd: wlceventd_proc_event(505): eth7: Auth 54:09:10:45:49:00, status: Successful (0)
Aug 14 04:04:14 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 54:09:10:45:49:00, status: 0, reason: Unspecified reason (1)
Aug 14 04:04:14 wlceventd: wlceventd_proc_event(505): eth7: Auth 54:09:10:45:49:00, status: Successful (0)
Aug 14 04:04:14 roamast: [EXAP]Deauth old sta in 0 0: 54:09:10:45:49:00
Aug 14 04:04:14 roamast: eth6: disconnect weak signal strength station [54:09:10:45:49:00]
Aug 14 04:04:14 kernel: potentially unexpected fatal signal 11.
Aug 14 04:04:14 kernel: CPU: 0 PID: 2704 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 04:04:14 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 04:04:14 kernel: task: ffffffc02b41b5c0 ti: ffffffc02b41c000 task.ti: ffffffc02b41c000
Aug 14 04:04:14 kernel: PC is at 0xf6d3072e
Aug 14 04:04:14 kernel: LR is at 0xf6cfc858
--
Aug 14 04:06:44 wlceventd: wlceventd_proc_event(505): eth7: Auth 54:09:10:45:49:00, status: Successful (0)
Aug 14 04:06:44 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 54:09:10:45:49:00, status: 0, reason: Unspecified reason (1)
Aug 14 04:06:44 wlceventd: wlceventd_proc_event(505): eth7: Auth 54:09:10:45:49:00, status: Successful (0)
Aug 14 04:06:45 roamast: [EXAP]Deauth old sta in 0 0: 54:09:10:45:49:00
Aug 14 04:06:45 roamast: eth6: disconnect weak signal strength station [54:09:10:45:49:00]
Aug 14 04:06:45 kernel: potentially unexpected fatal signal 11.
Aug 14 04:06:45 kernel: CPU: 1 PID: 4608 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 04:06:45 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 04:06:45 kernel: task: ffffffc02462f580 ti: ffffffc025018000 task.ti: ffffffc025018000
Aug 14 04:06:45 kernel: PC is at 0xf6b9472e
Aug 14 04:06:45 kernel: LR is at 0xf6b60858
--
Aug 14 04:09:58 hostapd: eth6: STA 54:09:10:45:49:00 IEEE 802.11: disassociated
Aug 14 04:09:59 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 54:09:10:45:49:00, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Aug 14 04:09:59 hostapd: eth6: STA 54:09:10:45:49:00 IEEE 802.11: disassociated
Aug 14 04:13:42 roamast: [EXAP]Deauth old sta in 1 0: 44:73:D6:21:A1:56
Aug 14 04:13:42 roamast: eth7: disconnect weak signal strength station [44:73:d6:21:a1:56]
Aug 14 04:13:42 kernel: potentially unexpected fatal signal 11.
Aug 14 04:13:42 kernel: CPU: 2 PID: 5181 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 04:13:42 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 04:13:42 kernel: task: ffffffc02c85d5c0 ti: ffffffc02474c000 task.ti: ffffffc02474c000
Aug 14 04:13:42 kernel: PC is at 0xf67ff72e
Aug 14 04:13:42 kernel: LR is at 0xf67cb858

And this sample:

Code: 
Aug 14 15:18:39 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 15:18:43 dnsmasq-dhcp[4329]: DHCPREQUEST(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 15:18:43 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 15:18:43 roamast: [EXAP]Deauth old sta in 1 0: 26:E0:DF:D8:CF:93
Aug 14 15:18:43 roamast: eth7: disconnect weak signal strength station [26:e0:df:d8:cf:93]
Aug 14 15:18:43 kernel: potentially unexpected fatal signal 11.
Aug 14 15:18:43 kernel: CPU: 1 PID: 28471 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 15:18:43 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 15:18:43 kernel: task: ffffffc02ff5cac0 ti: ffffffc02b638000 task.ti: ffffffc02b638000
Aug 14 15:18:43 kernel: PC is at 0xf6adb72e
Aug 14 15:18:43 kernel: LR is at 0xf6aa7858
--
Aug 14 15:38:09 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.110 58:d5:0a:b3:f2:f7 GW-58D50AB3F2F7
Aug 14 15:42:27 dnsmasq-dhcp[4329]: DHCPREQUEST(br0) 192.168.11.115 b0:be:83:e1:9b:c2
Aug 14 15:42:27 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.115 b0:be:83:e1:9b:c2 CECEN-HC49HQ6LR
Aug 14 15:42:27 roamast: [EXAP]Deauth old sta in 1 0: B0:BE:83:E1:9B:C2
Aug 14 15:42:27 roamast: eth7: disconnect weak signal strength station [b0:be:83:e1:9b:c2]
Aug 14 15:42:27 kernel: potentially unexpected fatal signal 11.
Aug 14 15:42:27 kernel: CPU: 1 PID: 28016 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 15:42:27 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 15:42:27 kernel: task: ffffffc02f265540 ti: ffffffc02470c000 task.ti: ffffffc02470c000
Aug 14 15:42:27 kernel: PC is at 0xf6ad26a4
Aug 14 15:42:27 kernel: LR is at 0xf6a9e858
--
Aug 14 16:01:06 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 26:E0:DF:D8:CF:93, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9)
Aug 14 16:01:06 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 26:E0:DF:D8:CF:93, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Aug 14 16:01:06 hostapd: eth7: STA 26:e0:df:d8:cf:93 IEEE 802.11: disassociated
Aug 14 16:01:06 roamast: [EXAP]Deauth old sta in 1 0: 26:E0:DF:D8:CF:93
Aug 14 16:01:06 roamast: eth7: disconnect weak signal strength station [26:e0:df:d8:cf:93]
Aug 14 16:01:06 kernel: potentially unexpected fatal signal 11.
Aug 14 16:01:06 kernel: CPU: 3 PID: 31111 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 16:01:06 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 16:01:06 kernel: task: ffffffc02b41abc0 ti: ffffffc028dc8000 task.ti: ffffffc028dc8000
Aug 14 16:01:06 kernel: PC is at 0xf68f572e
Aug 14 16:01:06 kernel: LR is at 0xf68c1858

And this one, showing messages relating to a mesh client that is later deauth'ed and dropped, which precedes the crash.

Code: 
Aug 14 22:21:50 dnsmasq-dhcp[4329]: DHCPREQUEST(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 22:21:50 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 22:21:50 kernel: 26:E0:DF:D8:CF:93 not mesh client, can't update it's ip
Aug 14 22:49:43 dnsmasq-dhcp[4329]: DHCPREQUEST(br0) 192.168.11.166 ac:7a:56:d1:bd:80
Aug 14 22:49:43 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.166 ac:7a:56:d1:bd:80 ucs-wifikit-vr01
Aug 14 22:53:55 dnsmasq-dhcp[4329]: DHCPREQUEST(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 22:53:55 dnsmasq-dhcp[4329]: DHCPACK(br0) 192.168.11.223 26:e0:df:d8:cf:93
Aug 14 22:53:55 kernel: 26:E0:DF:D8:CF:93 not mesh client, can't update it's ip
Aug 14 22:53:57 roamast: [EXAP]Deauth old sta in 1 0: 26:E0:DF:D8:CF:93
Aug 14 22:53:57 roamast: eth7: disconnect weak signal strength station [26:e0:df:d8:cf:93]
Aug 14 22:53:57 kernel: potentially unexpected fatal signal 11.
Aug 14 22:53:57 kernel: CPU: 1 PID: 17995 Comm: roamast Tainted: P           O    4.1.51 #2
Aug 14 22:53:57 kernel: Hardware name: Broadcom-v8A (DT)
Aug 14 22:53:57 kernel: task: ffffffc02cb03500 ti: ffffffc029ba4000 task.ti: ffffffc029ba4000
Aug 14 22:53:57 kernel: PC is at 0xf6a3172e
Aug 14 22:53:57 kernel: LR is at 0xf69fd858

Note the timing of the crashes: it's happening at the same time as a message from "roamast," the Roaming Assistant. The computer I'm on right now is NOT being diverted to the AiMesh node; it's still connected to the primary router.

Is this advice still relevant? https://www.snbforums.com/threads/wifi-aimesh-disconnects-for-a-few-seconds.47472/post-414933

Is there any other data I can collect on the roaming assistant to help analyze this?
Click to expand...
Can you remove BETA tag as you don't release any beta. !
 
Same here on my rt-ax88u or similar and also my parents have similar on rt-ax58u.
Both have aimesh.

Logs are full these:

Code: 
Aug 17 07:18:41 roamast: [EXAP]Deauth old sta in 1 0: ##:##:##:##:##:##
Aug 17 07:18:41 roamast: eth7: disconnect weak signal strength station [##:##:##:##:##:##]
Aug 17 07:18:41 kernel: CPU: 3 PID: 14698 Comm: roamast Tainted: P           O    4.1.51 #4
Aug 17 07:18:41 kernel: Hardware name: Broadcom-v8A (DT)
Aug 17 07:18:41 kernel: task: ffffffc032a00040 ti: ffffffc0268c4000 task.ti: ffffffc0268c4000
Aug 17 07:18:41 kernel: PC is at 0xf6b1272e
Aug 17 07:18:41 kernel: LR is at 0xf6ade858
Aug 17 07:18:41 kernel: pc : [<00000000f6b1272e>] lr : [<00000000f6ade858>] pstate: 20000030
Aug 17 07:18:41 kernel: sp : 00000000f6a9acb0
Aug 17 07:18:41 kernel: x12: 00000000ffffffff
Aug 17 07:18:41 kernel: x11: 00000000f6a9b1ac x10: 0000000000000000
Aug 17 07:18:41 kernel: x9 : 00000000f6bd87a8 x8 : 00000000f6bda000
Aug 17 07:18:41 kernel: x7 : 00000000f6a9c920 x6 : 0000000000000021
Aug 17 07:18:41 kernel: x5 : 00000000001c68ee x4 : 0000000000000006
Aug 17 07:18:41 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Aug 17 07:18:41 kernel: x1 : 0000000000000090 x0 : 0000000000000096
Aug 17 07:18:49 wlceventd: wlceventd_proc_event(530): eth7: Auth ##:##:##:##:##:##, status: Successful (0), rssi:0
Aug 17 07:18:49 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc ##:##:##:##:##:##, status: Successful (0), rssi:-65
Aug 17 07:19:07 roamast: ROAMING Start...

I haven't noticed any big issue with that.

Oh, and btw. For me this reply probably shouldn't be here. Because I'm using Asus latest"orginal" firmware(not merlin).
 
Make sure you have the Roam Assistant setting in the professional tab (all bands) Disabled.

Since AI Mesh 2.0, you will see roamast: entries for the 'roaming' that the Mesh code manages. The old Professional Roam Assistant setting is just a dumb setting that will kick stations, forcing them to renegotiate the setup and link - something that defeats the purpose of AI Mesh, but it also logs to syslog using the same name.

Make sure you have universal beamforming off as well as Airtime fairness. Fixed channels too.

More detail from a previous post of mine.

www.snbforums.com

smart connect and roaming assist

I have a Aimesh setup with AX86S as main router with 2x AX58U nodes. Overall I am very happy with the AX86S and how smart connect works. I have a few 2.4ghz only devices (printer, robot vacuum etc) and they sometimes get stuck on a node with a lower strength connection (below the smart connect...
www.snbforums.com www.snbforums.com
 
CaptnDanLKW said:
Make sure you have the Roam Assistant setting in the professional tab (all bands) Disabled.

Since AI Mesh 2.0, you will see roamast: entries for the 'roaming' that the Mesh code manages. The old Professional Roam Assistant setting is just a dumb setting that will kick stations, forcing them to renegotiate the setup and link - something that defeats the purpose of AI Mesh, but it also logs to syslog using the same name.

Make sure you have universal beamforming off as well as Airtime fairness. Fixed channels too.

More detail from a previous post of mine.

www.snbforums.com

smart connect and roaming assist

I have a Aimesh setup with AX86S as main router with 2x AX58U nodes. Overall I am very happy with the AX86S and how smart connect works. I have a few 2.4ghz only devices (printer, robot vacuum etc) and they sometimes get stuck on a node with a lower strength connection (below the smart connect...
www.snbforums.com www.snbforums.com
Click to expand...
Thanks, will try that! Channels are fixed, but seems universal beamforming was on and also roam assistant.

Update: turning off roam assistant did the trick. I'm not sure about about smart connect(because I use different SSIDs for 2.4 and 5Ghz).
 
Last edited:
You must log in or register to reply here.

Similar threads

M
Multiple Kernel log messages
Replies
2
Views
1K
bbunge
bbunge
S
Micro disconnects, cant find source
Replies
11
Views
2K
saeris
S
M
RT-ACRH13 WiFi 2.4 issues
Replies
4
Views
1K
mrmmm
M
B
Asus RT-AC68U becomes unresponsive in bridge mode
Replies
4
Views
5K
GDT
G
E
Your ISP's DHCP does not function correctly
Replies
16
Views
6K
Gregory Phillips
Gregory Phillips
Similar threads
Thread starter Title Forum Replies Date
elrengo RT-AX88U Pro - Block YouTube on Smart TV Asuswrt-Merlin 12
TheLyppardMan Smart Band Steering Asuswrt-Merlin 30
L Devices Connect to Wi-Fi but No Internet Asuswrt-Merlin 8
S [AC88U] How to connect 2 separated networks into 1 VLAN Asuswrt-Merlin 2
6 VPN Director ok, device no connect. Asuswrt-Merlin 20
N AiMesh, router stock asus, wired AP merlin. Cant connect to AP 5ghz Asuswrt-Merlin 4
fenguix Wireguard server: can't connect SMB volumes Asuswrt-Merlin 6
C RT-AX86U 3004.388.8_2 . pet feeder app cannot connect to wifi why? Asuswrt-Merlin 6
C Can't connect to DYNDNS when Unbound is enabled ! Asuswrt-Merlin 10
B Solved What VPN Director rule should i use to be able to connect outside my home to my VPN provider? Asuswrt-Merlin 2

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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

Members online

Total: 827 (members: 29, guests: 798)
Top