Beta Asuswrt-Merlin 386.1 Beta is now available

[Kees17760]

Hi,

Don't know if this is the right place, but noticed 2 things after installing 386.1 beta 1 on my AC2900.
- Clients on Guest network 1 (2,4 GHz) can't access internet
- CPU temperature appears to be +/- 5 degr. Celsius higher compared to 384.19

 

[Jumpstarter]

There are now "4" that can confirm that this happens.

what happens if you hit the log out button repetitively? or scroll up and down the page constantly?

 

[John Fitzgerald]

what happens if you hit the log out button repetitively? or scroll up and down the page constantly?

I've already updated to the patched version.

RT-AX58U crash should be fixed - the firmware was missing a userspace tool to control hardware acceleration.

RT-AX58U_386.1_beta1-ge88f0d2171_cferom_pureubi.w

W File

1drv.ms

 

[Jumpstarter]

Hi,

Don't know if this is the right place, but noticed 2 things after installing 386.1 beta 1 on my AC2900.
- Clients on Guest network 1 (2,4 GHz) can't access internet
- CPU temperature appears to be +/- 5 degr. Celsius higher compared to 384.19

Yea I noticed my router temps a few degrees higher. I can't get Yazfi settings to span across the network to Node guest networks either.... clients keep disconnecting or getting an ip from a different ip address pool.....

 

[Jumpstarter]

I've already updated to the patched version.

I hit the apply button on my wifi settings page and the router rebooted. It also rebooted while pairing a node.

 

[John Fitzgerald]

I hit the apply button on my wifi settings page and the router rebooted. It also rebooted while pairing a node.

Normal

 

[bbunge]

Hi,

Don't know if this is the right place, but noticed 2 things after installing 386.1 beta 1 on my AC2900.
- Clients on Guest network 1 (2,4 GHz) can't access internet
- CPU temperature appears to be +/- 5 degr. Celsius higher compared to 384.19

Guest network 1 for 2.4 and 5 GHZ sets a new IP subnet (192.168.101.0/24 and 192.168.102.0/24). This is to allow the guest WIFI to extend to the AiMesh nodes. I have observed that, with Diversion/DNSfilter - router, enabled, the clients assigned to Guest Network index 1 (the left Enable button) may not connect to the internet. I have set the clients to No Filtering in DNSfilter and they still do not connect. Moving to Guest Network index 2 or 3 assigns the same subnet as the router and with DNFfilter no filtering set for the clients they connect. Am not sure if this is a Diversion/Merlin issue or goes back to the Asus code.

For now, if you are having guest WIFI issues move your guest to Guest Network index 2 or 3, set DNSfilter, if used, (a) to global no filtering or (b) to global router and set each client in the guest WIFI to no filtering.

 

[mcosty]

Something is preventing that page from loading properly. Open your browser console and look for Javascript errors.

Here is screenshot of the console.

 

[RMerlin]

Here is screenshot of the console.

Shift-reload the page, access over https with self-signed certs is often quirky for unknown reasons.

 

[mcosty]

Shift-reload the page, access over https with self-signed certs is often quirky for unknown reasons.

Ah yes thanks!! That gets rid of it when on the page but it does come back when navigating away and back again but the shift+refresh fixes it.

 

[Treadler]

Glad things seem to be working out for you - my setup is now fully stable - BUT I am not able to use Guest1 WiFi without the issues reported in this thread ...
http://www.snbforums.com/threads/386-1-b1-on-rt-ac86u-log-spam-protocol-0800-is-buggy.68240/

Maybe it only occurs if, like me, you are using QoS and Guest1 WiFi ?

Good catch!
Using QOS & guest network.
Shifted guest network to the right, (1 > 2) & the errors have stopped cluttering the log.

 

[DigitizedMe]

Can someone post the jffs/scripts/ipsec.conf file after the update?

I only did a dirty upgrade with my old ipsec.conf in place. I'd like to use the new ASUS certificates with the default IKEv2 support that has certs which don't expire until 2026!

I had previously modified my ipsec.conf to be dependent on the Let's Encrypt certs from the WAN > DDNS using the following lines:

pc_append "ca letsencrypt" $CONFIG
pc_append "  cacert=/jffs/.le/$(nvram get ddns_hostname_x)/ca.cer" $CONFIG
pc_append "  leftcert=/jffs/.le/$(nvram get ddns_hostname_x)/my.domain.cer" $CONFIG

Then if Let's Encrypt cert renewal fails, I don't believe my IKEv2 will! (Honestly I don't believe Let's Encrypt will even matter for me anymore since I don't use the web ui outside of WAN.

Thanks in advance!

 

[SpicyApple]

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.

I have exactly the same problem. What is the issue here? Is it due to Asus firmware or can it be solved in Merlin?

 

[AntonK]

Did someone post awhile ago on how to eliminate the, well, irritating "wlceventd" entries in the log?

By that I mean, is there a way to set the Default Message Log Level, and Log Only Messages More Urgent Than so that Skynet, etc.. continues to function but you reduce the amount of unnecessary debugging log entries?

Thanks,
Anton

 

[LimJK]

Asus have released an update for the RT-AX88U. (386_41249)

AdrianH,
Where did you get this RT-AX88U 386_41249 firmware? Thanks

 

[Mutzli]

If upgrading from the alpha. And recommended if coming from stock.

I haven't seen any posts to say that dirty flashing from the 384 series would cause specific issues. (Though I haven't completely combed the thread yet).

Yes, but if you encounter problems the first thing I would do is a factory reset. Some NVRAM values could remain and cause issues with certain settings.

 

[bluepoint]

AdrianH,
Where did you get this RT-AX88U 386_41249 firmware? Thanks

ASUS RT-AX88U Firmware v3.0.0.4.386_41249 | SmallNetBuilder Forums (snbforums.com)

 

[Diddy]

No, there has been no change that I'm aware of related to that in 386.1.

I only ask, because, even with the bad JFFS parition, the 3100 works fine as a node on 384.19. Have it running that way now. It's only when I install the beta that it's not discoverable, or even pingable (but it has an IP).

 

[RMerlin]

I only ask, because, even with the bad JFFS parition, the 3100 works fine as a node on 384.19. Have it running that way now. It's only when I install the beta that it's not discoverable, or even pingable (but it has an IP).

As mentionned before, AiMesh is not working properly on the RT-AC3100 and RT-AC5300 with beta 1.

 

[Bulls729]

Remove USB devices before updating - this is somewhat the recommended procedure that you do before updating the firmware as it may sometimes hinder the firmware update process

No USB devices are connected.