Beta Asuswrt-Merlin 386.4 beta is now available

[tsukushitangram]

Can you please support IPv6 plus JPNE connection settings on the WAN configuration page of RT-AX3000?
It says in the release notes that GPL 386_45958 has been merged, but I'm confused because the beta farm doesn't have the v6 plus item added to the wan settings screen.

We'll be back.

 

[saleanddeki]

AX56U, dirty upgrade from beta1 to beta2. After update finished there was, for the first time, mesage to manual reset router. Power off and on and router started bootloop. WPS reset, restored cfg and jffs from beta1 and now everithing is fine

 

[kernol]

RT-AX86U - Full factory reset after beta2 on both main router and AiMesh node [previously running under Asus stock 3.0.0.4.386-45934 and meshed together] - cannot re-establish AiMesh node [also RT-AX86U] connection to main router.

All settings restored from scratch - and despite several resets ... [even one after setting the 2nd RT-AX86U as an AP - then using webui reset to factory defaults - wiping all settings]. Placed stock firmware 3.0.0.4.386-45934 back on the node - reset etc ... but still no ability to re-establish AiMesh connection between main router [still running beta2] and node on stock.

Revert to Asus stock 3.0.0.4.386-45934 on BOTH routers - factory reset - all is well, easily establishes AiMesh connections, IPv6 works straight off - and DDNS using asuscomm.com authenticates as quickly as ever.

I FULLY appreciate that these are all closed source issues over which you personally have no control.
It does suggest however that the closed source bits being made available to you do not come from tried and tested GPL's already issued and in the field by Asus [which I believe was the case in 384 and prior versions].

Appreciate your efforts - and deeply sympathise with the issues that crop up beyond your control.

 

[HeadBanger]

On beta 2, same ddns problem occurs.
And the ddns doesn't update... I have to manually call it

Same here. Beta 2 running for 5-6 hours and it still reports inactive. Switching off ipv6 it instantly works. AX88U.

HB

 

[bbunge]

Now, this is interesting. Just flashed the beta 2 over Asus 386_45934 on the AX86U. Everything seems to be working OK! Will try a factory reset and see what happens.. Of course I have saved the settings...

"Never give in. Never give in. Never, never, never, never--in nothing, great or small, large or petty--never give in, except to convictions of honour and good sense. Never yield to force. Never yield to the apparently overwhelming might of the enemy."
Winston Churchill's address to Harrow School on October 29, 1941

 

[DarkKnight75]

Now, this is interesting. Just flashed the beta 2 over Asus 386_45934 on the AX86U. Everything seems to be working OK! Will try a factory reset and see what happens.. Of course I have saved the settings...

"Never give in. Never give in. Never, never, never, never--in nothing, great or small, large or petty--never give in, except to convictions of honour and good sense. Never yield to force. Never yield to the apparently overwhelming might of the enemy."
Winston Churchill's address to Harrow School on October 29, 1941

How many times have you done this..lol.
I'm just waiting for 386.4 to be released on my hopefully good ax86u.

 

[ColinTaylor]

After a couple of days i dicivered this, same in all Alpha builds. This is Beta1

May 5 07:05:10 dnsmasq-script[1313]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
May 5 07:05:13 dnsmasq-script[1313]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
Dec 20 16:57:03 dnsmasq-script[3270]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
Dec 20 16:58:42 dnsmasq-script[3270]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
Dec 20 19:49:44 dnsmasq-script[3270]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
Dec 20 19:50:04 dnsmasq-script[3270]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory

But it's there:

Just noticed that I see this when the WiFi system restarts (e.g. because of a channel change). It is a daemon.debug message so you also need to have the logging level set to "all" to see it.

 

[JGrana]

wireguard-tools - Required tools for WireGuard, such as wg(8) and wg-quick(8)

git.zx2c4.com

and Jason provides bash scripts for different environments to be used to configure the WireGuard interfaces:

e.g. FreeBSD, Linux etc.

wg-quick « src - wireguard-tools - Required tools for WireGuard, such as wg(8) and wg-quick(8)

git.zx2c4.com

Entware:
wg-quick - 1.0.20210914-1 - This is an extremely simple script for easily bringing up a WireGuard interface, suitable for a few common use cases.

Thanks @Martineau , it is a bash script. I have a very simple use case (site to site, each sites does it own internet, own DNS (Unbound thanks to you)).
Do note that it does install a more full version of Bash. Hopefully doesn’t break any scripts using the Busybox version.

 

[kernol]

Now, this is interesting. Just flashed the beta 2 over Asus 386_45934 on the AX86U. Everything seems to be working OK! Will try a factory reset and see what happens.. Of course I have saved the settings...

"Never give in. Never give in. Never, never, never, never--in nothing, great or small, large or petty--never give in, except to convictions of honour and good sense. Never yield to force. Never yield to the apparently overwhelming might of the enemy."
Winston Churchill's address to Harrow School on October 29, 1941

Take care to export and save your DDNS certificate if you are using one from lets Encrypt.
I stupidly forgot to do so - and after all the resets and rebuilds I have done to test out the beta as much as I could - I hit the wall on their rates limits ...
https://letsencrypt.org/docs/rate-limits/

Have reverted to stock and will have to wait until next week to get certificate issued - but 386_45934 stock works on IPv6 and DDNS for the RT-AX86U.

 

[SheikhSheikha]

Upgrade from Beta1 to Beta2 and the show goes on! :-D

 

[Martineau]

Thanks @Martineau , it is a bash script.

Hence the reason I wrote wireguard_manager which is a simple SH script - usually compatible with ASUS routers without BASH

 

[bbunge]

Now, this is interesting. Just flashed the beta 2 over Asus 386_45934 on the AX86U. Everything seems to be working OK! Will try a factory reset and see what happens.. Of course I have saved the settings...

"Never give in. Never give in. Never, never, never, never--in nothing, great or small, large or petty--never give in, except to convictions of honour and good sense. Never yield to force. Never yield to the apparently overwhelming might of the enemy."
Winston Churchill's address to Harrow School on October 29, 1941

Well, this is embarrassing...

First, to answer DarkKnight75 - at least a half dozen tries.

Beta 2 on my AX86U is working and it probably was working the first time I upgraded. I was using my desktop which is connected to the LAN port 1 to flash and configure. The last time I flashed beta 2 and factory reset with new config I still did not have connection to the Internet from the desktop. I tried speed test on the router and it worked. So I fired up the Mac Mini which is wireless and, voila, it connected to Internet sites! What the h***? Switched the Ethernet cable over to LAN port 4 and guess what? CONNECTION! Yea!!! I dug up another CAT5e cable and connected the desktop back to LAN port 1 and all is good. I have a NAS and a PoE switch on two other ports and they were not bothered.
Guess I can blame this on gremelins or maybe mischievous Christmas elves.

Happy Holidays to all wherever you hang your hat.
Please be safe. “It's a dangerous business, Frodo, going out your door. You step onto the road, and if you don't keep your feet, there's no knowing where you might be swept off to.”

 

[Jeffrey Young]

Well, this is embarrassing...

First, to answer DarkKnight75 - at least a half dozen tries.

Beta 2 on my AX86U is working and it probably was working the first time I upgraded. I was using my desktop which is connected to the LAN port 1 to flash and configure. The last time I flashed beta 2 and factory reset with new config I still did not have connection to the Internet from the desktop. I tried speed test on the router and it worked. So I fired up the Mac Mini which is wireless and, voila, it connected to Internet sites! What the h***? Switched the Ethernet cable over to LAN port 4 and guess what? CONNECTION! Yea!!! I dug up another CAT5e cable and connected the desktop back to LAN port 1 and all is good. I have a NAS and a PoE switch on two other ports and they were not bothered.
Guess I can blame this on gremelins or maybe mischievous Christmas elves.

Happy Holidays to all wherever you hang your hat.
Please be safe. “It's a dangerous business, Frodo, going out your door. You step onto the road, and if you don't keep your feet, there's no knowing where you might be swept off to.”

We have all been there at one time or another!!

 

[Clark Griswald]

Dirty Update from beta1 (& I forgot to eject usb first), and no issues reported from Family.
EDIT: ipv6 still working as with beta1 and no network issues
Thank you RMerlin

Happy and SAFE Holidays

 

[SomeWhereOverTheRainBow]

RT-AX86U - Full factory reset after beta2 on both main router and AiMesh node [previously running under Asus stock 3.0.0.4.386-45934 and meshed together] - cannot re-establish AiMesh node [also RT-AX86U] connection to main router.

All settings restored from scratch - and despite several resets ... [even one after setting the 2nd RT-AX86U as an AP - then using webui reset to factory defaults - wiping all settings]. Placed stock firmware 3.0.0.4.386-45934 back on the node - reset etc ... but still no ability to re-establish AiMesh connection between main router [still running beta2] and node on stock.

Revert to Asus stock 3.0.0.4.386-45934 on BOTH routers - factory reset - all is well, easily establishes AiMesh connections, IPv6 works straight off - and DDNS using asuscomm.com authenticates as quickly as ever.

I FULLY appreciate that these are all closed source issues over which you personally have no control.
It does suggest however that the closed source bits being made available to you do not come from tried and tested GPL's already issued and in the field by Asus [which I believe was the case in 384 and prior versions].

Appreciate your efforts - and deeply sympathise with the issues that crop up beyond your control.

Yea I haven't had any issues yet with ipv6 and RMerlin beta 2. Everything seems to be working completely as well. I believe the "second ipv6" webui page you are referring to im a previous post is for dual wan setups, are you running an ipv6 dual wan?

 

[RMerlin]

@RMerlin - RT-AX86U - beta2 - same problem as @bbunge and @maghuro - and I believe the cause is failure of that router model to establish WAN IPv6 connection with your beta2. Your Merlinware GUI contains 2 pages for IPv6 setup but neither work.

You're using an addon that modifies your UI to generate that cascaded menu. Try again without that addon.

I know you can't test IPv6 - but maybe Asus can provide you the IPv6 framework from the above stock code - instead of from their untested 45958 which they have supplied to you?

IPv6 support is not a "framework" you can transplant between versions. It's integral to the firmware code as a whole. Beside, the issue is with the new IPv6 DDNS support, not IPv6 connectivity.

As for the DDNS patches they provided for beta 2, these came from their latest codebase and contain various fixes, including implementing support for the watchdog to do retries if the ddns failed an update. Watchdog will also ensure not to spam the remote server by giving up after a few minutes.

At this point, the current plan is to simply disable IPv6 support in DDNS.

and Jason provides bash scripts for different environments to be used to configure the WireGuard interfaces:

That's a bash script, which means it's highly likely not to work properly with the router's dash. Asus does not include it in the firmware, so it must be totally optional.

 

[RMerlin]

Can you please support IPv6 plus JPNE connection settings on the WAN configuration page of RT-AX3000?

I'm keeping that feature disabled at this time because I'm missing the proprietary portions of it for various models, and for some models with the necessary components it fails to compile properly. This will probably have to wait until Asus does a more widespread rollout accross mutliple models.

 

[Jack Yaz]

You're using an addon that modifies your UI to generate that cascaded menu. Try again without that addon.

FWIW all the code is doing is reading Asus' own tab/page array and generating some shortcuts, so the pages are all there, albeit some are part of an in-tab switch, like the Traffic Monitoring area.

 

[kernol]

You're using an addon that modifies your UI to generate that cascaded menu. Try again without that addon.

It fails right after a full factory reset after your beta2 is loaded - with minimum config and BEFORE any addon scripts are deployed.
@Jack Yaz - I assumed your scMerlin script simply listed the pages dropped into the system by the firmware and did not modify any of them. If ii does actually modify any pages or cause the original pages not to function correctly - perhaps you need to investigate?

IPv6 support is not a "framework" you can transplant between versions. It's integral to the firmware code as a whole.

My sincere apologies for my ignorance in terminology - I am not a coder ... but I am trying to be helpful by testing your beta.

At this point, the current plan is to simply disable IPv6 support in DDNS.

That work-around will no doubt do the trick - just a pity that the GPL supplied to you does not work as well in this particular respect as the latest stock firmware released for this router model - 3.0.0.4.386-45934.

Many thanks for your continued efforts - and for taking the time to respond {thumbs-Up}.

 

[Jack Yaz]

It fails right after a full factory reset after your beta2 is loaded - with minimum config and BEFORE any addon scripts are deployed.
@Jack Yaz - I assumed your scMerlin script simply listed the pages dropped into the system by the firmware and did not modify any of them. If ii does actually modify any pages or cause the original pages not to function correctly - perhaps you need to investigate?

It does not modify the pages. It adds some styles to the css used by all pages and javascript functions, but doesn't touch the pages themselves. If it did, a whole heap of stuff would have broken in the WebUI in the alpha and beta ;-)