ASUS RT-AC66U All AiMesh Nodes Stopped Working

[garycnew]

ASUS RT-AC66U All AiMesh Nodes Stopped Working. Link + Data Lights on Router Ethernet Ports Still Function.

WAN (eth0), Wi-Fi (br0), and VPN (tun12) Still Working. LAN Ethernet & Wi-Fi use the same interface br0.

DHCP seems to work with Wi-Fi. DHCP Range 192.168.0.193 - 192.168.0.253. Everything Lower Than 192.168.0.193 is Statically Assigned.

Statically Assigning IP Address to Remote Ethernet Desktop Interface Not Working.

Layer-2 Seems to Work.

Layer-3 Seems to Work for WAN (eth0), Wi-Fi (br0), and VPN (tun12), but Not for LAN Ethernet.

# robocfg showports
Switch: enabled
Port 0: 1000FD enabled stp: none vlan: 2 jumbo: off mac: 00:22:8e:d1:12:00
Port 1: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 00:10:3e:82:c2:93
Port 2: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 00:91:82:33:04:0c
Port 3: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 00:56:27:c8:56:10
Port 4: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 00:10:3e:18:3a:c2
Port 5: 1000FD enabled stp: none vlan: 2 jumbo: off mac: 00:96:93:e0:af:a4
Port 7: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 8: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00

# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
81.75.145.20 35.148.40.1 255.255.255.255 UGH 0 0 0 eth0
10.10.0.69 * 255.255.255.255 UH 0 0 0 tun12
35.148.40.1 * 255.255.255.255 UH 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 br0
35.148.40.0 * 255.255.248.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 35.148.40.1 0.0.0.0 UG 0 0 0 eth0

# arp -a
? (192.168.0.251) at 00:38:80:a9:f1:a9 [ether] on br0
? (192.168.0.31) at <incomplete> on br0
? (192.168.0.61) at <incomplete> on br0
? (192.168.0.217) at 00:d5:bd:f7:dc:9e [ether] on br0
? (192.168.0.121) at <incomplete> on br0
? (192.168.0.141) at <incomplete> on br0
? (35.148.40.1) at 00:22:8e:d1:12:00 [ether] on eth0
? (192.168.0.225) at 00:e2:2f:c3:56:6c [ether] on br0
? (192.168.0.91) at <incomplete> on br0
? (192.168.0.21) at <incomplete> on br0
? (192.168.0.41) at <incomplete> on br0
? (192.168.0.11) at <incomplete> on br0
? (192.168.0.51) at <incomplete> on br0
? (192.168.0.244) at 00:b5:7c:46:8e:57 [ether] on br0
? (192.168.0.81) at <incomplete> on br0
? (192.168.0.71) at <incomplete> on br0
? (192.168.0.223) at 00:96:93:e0:af:a4 [ether] on br0

Of the Successful ARP Responses Only SOME IP Addresses Can Be Pinged & Traced From The Router:

? (192.168.0.251) at 00:38:80:a9:f1:a9 [ether] on br0 (Phone: SUCCESS)
? (192.168.0.217) at 00:d5:bd:f7:dc:9e [ether] on br0 (Desktop: FAILED)
? (35.148.40.1) at 00:22:8e:d1:12:00 [ether] on eth0 (WAN: SUCCESS)
? (192.168.0.225) at 00:e2:2f:c3:56:6c [ether] on br0 (RokuExpress4K: SUCCESS)
? (192.168.0.197) at 00:42:01:6c:62:cc [ether] on br0 (Unknown: SUCCESS)
? (192.168.0.244) at 00:b5:7c:46:8e:57 [ether] on br0 (RokuUltra: SUCCESS)
? (192.168.0.223) at 00:96:93:e0:af:a4 [ether] on br0 (Unknown: FAILED)

[Note: The SUCCESSES are all above the DHCP 192.168.0.193 address minimum and have WLCEVENTD wlceventd_proc_event(529): eth2: Assoc 00:42:01:6C:62:CC, status: Successful (0) entries within the syslog that suggest they are Wi-Fi related devices.]

Desktop on Wi-Fi CAN Ping & Trace Router:

C:\Users\xxx>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\Users\xxx>tracert 192.168.0.1

Tracing route to router [192.168.0.1]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms router [192.168.0.1]

Trace complete.

Any Ideas as to what I may be missing?

Your Assistance is Greatly Appreciated.

 

[garycnew]

UPDATE: It appears that all the LAN Ethernet Ports on the Primary Router Work Fine directly connected to an Apple or Windows Computer. It seems the issue is with the AiMesh Nodes originally connected to those same LAN ETH Ports. It must have something to do with the AiMesh implementation.

No Clients listed in the Client List and No AiMesh Nodes listed in the AiMesh Nodes List.

Any thoughts?

Thanks, again.