AiMesh nodes disconnect since 386.1

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

VMARKUS_K

Occasional Visitor
Hello,

I have a setup of one rt-ac68u and two rt-ac67u. Both rt-ac67u are connected to the rt-ac68u. Starting with the upgrade to 386.1 the AiMesh nodes almost daliy reconnect and all connected clients loose their connection.

I have configured a preferred aimesh backbone for the nodes 5GHz connection quality is excellent.

Does anyone else see this behavior?
 

OzarkEdge

Part of the Furniture
Hello,

I have a setup of one rt-ac68u and two rt-ac67u. Both rt-ac67u are connected to the rt-ac68u. Starting with the upgrade to 386.1 the AiMesh nodes almost daliy reconnect and all connected clients loose their connection.

I have configured a preferred aimesh backbone for the nodes 5GHz connection quality is excellent.

Does anyone else see this behavior?

Did you reset the firmware on all nodes and configure the AC68U from scratch?

OE
 

OzarkEdge

Part of the Furniture

VMARKUS_K

Occasional Visitor
I have done a reset of all nodes. Issue occured again this morning.

I have configured a preferred connection point for the nodes. Might this be a possible cause?
 

VMARKUS_K

Occasional Visitor
Reconnect of RT-AC67U-9EC8 happened around 7am:

Code:
Feb 16 06:42:20 kernel: nvram: consolidating space!
Feb 16 06:00:03 Skynet: [#] 49804 IPs (+0) -- 1716 Ranges Banned (+0) || 2018 Inbound -- 0 Outbound Connections Blocked! [save] [3s]
Feb 16 07:02:10 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) a0:28:ed:0d:c0:aa
Feb 16 07:02:10 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.182 a0:28:ed:0d:c0:aa
Feb 16 07:02:10 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.182 a0:28:ed:0d:c0:aa
Feb 16 07:02:10 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.182 a0:28:ed:0d:c0:aa
Feb 16 07:03:06 syslog: wlceventd_proc_event(526): eth1: Auth 02:59:71:DC:67:B6, status: Successful (0), rssi:0
Feb 16 07:03:06 syslog: wlceventd_proc_event(536): eth1: ReAssoc 02:59:71:DC:67:B6, status: Successful (0), rssi:0
Feb 16 07:03:36 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:03:36 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.246 04:d9:f5:96:aa:88 RT-AC67U-AA88
Feb 16 07:03:44 syslog: wlceventd_proc_event(526): eth2: Auth A0:28:ED:0D:C0:AA, status: Successful (0), rssi:0
Feb 16 07:03:44 syslog: wlceventd_proc_event(555): eth2: Assoc A0:28:ED:0D:C0:AA, status: Successful (0), rssi:0
Feb 16 07:03:44 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) a0:28:ed:0d:c0:aa
Feb 16 07:03:44 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.182 a0:28:ed:0d:c0:aa
Feb 16 07:03:44 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.182 a0:28:ed:0d:c0:aa
Feb 16 07:03:44 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.182 a0:28:ed:0d:c0:aa
Feb 16 07:03:46 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:03:46 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.246 04:d9:f5:96:aa:88 RT-AC67U-AA88
Feb 16 07:03:51 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:03:51 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.246 04:d9:f5:96:aa:88 RT-AC67U-AA88
Feb 16 07:03:53 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:03:53 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.246 04:d9:f5:96:aa:88 RT-AC67U-AA88
Feb 16 07:03:54 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:03:54 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.246 04:d9:f5:96:aa:88 RT-AC67U-AA88
Feb 16 07:03:54 rc_service: httpd 18473:notify_rc restart_httpd
Feb 16 07:03:54 custom_script: Running /jffs/scripts/service-event (args: restart httpd)
Feb 16 07:03:55 RT-AC68U: start httpd:80
Feb 16 07:03:55 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:03:55 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:03:56 httpd: Save SSL certificate...80
Feb 16 07:03:56 httpd: mssl_cert_key_match : PASS
Feb 16 07:03:57 httpd: Succeed to init SSL certificate...80
Feb 16 07:03:58 rc_service: httpd 14652:notify_rc restart_httpd
Feb 16 07:03:58 custom_script: Running /jffs/scripts/service-event (args: restart httpd)
Feb 16 07:03:58 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:03:58 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:03:59 RT-AC68U: start httpd:80
Feb 16 07:04:00 httpd: Save SSL certificate...80
Feb 16 07:04:00 httpd: mssl_cert_key_match : PASS
Feb 16 07:04:01 httpd: Succeed to init SSL certificate...80
Feb 16 07:04:01 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:01 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:08 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:08 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:11 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:11 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:14 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:14 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:37 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:37 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:40 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:40 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:40 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:40 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:43 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:43 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:46 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:04:46 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:09 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:09 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:12 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:12 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:12 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:12 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:15 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:15 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:18 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:18 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:41 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:41 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:41 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:41 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.246 04:d9:f5:96:aa:88 RT-AC67U-AA88
Feb 16 07:05:48 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.246 04:d9:f5:96:aa:88
Feb 16 07:05:48 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.246 04:d9:f5:96:aa:88 RT-AC67U-AA88
Feb 16 07:05:55 syslog: wlceventd_proc_event(526): eth1: Auth F8:54:B8:C8:7F:4A, status: Successful (0), rssi:0
Feb 16 07:05:55 syslog: wlceventd_proc_event(555): eth1: Assoc F8:54:B8:C8:7F:4A, status: Successful (0), rssi:0
Feb 16 07:05:55 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) f8:54:b8:c8:7f:4a
Feb 16 07:05:55 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.22 f8:54:b8:c8:7f:4a
Feb 16 07:05:55 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.22 f8:54:b8:c8:7f:4a
Feb 16 07:05:55 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.22 f8:54:b8:c8:7f:4a
Feb 16 07:06:43 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.132 ec:8c:9a:82:01:41
Feb 16 07:06:43 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.132 ec:8c:9a:82:01:41 HUAWEI_P10-913e9010ad620d
Feb 16 07:06:43 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.132 ec:8c:9a:82:01:41
Feb 16 07:06:43 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.132 ec:8c:9a:82:01:41 HUAWEI_P10-913e9010ad620d
Feb 16 07:07:45 syslog: wlceventd_proc_event(490): eth1: Deauth_ind 02:59:71:DC:67:B6, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:0
Feb 16 07:07:50 rc_service: httpd 14669:notify_rc restart_httpd
Feb 16 07:07:50 custom_script: Running /jffs/scripts/service-event (args: restart httpd)
Feb 16 07:07:50 RT-AC68U: start httpd:80
Feb 16 07:07:52 httpd: Save SSL certificate...80
Feb 16 07:07:52 httpd: mssl_cert_key_match : PASS
Feb 16 07:07:52 httpd: Succeed to init SSL certificate...80
Feb 16 07:13:21 syslog: wlceventd_proc_event(526): eth1: Auth EC:8C:9A:82:01:41, status: Successful (0), rssi:0
Feb 16 07:13:21 syslog: wlceventd_proc_event(536): eth1: ReAssoc EC:8C:9A:82:01:41, status: Successful (0), rssi:0
Feb 16 07:14:01 syslog: wlceventd_proc_event(490): eth2: Deauth_ind A0:28:ED:0D:C0:AA, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Feb 16 07:15:23 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) a0:28:ed:0d:c0:aa
Feb 16 07:15:23 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.182 a0:28:ed:0d:c0:aa
Feb 16 07:15:23 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.182 a0:28:ed:0d:c0:aa
Feb 16 07:15:23 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.182 a0:28:ed:0d:c0:aa
Feb 16 07:18:52 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.211 04:d9:f5:96:9e:c8
Feb 16 07:18:52 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.211 04:d9:f5:96:9e:c8 RT-AC67U-9EC8
Feb 16 07:26:28 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) 44:65:0d:92:20:ef
Feb 16 07:26:28 dnsmasq-dhcp[16407]: DHCPOFFER(br0) 192.168.1.210 44:65:0d:92:20:ef
Feb 16 07:26:28 dnsmasq-dhcp[16407]: DHCPREQUEST(br0) 192.168.1.210 44:65:0d:92:20:ef
Feb 16 07:26:28 dnsmasq-dhcp[16407]: DHCPACK(br0) 192.168.1.210 44:65:0d:92:20:ef
Feb 16 07:28:02 syslog: wlceventd_proc_event(526): eth2: Auth A0:28:ED:0D:C0:AA, status: Successful (0), rssi:0
Feb 16 07:28:02 syslog: wlceventd_proc_event(536): eth2: ReAssoc A0:28:ED:0D:C0:AA, status: Successful (0), rssi:0
Feb 16 07:29:01 syslog: wlceventd_proc_event(490): eth1: Deauth_ind F8:54:B8:C8:7F:4A, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Feb 16 07:29:29 syslog: wlceventd_proc_event(526): eth2: Auth A0:28:ED:0D:C0:AA, status: Successful (0), rssi:0
Feb 16 07:29:29 syslog: wlceventd_proc_event(536): eth2: ReAssoc A0:28:ED:0D:C0:AA, status: Successful (0), rssi:0
Feb 16 07:29:42 dnsmasq-dhcp[16407]: DHCPDISCOVER(br0) f0:f0:a4:00:76:c1
 

OzarkEdge

Part of the Furniture
I have done a reset of all nodes. Issue occured again this morning.

I have configured a preferred connection point for the nodes. Might this be a possible cause?

When you say "reset all nodes", does this include the main router AC68U?

OE
 

VMARKUS_K

Occasional Visitor
I have now done a downgrade to 384.19 on all nodes (including reset afterward) and will test my setup again with this version.
 

OzarkEdge

Part of the Furniture
I have now done a downgrade to 384.19 on all nodes (including reset afterward) and will test my setup again with this version.

Yeah, could be a firmware issue. The AC67U is not common around here, so maybe it needs more love from Asus.

OE
 

VMARKUS_K

Occasional Visitor
384.19 works fine so far.

My Process:
- Downgrade Nodes to 384.19
- Downgrade Master to 384.19
- Reset of all devices and Reconfig Master
- Format JFFS and reboot Master
- Reconnect all Nodes


My Config Changes from Default:
- PPPoE Setup
- Network Protection Enabled
- DNS, DNSSEC, and DNS-over-TLS Config
- NTP Config
- Enable JFFS Scripts and install Skyline
- Fixed Channel bandwidth (2.4GHz: 20MHz / 5GHz: 80MHz) / Fixed Control Channel (2.4GHz: 11/ 5GHz: 112)
- Roaming assistant enabled
 

lordtech

Occasional Visitor
Hi, I am having the same problem. The AiMesh node seems to drop off a few times per day, which is quite annoying for online meetings.
Both the main router and the node are using the latest firmware 386.1_2. The master router is AC88 and the node is AC68. I did a full reset before updating them to the new firmware.

@VMARKUS_K, are you still running your AiMesh with firmware 384.19?
 

lordtech

Occasional Visitor
I did a rollback too to 384.19 yesterday to both router and node. I am not experimenting with any drop issues so far but I would like to monitor the performance for a couple of days. It is gonna be easy since my kids play online a few hours per day so they are a very reliable quality control team.
 

ech

Regular Contributor
I did a rollback too to 384.19 yesterday to both router and node. I am not experimenting with any drop issues so far but I would like to monitor the performance for a couple of days. It is gonna be easy since my kids play online a few hours per day so they are a very reliable quality control team.
How did this go? I'm also seeing issues with my aimesh node inexplicably disconnecting randomly when running 386.1_2. I've also tried running the latest stock fw on the node but have seen the same problem. Maybe just putting 384.19 on the node would be better.
 

attaxia

New Around Here
I'm also experiencing this issue using RT-AX88U as main and RT-AC88U as (wired) AIMesh node.
RT-AX88U is running 386.1_2 and RT-AC86U is running stock 9.0.0.4.386_41994 as I read on wiki that stock firmware is preferred for the node.

Issues started the day after upgrading to 386, I was on 384 before. I upgraded last Tuesday and have been having the issue daily since. Wired clients get a self-assigned IP and some wifi clients get issues with connectivity.
 

VMARKUS_K

Occasional Visitor
I have started a new trial today:
RT-AC68U Router: 386.2
RT-AC67U Nodes: 3.0.0.4.386_41634-g08f88ae

Upgrade with Factory Reset on all Nodes.

My Config Changes from Default:
- PPPoE Setup
- NAT Settings for VOIP (WAN - NAT Passthrough -> No Helper)
- Network Protection Enabled
- DNS, DNSSEC, and DNS-over-TLS Config
- NTP Server Enabled
- Roaming assistant enabled

Let's see how it works in the next few days.
 

banger

Senior Member
I was having similar problems with stock firmware on 2x RT-AC68U so I have switched to Merlin 386.2 on both router and node. Still monitoring. Personally I think it is the Mesh coding from Asus.
 

Similar threads

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