Beta Asuswrt-Merlin 388.1 Beta is available for select models

[jesteves]

I’m using this 388 beta 1 in the last 24hours… everything working great for now.
Installed dirty over the 386.7.2 on the AX86u.

Aimesh system AX86u (388 beta 1) + AC88u (merlin 386.7.2)
Uplink Type: Wireless 5Ghz (Great Quality)

I have a 1gbs/100mbs internet access with 30 devices in my network,
i use openvpn, and no other addons.

Thanks to RMerlin for this.

 

[snah001]

From RMerlin:
https://www.snbforums.com/threads/dev-asuswrt-merlin-388-1-development.81087/page-16#post-796807

I do not understand this.
Using Wireguard in this beta version you have to set NAT to ON.
When you set it to NO you get no connection.
So please make me understand this.

 

[torstein]

You should do more reading, or use the search tool. This has been discussed at length in previous posts in this thread. NAT acceleration is not compatible with this Wireguard implementation at this point. It may stay that way as well.

I read the entire 9 pages before asking, but couldn't find it. Maybe I skimmed too fast, that's on me. The search tool on snbforums I've tried in many other threads and settings, and I rarely find anything using it - maybe I'm too spoiled by google and don't know how to use "advanced search" properly on a forum, that's also on me.

Having said that, some of the users here on snb really makes one sorry and regret asking anything at all, really. I'll think it over thrice next time I ask, but someone will probably give the same snark nonetheless. Anyway, thank you for answering my question, despite the passive agressiveness.

 

[ghalidrim]

Dug into why my AX68U can't join the AIMesh a bit more and I'm seeing the same log entries for every attempt to join it, but these don't seem catastrophic:

Nov  8 07:56:57 home kernel: device br0 entered promiscuous mode
Nov  8 07:56:58 home lld2d[1241]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Nov  8 07:56:58 home lld2d[1241]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Nov  8 07:56:59 home lld2d[1241]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Nov  8 07:56:59 home lld2d[1241]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Nov  8 07:57:05 home lld2d[1241]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Nov  8 07:57:06 home kernel: device br0 left promiscuous mode
Nov  8 07:57:06 home kernel: device br0 entered promiscuous mode
Nov  8 07:57:07 home lld2d[1241]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Nov  8 07:57:07 home lld2d[1241]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Nov  8 07:57:07 home lld2d[1241]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Nov  8 07:57:08 home lld2d[1241]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Nov  8 07:57:22 home kernel: device br0 left promiscuous mode

I ONLY see that icon file failure while trying to join the AX68U to the mesh, and did NOT see similar entries joining an AX88U. I've done this wired and wireless, from factory reset. It shows the same log entries every time.

 

[skeal]

I do not understand this.
Using Wireguard in this beta version you have to set NAT to ON.
When you set it to NO you get no connection.
So please make me understand this.

NAT stands for Network Address Translation. NAT Acceleration is a speed enhancement applied to NAT. They are separate entities.

NAT as applied here is the ability to have many devices connected through one public IP.

NAT acceleration or Flow Cache helps maintain a high speed LAN network without a more expensive processor.

Disclaimer: Very basic description here. NAT needs to be enabled, to allow your devices behind the router to connect to the internet.

 

[RMerlin]

Dug into why my AX68U can't join the AIMesh a bit more and I'm seeing the same log entries for every attempt to join it, but these don't seem catastrophic:

It`s a bug from upstream GPL. I noticed that some models have a symlink pointing to a non-existing files since GPL 388 for some reason. Just ignore that for now.

 

[ghalidrim]

It`s a bug from upstream GPL. I noticed that some models have a symlink pointing to a non-existing files since GPL 388 for some reason. Just ignore that for now.

Something is keeping AX68's from joining meshes though, there are several folks in here reporting it on only that model. Any idea from the Asus folks on what might be happening there?

 

[RMerlin]

Something is keeping AX68's from joining meshes though, there are several folks in here reporting it on only that model. Any idea from the Asus folks on what might be happening there?

I don`t know. Since AiMesh is completely out of my control, I don't concern myself at all with it. All I can say is that last time I tested it (a few weeks ago), I had no issue pairing two devices over Ethernet.

 

[ghalidrim]

I have two AX88Us, one as router one as node, those joined fine. My AX68U will not join no matter what on 388.1_beta. Downgraded the AX68U to 386.7_2 and it joined immediately and with no issue. So something in the new 388 release is keeping AX68Us from joining, and I'm willing to help figure out what if you have any idea where to look.

 

[RMerlin]

So something in the new 388 release is keeping AX68Us from joining, and I'm willing to help figure out what if you have any idea where to look.

I don't sorry. I have no idea how internally AiMesh works for handling discovery and pairing, so I wouldn't even know what to try.

 

[Mutzli]

I have two AX88Us, one as router one as node, those joined fine. My AX68U will not join no matter what on 388.1_beta. Downgraded the AX68U to 386.7_2 and it joined immediately and with no issue. So something in the new 388 release is keeping AX68Us from joining, and I'm willing to help figure out what if you have any idea where to look.

I would start by using the original 386 firmware from ASUS (Version 3.0.0.4.386.50427) on the AiMesh node to troubleshoot this connection. I had some issues on my AX58U that were solved by using the original firmware.

 

[TheOldMan]

I don`t know. Since AiMesh is completely out of my control, I don't concern myself at all with it. All I can say is that last time I tested it (a few weeks ago), I had no issue pairing two devices over Ethernet.

My AiMesh between two RT-AX68Us is working great with ethernet backhaul. WiFi backhaul you need to have the two routers within a few feet to make it work to connect first. Then you can move the AiMesh to where you want it to be. No issues here.

 

[shabbs]

RT-AX68U with Asuswrt-Merlin 388.1_Beta2 main router
RT-AX68U with Asuswrt-Merlin 388.1_Beta2 aimesh node

Beta 2? Did I miss a special build? Heh heh.

 

[capncybo]

NAT stands for Network Address Translation. NAT Acceleration is a speed enhancement applied to NAT. They are separate entities.

NAT as applied here is the ability to have many devices connected through one public IP.

NAT acceleration or Flow Cache helps maintain a high speed LAN network without a more expensive processor.

Disclaimer: Very basic description here. NAT needs to be enabled, to allow your devices behind the router to connect to the internet.

@snah001
Actually I think what MANY people keep misunderstanding is..
-Not all NAT is being disabled for Wireguard functionality.
What becomes disabled is some of HARDWARE ACCELERATION meaning... (chips/integrated-circuits) built to offload (NAT-work) & free-up the router's CPU
You can't change the firmware & function of these I.C.s, because they were made with a ONE-Time flash & purpose built.
But if you disable some of these specialized components... you slow down your NAT because...
The router has to do it via software & make more use of it's CPU, RAM etc etc.

 

[ZebMcKayhan]

I do not understand this.
Using Wireguard in this beta version you have to set NAT to ON.
When you set it to NO you get no connection.
So please make me understand this.

I wrote this some time ago for Wireguard Manager but its mostly about the how and why. It may contribute to the discussion:
https://github.com/ZebMcKayhan/WireguardManager#disable-flowcache

 

[TheOldMan]

Beta 2? Did I miss a special build? Heh heh.

Not unless you can compile it yourself.

 

[bennor]

I do not understand this.
Using Wireguard in this beta version you have to set NAT to ON.
When you set it to NO you get no connection.
So please make me understand this.

Are you confusing the two elements? NAT (Network Address Translation) and NAT Acceleration.

 

[shabbs]

Not unless you can compile it yourself.

LOL! Ahhh... you should add "-snapshot" then to the build reference.

 

[ASSAD]

Tried the 388.1 beta it's really incredible fast and stable and even i see that jumbo frame added even the LEDS light fixed when disable the wireless, really nice work RMerlin good job, but i see this on system log don't know if that normal or not.

Nov 8 21:22:26 BWDPI: Don't support load-balance mode!
Nov 8 21:22:26 BWDPI: module is blocked, reason=5!
Nov 8 21:22:28 BWDPI: Don't support load-balance mode!
Nov 8 21:22:28 BWDPI: module is blocked, reason=5!
Nov 8 21:22:31 BWDPI: Don't support load-balance mode!
Nov 8 21:22:31 BWDPI: module is blocked, reason=5!
Nov 8 21:22:34 BWDPI: Don't support load-balance mode!
Nov 8 21:22:34 BWDPI: module is blocked, reason=5!
Nov 8 21:22:37 BWDPI: Don't support load-balance mode!
Nov 8 21:22:37 BWDPI: module is blocked, reason=5!

 

[snippem]

Hi @RMerlin thanks for the new build. I have a AX86S, AX56U and a AX68U.
The AX86S is my main accespoint and the AX56U and AX68U are my mesh nodes.
Everything is working as before the 388.1 but the AX68U does not come online after the upgrade.
I can see that an ip-adres is given to AX68U but it's not online in the AI-mesh menu.
When i reset the AX68U and set it up in router mode everythings works as it should.
Flashed the 386.7 firmware again and set the AX68U as an ai-mesh node and it works again.
Then tried the official firmware from the AX68U in mesh node mode and the same problem again.
Are there more people that are using the AX68U as an mesh node that experience the same problem?

Edit: did not read the whole topic and it seems i am not the only one.