Beta Asuswrt-Merlin 386.1 Beta is now available

[RMerlin]

After upgrading to Beta 2 my Wireless General page has been reformatted again. I've included the page below. However wifi continues to work but of course settings are no longer available.

Cannot reproduce, try a factory default reset including erasing the JFFS partition content, and also make sure your JFFS partition is properly mounted.

 

[swejuggalo]

I apparently was happy about about Lets encrypt too early. It did not update and but it looked good in the log... So I rebooted.

Then this.

May 5 07:10:17 scMerlin: NTP failed to sync after 5 minutes. Please resolve!
May 5 07:10:17 ntpMerlin: NTP failed to sync after 5 minutes. Please resolve!
May 5 07:10:22 Skynet: [*] NTP Failed To Start After 5 Minutes - Please Fix Immediately!
May 5 07:10:24 S77ntpd: NTP failed to sync after 5 minutes - please check immediately!
May 5 07:10:24 swejuggalo: Started tailtopd from /jffs/scripts/post-mount.
May 5 07:10:32 Skynet: [*] NTP Failed To Start After 5 Minutes - Please Fix Immediately!

An no internet access.

All scripts failed after reboot. Restored JFFS and it's now good again. Will replicate if possible

Did the same steps... But did not happen again. Nor do I see lets encrypt writing any files to JFFS in the log.

Dec 14 19:31:00 rc_service: service 6049:notify_rc restart_letsencrypt
Dec 14 19:31:00 custom_script: Running /jffs/scripts/service-event (args: restart letsencrypt)
Dec 14 19:31:01 kernel: bcm_i2c: bus 0: Failed to detect SFP: 100 retries exhausted

Maybe this means something of value

 

[kernol]

Can anyone confirm the AiMesh issues with AC5300 are resolved with beta 2?

Works for me - but see my config from signature - using AC5300 as AiMesh Node with AC86U as AiMesh Router.
That config did NOT work with b1 on the AC5300.

 

[skeal]

Cannot reproduce, try a factory default reset including erasing the JFFS partition content, and also make sure your JFFS partition is properly mounted.

Done and done. I reset coming from 386.1 Alpha for the first Beta. I struggled with the problem then as well. So it's not a new problem for me. As a matter of fact I think I reset 5 or 6 times on account of this page being rendered that way. Oh and replaced my jffs completely.

 

[jewelr]

Works for me - but see my config from signature - using AC5300 as AiMesh Node with AC86U as AiMesh Router.
That config did NOT work with b1 on the AC5300.

I will be using AC5300 as AiMesh Router and AC68U as AiMesh Node. If your issue was resolved in B2 I'm guessing using AC5300 as AiMesh Router should work as well. I will soon find out. Thanks!

 

[distilled]

AC86U as router, AC68U as node. Dirty flashed the router with Beta 2, left the node running the official 386 release. Everything was working perfectly, and I was *really* hoping something would break so I could participate in troubleshooting, but, sadly, things seem to be running smooth all around.

Oh well, can't win them all. Maybe I will get really drunk before trying to apply the next one.

 

[skeal]

Cannot reproduce, try a factory default reset including erasing the JFFS partition content, and also make sure your JFFS partition is properly mounted.

This is with a minimum configuration and without touching wifi. As you can see the default SSID are still in use. This was after one of the several resets that I did. I tried the reset from the GUI and the wps power option and it resets but this continues to happen eventually.

 

[octopus]

Have you tried with: Ctrl-F5 ?

 

[STRUZZIN]

All updated to BETA 2 on 2 AX58U & 68U running fine so far.

 

[jckblack7]

Can anyone confirm the AiMesh issues with AC5300 are resolved with beta 2?

I'm running Open Beta on my GT-AC5300 as node and Beta 2 on my AC86U. so far so good. Network map page was loading slow at first, i rebooted and it seems fine now.

 

[skeal]

Have you tried with: Ctrl-F5 ?

Yes I have. This is present on all devices in my network.

 

[JoGi]

(dirty) update from 386.1 beta1> beta2
everything works and stable, Unfortunately "Let's Encrypt" (www.asus.com) still doesn't work :-(

 

[jerry6]

beta 2 working well on my rt5300 , no more log entries every 10 seconds . everything is working as it should sorry
today logs a filled again , do i have a problem ?

Dec 15 11:32:05 syslog: wlceventd_proc_event(539): eth1: Assoc 40:6F:2A:E4:B2:96, status: Successful (0)

Dec 15 11:32:13 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 40:6F:2A:E4:B2:96, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 15 11:32:13 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 40:6F:2A:E4:B2:96, status: 0,
Thank you Merlin

 

[shabbs]

Updated all three devices (APs) running Beta 1 with Beta 2. No issues so far.

Primary/Main Router remains on 384.19 Release at this time.

So far so good. Thanks again @RMerlin

 

[jewelr]

beta 2 working well on my rt5300 , no more log entries every 10 seconds . everything is working as it should
Thank you Merlin

Are you running the 5300 as AiMesh Router?

 

[shabbs]

beta 2 working well on my rt5300 , no more log entries every 10 seconds . everything is working as it should
Thank you Merlin

Gonna miss that wlceventd guy...

 

[brummygit]

Let's Encrypt issue +1 (AX88U)

 

[LaMpiR]

This looks very promising. Thank you @RMerlin for the effort

Currently have AX88U with latest stable 384.19. If I install the beta 2 now, would I need to do the factory reset? If yes, then I would probably wait the stable version for it. Would be nice to know a guessed timeline for the stable version?

 

[bluzfanmr1]

Upgraded from 384.18 to 386.1_beta2 and all seems well so far. That being said, I now have the following in my routing table. This appears to be connecting to a Facebook IP. Does anyone know why the heck this would be happening?

br2
Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:192.168.102.1 Bcast:192.168.102.255 Mask:255.255.255.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:2029 errors:0 dropped:0 overruns:0 frame:0
TX packets:1955 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:437254 (427.0 KiB) TX bytes:545156 (532.3 KiB)

 

[kernol]

Beta 2 is now available. Changes since beta 1:

Additional things to test:

• RT-AC68U V3 support (untested)
• Let's Encrypt renewal

Let's Encrypt still not working for me on RT-AC86U ... but just could be because I imported prior certificate issued under 384.19 when I could not get 386.1_b1 to work. Stuck on "Updating" in webui ... but log shows ...

Dec 14 20:46:55 RT-AC86U-8178 kernel: The For ALL DEVICES flag of Prof 1 has been set to ENABLE
Dec 14 20:46:55 RT-AC86U-8178 httpd: mssl_cert_key_match : PASS
Dec 14 20:46:55 RT-AC86U-8178 httpd: Succeed to init SSL certificate...80
Dec 14 20:46:55 RT-AC86U-8178 httpd: Succeed to init SSL certificate...8443
Dec 14 20:50:00 RT-AC86U-8178 rc_service: service 1156:notify_rc restart_letsencrypt
Dec 14 20:50:00 RT-AC86U-8178 custom_script: Running /jffs/scripts/service-event (args: restart letsencrypt)
Dec 14 20:50:01 RT-AC86U-8178 custom_script: Running /jffs/scripts/service-event-end (args: restart letsencrypt)
Dec 14 20:50:01 RT-AC86U-8178 FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=1159) called in unattended mode with 1 args: -check
Dec 14 20:50:01 RT-AC86U-8178 FlexQoS: iptables rules already present
Dec 14 20:50:01 RT-AC86U-8178 FlexQoS: TC Modification Delayed Start
Dec 14 20:50:04 RT-AC86U-8178 kernel[Mon]: Dec 14 20:50:04 GMT 2020]
Dec 14 20:50:04 RT-AC86U-8178 kernel: not changed.
Dec 14 20:50:04 RT-AC86U-8178 kernel[Mon]: Dec 14 20:50:04 GMT 2020]
Dec 14 20:50:04 RT-AC86U-8178 kernel: Next renewal time is: Thu Feb  4 07:26:09 UTC 2021
Dec 14 20:50:04 RT-AC86U-8178 kernel[Mon]: Dec 14 20:50:04 GMT 2020]
Dec 14 20:50:04 RT-AC86U-8178 kernel: '--force' to force to renew.

It is clearly finding my imported certificate - correctly asserting its renewal date - but failing to update the info on the webui page to show all is well. If someone can direct me on how to clear the existing certificate [without a full reset] I am happy to start afresh and see if obtaining the certificate from LetsEncrypt instead of using my prior one from the same source will fix the prior issues under b1.