[Official Release] AiMesh Firmware v3.0.0.4.384.20308 for All Supported Products

[OzarkEdge]

Even with a wired backhaul, AiMesh sets-up identical 2.4 and 5G IPs to the node (each with its own MAC). Probably for self-healing in case the wired goes down. So you can ignore that warning. I don't think Asus is going to re-engineer AiMesh for them.

Oddly,the wired IP to the node doesn't show in the client list. It also has the same IP. Maybe because its MAC is the same as 2.4Ghz.

Here... a node's wired/LAN and wireless/WLAN network interfaces each have their own MAC address. And a node is leased only one IP address...

With one ~60 foot wireless backhaul to a node with MACs 88:--:--:--:--:A?...

The DHCP Leases tab lists the node's wired/LAN MAC (the one on the labels):
* 88:--:--:--:--:A0 (IP 192.168.1.187 for Hostname *)

The Wireless Log tab lists the node's wireless/WLAN MACs:
2.4 GHz 88:--:--:--:--:A1 (RSSI -45dBm with great Tx/Rx rates)
5.0 GHz 88:--:--:--:--:A4 (RSSI -53dBm with great Tx/Rx rates)

The Network Map lists NO clients having the node's wired/LAN or wireless/WLAN MACs/IP address.

If I directly wire the backhaul, AiMesh Auto senses connection type 'Wired', and then the Network Map lists the node's wireless/WLAN MACs:
2.4 GHz 88:--:--:--:--:A1 (IP 192.168.1.187 for client ASUS)
5.0 GHz 88:--:--:--:--:A4 (IP 192.168.1.187 for client ASUS)

So, AiMesh leases one IP address to Hostname * (the node), and a wired backhaul lists two wireless clients, both using that same IP address.

This is all probably AiMesh normal!

OE

 

[Quad80]

Here... a node's wired/LAN and wireless/WLAN network interfaces each have their own MAC address. And a node is leased only one IP address...

So, AiMesh leases one IP address to Hostname * (the node), and a wired backhaul produces two wireless clients both using that same IP address.

This is all probably AiMesh normal!

OE

Is that what that is!? If that was documented somewhere, I'm gonna feel like a damn fool for missing it, because that would explain why I see my node listed twice on my clients list. I have it hooked up with a wired backhaul and both bands are active. That also explains why it seemingly came out of nowhere for me. It must have corresponded to when I actually hooked up the backend to a wire. I didn't always have it that way when I first set it up, but I didn't even stop to think or notice that it corresponded to when I plugged in the cable. One thing explained.

 

[arthurlien]

2.4 GHz 88:--:--:--:--:A1 (IP 192.168.1.187 for client ASUS)
5.0 GHz 88:--:--:--:--:A4 (IP 192.168.1.187 for client ASUS)
OE

Known Issue, Will Fix.
BTW, this is a display issue.

 

[Flying Dutchman]

I don't think Asus is going to re-engineer AiMesh for them.

You are working for Asus?

 

[Ken Atkinson]

Not sure if this has been mentioned before as part of the wrong info listed on the app or overlooked , but wired connections reporting 100/100 even if they are 1000/1000

 

[arthurlien]

Not sure if this has been mentioned before as part of the wrong info listed on the app or overlooked , but wired connections reporting 100/100 even if they are 1000/1000

Could you post the figure ?

 

[Ken Atkinson]

Arthur , Screenshot laptop of app listing for main laptop and of the adaptor on the laptop showing Gig connection. Anything else you need just let me know.

 

[OzarkEdge]

Not sure if this has been mentioned before as part of the wrong info listed on the app or overlooked , but wired connections reporting 100/100 even if they are 1000/1000

Same here. I assumed that greyed out 'Bandwidth 100/100' was not implemented yet... "a display issue".

OE

 

[Ken Atkinson]

Same here. I assumed that greyed out 'Bandwidth 100/100' was not implemented yet... "a display issue".

OE

Got you , I took it as it wasn't a configurable option/info only hence grey

 

[OzarkEdge]

Got you , I took it as it wasn't a configurable option/info only hence grey

Ha! But... it's greyed and the wrong info... everywhere, hence not working! But I get your point.

OE

 

[Ken Atkinson]

Ha! But... it's greyed and the wrong info... everywhere, hence not working! But I get your point.

OE

"Got you" was meant i totally understand what you assumed , not meant as I've gotcha

 

[OzarkEdge]

"Got you" was meant i totally understand what you assumed , not meant as I've gotcha

Sorry... you made a good point... not configurable... so that threw me off.

OE

 

[TonyRI]

Just upgraded 86U (main) to version 20467. 68R (node) is still on 20308 with wireless backhaul.

Observations:

Node wireless signals for 2.4 a 5GHz no longer appear on client list (yay).
Callbacks suppressed issue that I had reported earlier has resolved.

Now I'm receiving a new syslog message repeatedly:
​

Mar 15 08:27:30 rc_service: watchdog 807:notify_rc stop_aae
Mar 15 08:27:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:27:30 rc_service: watchdog 807:notify_rc start_mastiff
Mar 15 08:27:30 rc_service: waitting "stop_aae" via watchdog ...
Mar 15 08:27:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:27:31 NAT Tunnel: AAE Service is stopped
Mar 15 08:27:31 AAE: AAE Service is started
Mar 15 08:27:31 Mastiff: init
Mar 15 08:27:59 rc_service: httpd 803:notify_rc start_lltdc
Mar 15 08:28:06 Mastiff: Got SIGABRT
Mar 15 08:28:30 rc_service: watchdog 807:notify_rc stop_aae
Mar 15 08:28:30 rc_service: watchdog 807:notify_rc start_mastiff
Mar 15 08:28:30 rc_service: waitting "stop_aae" via watchdog ...
Mar 15 08:28:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:28:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:28:31 NAT Tunnel: AAE Service is stopped
Mar 15 08:28:31 AAE: AAE Service is started
Mar 15 08:28:31 Mastiff: init
Mar 15 08:29:06 Mastiff: Got SIGABRT
Mar 15 08:29:30 rc_service: watchdog 807:notify_rc stop_aae
Mar 15 08:29:30 rc_service: watchdog 807:notify_rc start_mastiff
Mar 15 08:29:30 rc_service: waitting "stop_aae" via watchdog ...
Mar 15 08:29:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:29:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:29:31 NAT Tunnel: AAE Service is stopped
Mar 15 08:29:31 AAE: AAE Service is started
Mar 15 08:29:31 Mastiff: init

Just reporting here until new thread opens for version 20467

 

[arthurlien]

How to get the version 20467. 68R?

我從使用 Tapatalk 的 ASUS_Z012DA 發送

 

[TonyRI]

Just upgraded 86U (main) to version 20467. 68R (node) is still on 20308 with wireless backhaul.

Observations:

Node wireless signals for 2.4 a 5GHz no longer appear on client list (yay).
Callbacks suppressed issue that I had reported earlier has resolved.

Now I'm receiving a new syslog message repeatedly:
​

Mar 15 08:27:30 rc_service: watchdog 807:notify_rc stop_aae
Mar 15 08:27:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:27:30 rc_service: watchdog 807:notify_rc start_mastiff
Mar 15 08:27:30 rc_service: waitting "stop_aae" via watchdog ...
Mar 15 08:27:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:27:31 NAT Tunnel: AAE Service is stopped
Mar 15 08:27:31 AAE: AAE Service is started
Mar 15 08:27:31 Mastiff: init
Mar 15 08:27:59 rc_service: httpd 803:notify_rc start_lltdc
Mar 15 08:28:06 Mastiff: Got SIGABRT
Mar 15 08:28:30 rc_service: watchdog 807:notify_rc stop_aae
Mar 15 08:28:30 rc_service: watchdog 807:notify_rc start_mastiff
Mar 15 08:28:30 rc_service: waitting "stop_aae" via watchdog ...
Mar 15 08:28:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:28:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:28:31 NAT Tunnel: AAE Service is stopped
Mar 15 08:28:31 AAE: AAE Service is started
Mar 15 08:28:31 Mastiff: init
Mar 15 08:29:06 Mastiff: Got SIGABRT
Mar 15 08:29:30 rc_service: watchdog 807:notify_rc stop_aae
Mar 15 08:29:30 rc_service: watchdog 807:notify_rc start_mastiff
Mar 15 08:29:30 rc_service: waitting "stop_aae" via watchdog ...
Mar 15 08:29:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:29:30 NAT Tunnel: AAE Service is stopped
Mar 15 08:29:31 NAT Tunnel: AAE Service is stopped
Mar 15 08:29:31 AAE: AAE Service is started
Mar 15 08:29:31 Mastiff: init

Just reporting here until new thread opens for version 20467

After Reboot of Main:

Mar 15 08:56:54 Mastiff: Got SIGABRT
Mar 15 08:57:19 rc_service: watchdog 807:notify_rc stop_aae
Mar 15 08:57:19 rc_service: watchdog 807:notify_rc start_mastiff
Mar 15 08:57:19 rc_service: waitting "stop_aae" via watchdog ...
Mar 15 08:57:19 NAT Tunnel: AAE Service is stopped
Mar 15 08:57:19 NAT Tunnel: AAE Service is stopped
Mar 15 08:57:20 NAT Tunnel: AAE Service is stopped
Mar 15 08:57:20 AAE: AAE Service is started
Mar 15 08:57:20 Mastiff: init
Mar 15 08:57:54 Mastiff: Got SIGABRT
Mar 15 08:58:19 rc_service: watchdog 807:notify_rc stop_aae
Mar 15 08:58:19 rc_service: watchdog 807:notify_rc start_mastiff
Mar 15 08:58:19 rc_service: waitting "stop_aae" via watchdog ...
Mar 15 08:58:19 NAT Tunnel: AAE Service is stopped
Mar 15 08:58:19 NAT Tunnel: AAE Service is stopped
Mar 15 08:58:20 NAT Tunnel: AAE Service is stopped
Mar 15 08:58:20 AAE: AAE Service is started
Mar 15 08:58:20 Mastiff: init
Mar 15 08:58:55 Mastiff: Got SIGABRT
Mar 15 08:59:19 rc_service: watchdog 807:notify_rc stop_aae
Mar 15 08:59:19 rc_service: watchdog 807:notify_rc start_mastiff
Mar 15 08:59:19 rc_service: waitting "stop_aae" via watchdog ...
Mar 15 08:59:19 NAT Tunnel: AAE Service is stopped
Mar 15 08:59:19 NAT Tunnel: AAE Service is stopped
Mar 15 08:59:20 NAT Tunnel: AAE Service is stopped
Mar 15 08:59:20 AAE: AAE Service is started
Mar 15 08:59:20 Mastiff: init

 

[TonyRI]

How to get the version 20467. 68R?

我從使用 Tapatalk 的 ASUS_Z012DA 發送

68R still on 20308
86U upgraded to 20467 via mobile app "Firmware Update" button

 

[arthurlien]

68R still on 20308
86U upgraded to 20467 via mobile app "Firmware Update" button

Thanks

我從使用 Tapatalk 的 ASUS_Z012DA 發送

 

[TonyRI]

68R still on 20308
86U upgraded to 20467 via mobile app "Firmware Update" button

PS Although there is one Ethernet wired client attached to node port and it appears on the main "View List", it will appear, disappear and then reappear from the Node "More Config" list as a wired client. It works fine, it just doesn't always show as a wired client on the node. This has been the same for all builds of the Mesh firmware. Wireless client attached to node always shows. I also want to just say Thank You for all of the hard work that ASUS has been doing to make AIMesh work as advertised!

 

[TonyRI]

Thanks

我從使用 Tapatalk 的 ASUS_Z012DA 發送

You are welcome. Happy to help and thank you again!

 

[visortgw]

How to get the version 20467. 68R?

我從使用 Tapatalk 的 ASUS_Z012DA 發送

Is there any word as to when 68x will move to 20467 or newer? Thanks.