AiMesh node disconnect a few times a day

  • 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.

collider

New Around Here
I have 3 AC68U. Three of them are on the latest 386.1_2 (but this problem happened with several previous versions). One is configured in AiMesh AP mode. The other two are in AiMesh nodes backhauled by 5GHz wireless.

When clients are connected with the AP, everything is fine. But when clients are connected with any of the two nodes. There are Internet disconnections (WiFi is still connected while losing Internet) several times a day. This problem happens randomly on both of the AiMesh nodes. Though it just disconnect 2 or 3 mins, it is very annoying for online meeting,

I looked at the log and used the user scripts to find the problem. Looks like I found the problem but I don't know how to solve.

Here's the outputs of a simple script to timestamp the dhcpc-event:
Code:
deconfig
Sat Feb 13 19:06:46 EST 2021
leasefail
Sat Feb 13 19:06:56 EST 2021
leasefail
Sat Feb 13 19:07:09 EST 2021
bound
Sat Feb 13 19:07:35 EST 2021

Here's the output from system log for the same time period:
Code:
Feb 13 19:06:11 MISC: wifi upstream is connected, and disconnected from CAP.
Feb 13 19:06:46 custom_script: Running /jffs/scripts/dhcpc-event (args: deconfig)
Feb 13 19:06:46 avahi-daemon[448]: Withdrawing address record for 192.168.10.240 on br0.
Feb 13 19:06:46 avahi-daemon[448]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.10.240.
Feb 13 19:06:46 lldpd[208]: removal request for address of 192.168.10.240%10, but no knowledge of it
Feb 13 19:06:46 dnsmasq[1076]: stopped listening on br0(#10): 192.168.10.240 port 53
Feb 13 19:06:46 dnsmasq[1076]: listening on br0(#10): 192.168.1.1 port 53
Feb 13 19:06:46 avahi-daemon[448]: Interface br0.IPv4 no longer relevant for mDNS.
Feb 13 19:06:46 avahi-daemon[448]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.1.
Feb 13 19:06:46 avahi-daemon[448]: New relevant interface br0.IPv4 for mDNS.
Feb 13 19:06:46 avahi-daemon[448]: Registering new address record for 192.168.1.1 on br0.IPv4.
Feb 13 19:06:56 custom_script: Running /jffs/scripts/dhcpc-event (args: leasefail)
Feb 13 19:07:09 custom_script: Running /jffs/scripts/dhcpc-event (args: leasefail)
Feb 13 19:07:33 syslog: wlceventd_proc_event(490): eth2: Deauth_ind 94:10:3E:82:C2:0F, status: 0, reason: Group key update timeout (10), rssi:-68
Feb 13 19:07:35 custom_script: Running /jffs/scripts/dhcpc-event (args: bound)
Feb 13 19:07:35 rc_service: udhcpc_lan 10021:notify_rc stop_httpd
Feb 13 19:07:35 rc_service: udhcpc_lan 10021:notify_rc start_httpd
Feb 13 19:07:35 rc_service: waitting "stop_httpd" via udhcpc_lan ...
Feb 13 19:07:36 RT-AC68U: start httpd:80
Feb 13 19:07:36 avahi-daemon[448]: Withdrawing address record for 192.168.1.1 on br0.
Feb 13 19:07:36 avahi-daemon[448]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.1.
Feb 13 19:07:36 lldpd[208]: removal request for address of 192.168.1.1%10, but no knowledge of it
Feb 13 19:07:36 dnsmasq[1076]: stopped listening on br0(#10): 192.168.1.1 port 53
Feb 13 19:07:36 dnsmasq[1076]: listening on br0(#10): 192.168.10.240 port 53
Feb 13 19:07:36 avahi-daemon[448]: Interface br0.IPv4 no longer relevant for mDNS.
Feb 13 19:07:36 rc_service: udhcpc_lan 10021:notify_rc start_dnsmasq
Feb 13 19:07:36 rc_service: waitting "start_httpd" via udhcpc_lan ...
Feb 13 19:07:36 avahi-daemon[448]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.10.240.
Feb 13 19:07:36 avahi-daemon[448]: New relevant interface br0.IPv4 for mDNS.
Feb 13 19:07:36 avahi-daemon[448]: Registering new address record for 192.168.10.240 on br0.IPv4.
Feb 13 19:07:36 BHC: WiFi connection status change.

Seems to me, the node randomly drop the leased IP address and go back to the default 192.168.1.1 (the DHCP lease time is set to 48 hours and no problem for any other device) and course the leasefail. But it can get the new address lease in 1 or 2 mins.
 

fizix610

Occasional Visitor
I'm having the same issue! Do you see several "wlceventd_proc_event(490): wl0.1: Deauth_ind" events prior to this?
 

at_random

New Around Here
seeing the same problem! i do see "wlceventd_proc_event(490): wl0.1: Deauth_ind" events before this.
I even scheduled a nightly reboot (the ainodes also get rebooted!), but that didnt help.

1. did you guys figure this out?
2. what are 'user scripts'?
3. where did you find `dhcpc-event` log?

Thanks!
 

Latest threads

Sign Up For SNBForums Daily Digest

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