Beta Asuswrt-Merlin 386.1 Beta is now available

[Stoonhea020]

I have the same problem that two others reported as well. Since the upgrade from alpha4 to beta1 I am no longer able to retrieve a LE free certificate. It hangs in an Authorization status, even after a couple of reboots.
I also factory reset my router (RT-AX86U) several times via the UI and formatted jffs partition but no success. As test I disabled the Firewall and enabled WAN access but the status remain the same.

Dec 6 11:35:03 Mastiff: Got AAE_SIG_REMOTE_CONNECTION_TURNED_ON
Dec 6 11:35:03 rc_service: httpd 5672:notify_rc restart_ddns_le
Dec 6 11:35:03 start_ddns: update WWW.ASUS.COM update@asus.com, wan_unit 0
Dec 6 11:35:03 inadyn[11420]: In-a-dyn version 2.7 -- Dynamic DNS update client.
Dec 6 11:35:03 inadyn[11420]: Update forced for alias ***********.asuscomm.com, new IP# XXX.XXX.XXX.XXX
Dec 6 11:35:04 inadyn[11420]: Updating cache for ***********.asuscomm.com
Dec 6 11:35:10 kernel: [Sun Dec 6 11:35:10 MEZ 2020]
Dec 6 11:35:10 kernel: Registering account
Dec 6 11:35:12 kernel: [Sun Dec 6 11:35:12 MEZ 2020]
Dec 6 11:35:12 kernel: Already registered
Dec 6 11:35:12 kernel: [Sun Dec 6 11:35:12 MEZ 2020]
Dec 6 11:35:12 kernel: ACCOUNT_THUMBPRINT='***************************************'
Dec 6 11:35:12 kernel: [Sun Dec 6 11:35:12 MEZ 2020]
Dec 6 11:35:12 kernel: Creating domain key
Dec 6 11:35:16 kernel: [Sun Dec 6 11:35:16 MEZ 2020]
Dec 6 11:35:16 kernel: The domain key is here: /jffs/.le/***********.asuscomm.com/***********.asuscomm.com.key
Dec 6 11:35:16 kernel: [Sun Dec 6 11:35:16 MEZ 2020]
Dec 6 11:35:16 kernel: Single domain='***********.asuscomm.com'
Dec 6 11:35:16 kernel: [Sun Dec 6 11:35:16 MEZ 2020]
Dec 6 11:35:16 kernel: Getting domain auth token for each domain
Dec 6 11:35:19 kernel: [Sun Dec 6 11:35:19 MEZ 2020]
Dec 6 11:35:19 kernel: Getting webroot for domain='***********.asuscomm.com'
Dec 6 11:35:19 kernel: [Sun Dec 6 11:35:19 MEZ 2020]
Dec 6 11:35:19 kernel: ***********.asuscomm.com is already verified, skip dns-01.
Dec 6 11:35:19 kernel: [Sun Dec 6 11:35:19 MEZ 2020]
Dec 6 11:35:19 kernel: Verify finished, start to sign.
Dec 6 11:35:19 kernel: [Sun Dec 6 11:35:19 MEZ 2020]
Dec 6 11:35:19 kernel: Lets finalize the order, Le_OrderFinalize: https://acme-v02.api.letsencrypt.org/acme/finalize/**************/*****************
Dec 6 11:35:20 kernel: [Sun Dec 6 11:35:20 MEZ 2020]
Dec 6 11:35:20 kernel: Download cert, Le_LinkCert: https://acme-v02.api.letsencrypt.org/acme/cert/*****************************************
Dec 6 11:35:22 kernel: [Sun Dec 6 11:35:22 MEZ 2020]
Dec 6 11:35:22 kernel: Cert success.
Dec 6 11:35:22 kernel: cat: write error: Invalid argument
Dec 6 11:35:22 kernel: [Sun Dec 6 11:35:22 MEZ 2020]
Dec 6 11:35:22 kernel: Your cert is in /jffs/.le/***********.asuscomm.com/***********.asuscomm.com.cer
Dec 6 11:35:22 kernel: [Sun Dec 6 11:35:22 MEZ 2020]
Dec 6 11:35:22 kernel: Your cert key is in /jffs/.le/***********.asuscomm.com/***********.asuscomm.com.key
Dec 6 11:35:22 kernel: [Sun Dec 6 11:35:22 MEZ 2020]
Dec 6 11:35:22 kernel: The intermediate CA cert is in /jffs/.le/***********.asuscomm.com/ca.cer
Dec 6 11:35:22 kernel: [Sun Dec 6 11:35:22 MEZ 2020]
Dec 6 11:35:22 kernel: And the full chain certs is there: /jffs/.le/***********.asuscomm.com/fullchain.cer
Dec 6 11:35:22 kernel: [Sun Dec 6 11:35:22 MEZ 2020]
Dec 6 11:35:22 kernel: Installing key to:/jffs/.le/***********.asuscomm.com/domain.key
Dec 6 11:35:22 kernel: [Sun Dec 6 11:35:22 MEZ 2020]
Dec 6 11:35:22 kernel: Installing full chain to:/jffs/.le/***********.asuscomm.com/fullchain.pem
Dec 6 11:36:00 rc_service: service 14384:notify_rc restart_letsencrypt
Dec 6 11:36:01 kernel: [Sun Dec 6 11:36:01 MEZ 2020]
Dec 6 11:36:01 kernel: Domains not changed.
Dec 6 11:36:01 kernel: [Sun Dec 6 11:36:01 MEZ 2020]
Dec 6 11:36:01 kernel: Skip, Next renewal time is: Thu Feb 4 10:35:22 UTC 2021
Dec 6 11:36:01 kernel: [Sun Dec 6 11:36:01 MEZ 2020]
Dec 6 11:36:01 kernel: Add '--force' to force to renew.

 

[octopus]

RT-AC1900P....Any changes to VPN client setting results in dropped WAN. This was the case with Alpha 2 & 4 as well. I can restore WAN connection by going to the WAN settings and simply hitting the "Apply" button.

I am running two VPN clients.

I have same issue tried with two clients and noone get internet over vpn. I have to reset and test again and se if i can read log for errors.

 

[WillyTP]

Hello again everybody.
Regarding my post of some pages before:

I've been able to fix the In-a-dyn updating every minute: this was my error.
By mistake, I inserted my FreeDNS.araid login with some uppercase letters (example: "LogIn" rather than "login").
After my experience, I think it would be useful a "lowercase" check for this specific free DNS provider

However, Let's Encrypt certificate issue persists. Since I wasn't aware of other users's posts until this morning, I tried too to downgrade firmware *without* success.
Now I'm again on 386.1 Beta 1.

I tried a bit of everything but nothing works (reboot, reset, JFFS reset, removal of .le folder discussed in other topics).
The following are the errors plus some my notes

Certificate creation seems to be OK. data is getting correctly stored with the .le folder

Dec  6 01:32:17 Mastiff: Got AAE_SIG_REMOTE_CONNECTION_TURNED_ON
Dec  6 01:32:17 rc_service: httpds 281:notify_rc restart_ddns_le
Dec  6 01:32:17 start_ddns: update FREEDNS.AFRAID.ORG default@freedns.afraid.org, wan_unit 0
Dec  6 01:32:17 inadyn[937]: In-a-dyn version 2.7 -- Dynamic DNS update client.
Dec  6 01:32:19 inadyn[937]: Update forced for alias my.mysite.com, new IP# 93.46.116.20
Dec  6 01:32:21 inadyn[937]: Updating cache for my.mysite.com
Dec  6 01:32:30 kernel: [Sun Dec  6 01:32:30 MEZ 2020] Standalone mode.
Dec  6 01:32:33 kernel: [Sun Dec  6 01:32:33 MEZ 2020] Create account key ok.
Dec  6 01:32:33 kernel: [Sun Dec  6 01:32:33 MEZ 2020] Registering account
Dec  6 01:32:36 kernel: [Sun Dec  6 01:32:36 MEZ 2020] Registered
Dec  6 01:32:37 kernel: [Sun Dec  6 01:32:37 MEZ 2020] ACCOUNT_THUMBPRINT='FRxgJr9LDjkRIV4TI1uREx9iQLRmaxwwGx6ht2IyY0I'
Dec  6 01:32:37 kernel: [Sun Dec  6 01:32:37 MEZ 2020] Creating domain key
Dec  6 01:32:38 kernel: [Sun Dec  6 01:32:38 MEZ 2020] The domain key is here: /jffs/.le/my.mysite.com/my.mysite.com.key
Dec  6 01:32:38 kernel: [Sun Dec  6 01:32:38 MEZ 2020] Single domain='my.mysite.com'
Dec  6 01:32:39 kernel: [Sun Dec  6 01:32:39 MEZ 2020] Getting domain auth token for each domain
Dec  6 01:32:43 kernel: [Sun Dec  6 01:32:43 MEZ 2020] Getting webroot for domain='my.mysite.com'
Dec  6 01:32:44 kernel: [Sun Dec  6 01:32:43 MEZ 2020] Verifying: my.mysite.com
Dec  6 01:32:44 kernel: [Sun Dec  6 01:32:44 MEZ 2020] Standalone mode server
Dec  6 01:32:50 kernel: [Sun Dec  6 01:32:50 MEZ 2020] Success
Dec  6 01:32:51 kernel: [Sun Dec  6 01:32:51 MEZ 2020] Verify finished, start to sign.
Dec  6 01:32:51 kernel: [Sun Dec  6 01:32:51 MEZ 2020] Lets finalize the order, Le_OrderFinalize: https://acme-v02.api.letsencrypt.org/acme/finalize/105261011/6586480041
Dec  6 01:32:53 kernel: [Sun Dec  6 01:32:53 MEZ 2020] Download cert, Le_LinkCert: https://acme-v02.api.letsencrypt.org/acme/cert/037a7141e1249ac0a342aebcb2154d234a9a
Dec  6 01:32:55 kernel: [Sun Dec  6 01:32:55 MEZ 2020] Cert success.
Dec  6 01:32:55 kernel: -----BEGIN CERTIFICATE-----
[certificate removed by me...]
Dec  6 01:32:55 kernel: -----END CERTIFICATE-----
Dec  6 01:32:55 kernel: [Sun Dec  6 01:32:55 MEZ 2020] Your cert is in  /jffs/.le/my.mysite.com/my.mysite.com.cer
Dec  6 01:32:55 kernel: [Sun Dec  6 01:32:55 MEZ 2020] Your cert key is in  /jffs/.le/my.mysite.com/my.mysite.com.key
Dec  6 01:32:56 kernel: [Sun Dec  6 01:32:55 MEZ 2020] The intermediate CA cert is in  /jffs/.le/my.mysite.com/ca.cer
Dec  6 01:32:56 kernel: [Sun Dec  6 01:32:56 MEZ 2020] And the full chain certs is there:  /jffs/.le/my.mysite.com/fullchain.cer
Dec  6 01:32:57 kernel: [Sun Dec  6 01:32:57 MEZ 2020] Installing key to:/jffs/.le/my.mysite.com/domain.key
Dec  6 01:32:57 kernel: [Sun Dec  6 01:32:57 MEZ 2020] Installing full chain to:/jffs/.le/my.mysite.com/fullchain.pem

However, certificate installation actually doesn't work (the browser I use doesn't recognize it), Asus GUI always signal "Waiting for authorization", and the log shows

Dec  6 01:49:33 kernel: [Sun Dec  6 01:49:33 MEZ 2020] Domains not changed.
Dec  6 01:49:33 kernel: [Sun Dec  6 01:49:33 MEZ 2020] Skip, Next renewal time is: Thu Feb  4 00:32:56 UTC 2021
Dec  6 01:49:33 kernel: [Sun Dec  6 01:49:33 MEZ 2020] Add '--force' to force to renew.

Certificate Information which I get from Firefox is patently wrong.

 

[Morpheus2020]

AX86U, Asuswrt-Merlin 386.1 Beta. Reset completely.

1.QOS off or Adaptive QOS ON:
Bandwidth monitor doesn't work. The bandwidth value is very low, which is obviously wrong.
It works only in 384.9298 of AX86U.

2. Many entries like "kernel: invalid dirty_p detected: ffffffc000000000 valid=[ffffffc03ccbbb40 ffffffc03ccbbc80]" appear in the syslog, when there are data transmission and reception in 5G WiFi, if I switch Adaptive QOS ON or just stay at the bandwidth monitor interface. The upload speed of 5G WiFi is very low, if I switch Adaptive QOS or Aiprotection ON.
This issue has been resolved in 9.0.0.4_386_41034-ge2d15cc(https://www.snbforums.com/threads/ax86u-slow-upload-speed-with-aiprotection-on.67149/).
9.0.0.4.386.41157(https://www.snbforums.com/threads/asuswrt-386-rc2-public-beta-with-full-functions-aimesh-2-0.65235/) also resolved this issue.

I think if you merge 386.41157 or newer, Issue 2 could be resolved. And I really want to know why ASUS Official has not resolved Issue 1 for more than half a year.....

3.Traditional QOS ON:

NO Data.

 

[JoGi]

Hello

I have a RT-5300AC and RT-AC68U (node)
I have updated from 384-19 to 386 beta 1.
Lost AI-MESH.
Tried factory reset and still impossible to connect the two routeurs.

Best regards

I had the same issue, wireless cant connect to nodes first time, after (temporily)wired pairing, its working again

 

[coaltrans]

I had the same issue, wireless cant connect to nodes first time, after (temporily)wired pairing, its working again

Many thanks for your feedback.
I have tried already but without any success. When i search for node it never appears

EDIT / Solved the issue by downgrading RT 5300 to 384-19 now it works

 

[skeal]

Issues with my update to the new Beta 1 on my AX88U

1. I had a lot of trouble with my reset to defaults and configuring from scratch. Took several resets to clear the router of all settings. I kept finding some settings I didn't enter yet still in use.

2. On my AX88U, the firmware revealed that I had a too long of a password for wifi on one of my networks. One character to long. Worked on Alpha 4. I would get it set up and the password length would cause a reformat of the general wireless page. It really messed stuff up. I got it now it seems to be fine.

3. The client page doesn't show all the devices I have connected though. Seems some of my access points clients are not being shown on this page. Not only that but when I click the client page link button I swear my router reboots or something similar. It stops video from playing. I go to my AP An AC68U(384.19) and look at the clients page and they are all there on it's client list.

4. DDNS fails to authenticate, even tried a new asuscomm ddns name and it won't authenticate. Otherwise things are okay finally. No I'm not using AImesh.

This firmware looks like it was a major undertaking, thanks and great work @RMerlin

 

[LimJK]

However, Let's Encrypt certificate issue persists.

I have the same problem that two others reported as well. Since the upgrade from alpha4 to beta1 I am no longer able to retrieve a LE free certificate. It hangs in an Authorization status, even after a couple of reboots.
I also factory reset my router (RT-AX86U) several times via the UI and formatted jffs partition but no success. As test I disabled the Firewall and enabled WAN access but the status remain the same.

I have the same issue with Let's Encrypt Certificate:

PS: I do not have this issue with earlier Merlin 386.1_Alphas and Stock RC-B9 9.0.0.4_386_41157-gd618756

 

[isr25]

Further to my earlier LE error report, I’m now setting HTTPS/SSL cert setting to none, and removing /jffs/.le folder. Will try to set it up tomorrow and see if it makes any difference

 

[LimJK]

My Configuration:

• AiMesh Router: AX88U 386.1_beta1 + 2 x AiMesh Nodes: AC86U 386.1_beta1
• Backhaul (Priority:"Auto", Type:"Wired"), Cisco SG100D 8-Port Gigabit Switch from Router to Nodes, ISP: 1 Gbps Fibre

My steps to Upgrade from Stock RC2-B9 9.0.0.4_386_41157 -> Merlin 386.1_beta1:

(1) Upgrade AiMesh Nodes:

• Administration -> Upgrade Firmware -> Select and Upgrade AiMesh Node (One Node at a time)
• AiMesh -> Topology -> Select AiMesh Node -> Remove Node (One Node at a time to Factory Reset Node)

(2) Upgrade AiMesh Router:

• Administration -> Upgrade Firmware -> Select and Upgrade AiMesh Router
• Factory Reset with physical WPS button
• Configure AiMesh Router from scratch
• Enable & Formatted JFFS Partition
• Physically Reboot AiMesh Router
• (I recalled doing 3 such factory resets to get AiMesh Router up and running)

(3) After Full Factory Reset of AiMesh Router / Nodes, I tried to leave NVRAM using Merlin FW default values, except with the following changes:

• Enabled AiProtection: ON
  • Malicious Sites Blocking: ON
  • Two-Way IPS: ON
  • Infected Device Prevention and Blocking: ON
• USB Application
  • UPnP Media Server: OFF
  • Samba Share: Off
• Wireless:
  • 2.4 GHz: Fixed Channel Bandwidth 20MHz, Fixed Control Channel: 11, Explicit / Universal Beamforming: Disable
  • 5.0 GHz: Fixed Channel Bandwidth 80MHz, Fixed Control Channel: 149
• WAN DDNS:
  • Using Asus DDNS Service with Let’s Encrypt
• VPN Servers:
  • OpenVPN works with MacBookPro Tunnelblick 3.8.5beta0, iPhoneXsMax iOS OpenVPN Connect 3.2.2
  • IPSec works with MacBookPro & iPhoneXsMax Native Configurations
  • Instant Guard works with iPhoneXsMax iOS Instant Guard 1.0.9

(5) Add AiMesh Nodes

(6) Reboot AiMesh Network

• AiMesh -> System Settings -> Reboot (AiMesh Router & Nodes)

I would like to report that, I have been running smoothly with 386.1_beta1 for my configuration including AiMesh 2.0 DEFAULT settings for over 4 hours:

• Solid Ethernet Backhaul
• Excellent Wifi (AiMesh Roaming/Steering)
• Good Performance (Upload/Download: Wifi (ac) about 400mbps, Wired about 930mbps)

Hoping that it can be a useful comparison for others with similar configuration.

 

[1p3op]

with this version this problem returned. can you send me back the string to use in ssh? I can't find it anymore

ec 4 15:35:18 kernel: nf_conntrack: expectation table full
Dec 4 15:35:18 kernel: nf_conntrack: expectation table full
Dec 4 15:35:18 kernel: nf_conntrack: expectation table full
Dec 4 15:35:18 kernel: nf_conntrack: expectation table full
Dec 4 15:35:18 kernel: nf_conntrack: expectation table full
Dec 4 15:35:18 kernel: nf_conntrack: expectation table full
Dec 4 15:35:18 kernel: nf_conntrack: expectation table full
Dec 4 15:35:18 kernel: nf_conntrack: expectation table full
Dec 4 15:35:18 kernel: nf_conntrack: expectation table full

 

[Deleted member 22229]

if I logon to the GUI and move around in the menu system, the router eventually takes a spontaneous restart.

Never had that issue here

In the category of whoops I did it again! I'd appreciate it if others with the RT-AX58U could do a quick negative test to see if you can duplicate the GUI crashes that I am seeing on 386 Beta 1.

Test case:
- login to the GUI (I am using latest Chrome but browser likely makes no difference)
- starting with Network Map work your way down the menu system and select each menu option, each time you select a left hand menu option, within each menu select each of the sub menus (just click on them don't change anything)
- work your way up and down the menu list
- after about 2-4 minutes your router will crash

Yes, I crashed the router a 3rd and 4th time. Whoops, I did it again! @RMerlin I believe you also have the RT-AX58U, would be interesting if you also can replicate this fault.

View attachment 28252

Tried this this morning and can confirm clicking through the UI caused my AX58U to crash and reboot. Something very strange there.

 

[Sicario]

No. The problem is these alpha builds have some invalid nvram values.

Do we need to factory default reset when 386.1 final will be released?

edit: I mean, coming from this beta to the final release later.

 

[Slawek P]

My Configuration:

• AiMesh Router: AX88U 386.1_beta1 + 2 x AiMesh Nodes: AC86U 386.1_beta1
• Backhaul (Priority:"Auto", Type:"Wired"), Cisco SG100D 8-Port Gigabit Switch from Router to Nodes, ISP: 1 Gbps Fibre

My steps to Upgrade from Stock RC2-B9 9.0.0.4_386_41157 -> Merlin 386.1_beta1:

(1) Upgrade AiMesh Nodes:

• Administration -> Upgrade Firmware -> Select and Upgrade AiMesh Node (One Node at a time)
• AiMesh -> Topology -> Select AiMesh Node -> Remove Node (One Node at a time to Factory Reset Node)

(2) Upgrade AiMesh Router:

• Administration -> Upgrade Firmware -> Select and Upgrade AiMesh Router
• Factory Reset with physical WPS button
• Configure AiMesh Router from scratch
• Enable & Formatted JFFS Partition
• Physically Reboot AiMesh Router
• (I recalled doing 3 such factory resets to get AiMesh Router up and running)

(3) After Full Factory Reset of AiMesh Router / Nodes, I tried to leave NVRAM using Merlin FW default values, except with the following changes:

• Enabled AiProtection: ON
  • Malicious Sites Blocking: ON
  • Two-Way IPS: ON
  • Infected Device Prevention and Blocking: ON
• USB Application
  • UPnP Media Server: OFF
  • Samba Share: Off
• Wireless:
  • 2.4 GHz: Fixed Channel Bandwidth 20MHz, Fixed Control Channel: 11, Explicit / Universal Beamforming: Disable
  • 5.0 GHz: Fixed Channel Bandwidth 80MHz, Fixed Control Channel: 149
• WAN DDNS:
  • Using Asus DDNS Service with Let’s Encrypt
• VPN Servers:
  • OpenVPN works with MacBookPro Tunnelblick 3.8.5beta0, iPhoneXsMax iOS OpenVPN Connect 3.2.2
  • IPSec works with MacBookPro & iPhoneXsMax Native Configurations
  • Instant Guard works with iPhoneXsMax iOS Instant Guard 1.0.9

(5) Add AiMesh Nodes

(6) Reboot AiMesh Network

• AiMesh -> System Settings -> Reboot (AiMesh Router & Nodes)

I would like to report that, I have been running smoothly with RC2-B8 9.0.0.4_386_41157 for my configuration including AiMesh 2.0 DEFAULT settings for over 4 hours:

• Solid Ethernet Backhaul
• Excellent Wifi (AiMesh Roaming/Steering)
• Good Performance (Upload/Download: Wifi (ac) about 400mbps, Wired about 930mbps)

Hoping that it can be a useful comparison for others with similar configuration.

I wonder if TrendMicro still slows down 1Gbps ookla tests on AX88U on beta release or that is something ASUS has addressed now.

 

[shabbs]

And a new look website to boot! Like Christmas! HA! @RMerlin

 

[Sonyrolfy]

I have same issue tried with two clients and noone get internet over vpn. I have to reset and test again and se if i can read log for errors.

Same problem here after a fresh install with Beta 1.
Maybe this is a problem?
All 192.168.1.0/24 VPN
Device 192.168.1.50 WAN

Small log attached.

 

[LimJK]

I wonder if TrendMicro still slows down 1Gbps ookla tests on AX88U on beta release or that is something ASUS has addressed now.

Slawek,
With AiProtection Enabled, this is what I get on AX88U built-in Speedtest

This is what I get on my MacBookPro (Wired) to one of my AiMesh Node

 

[Slawek P]

Do we need to factory default reset when 386.1 final will be released?

edit: I mean, coming from this beta to the final release later.

Probably unknown at this stage as Asus may provide another revision of their binaries

 

[hifiwifi]

Check your route and VPN configurations and look for error messages in the system log.



What does your system log says? There should be crashlog entries in it if it really crashes.

I should point out that I am using an ATT modem in "not quite bridge mode," which passes the modem IP to the router. I deleted the PIA config file (which I generated new using the new PIA web tool) and it still happens using my other, main VPN config. I blanked both configs, rebooted, and reconfigured clients. Still happens with either both or singly installed clients and won't recover unless I hit the "apply" button on the WAN page, or reboot. Both VPN clients connect normally and work fine, except when any changes are made or they are stopped/restarted. I never experienced this with 384.19.

Here is something that occurs in the log after making a change or stopping/starting a VPN client.

Dec  6 06:59:21 openvpn-routing: Configuring policy rules for client 1
Dec  6 06:59:21 ovpn-client1[8289]: Initialization Sequence Completed
Dec  6 06:59:39 WAN_Connection: ISP's DHCP did not function properly.

 

[Slawek P]

Slawek,
With AiProtection Enabled, this is what I get on AX88U built-in Speedtest
View attachment 28266
This is what I get on my MacBookPro (Wired) to one of my AiMesh Node
View attachment 28267

Interesting - thanks for that. This is encouraging me to do beta upgrade, I just hate reconfig from factory settings, so was hoping to wait out for final version. So that would imply Asus has fixed that or my AX88U is bad, but I tried on both of them. What I get on alpha build when I enable AiProtection (or Traffic Analyser) and then back when I withdraw from TrendMicro agreement is below - was same on 384

.