Beta Asuswrt-Merlin 386.1 Beta is now available

Status
Not open for further replies.

dave14305

Part of the Furniture
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?

View attachment 28494

View attachment 28495

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)
Is this the new VLAN for Guest Network #1?
 

MysticGold04

Regular Contributor
Many thanks for this firmware, Merlin - I have accumulated 8 days of uptime on beta1, and plan to update to beta2 tonight when everyone is off of work and school. I have a relatively simple config - static leases, plus one VPN Client (Policy routed) and FlexQos. It all works great!!

**aside from AiMesh being unstable for streaming on a node (another 68u)
More testing to come.


Beta 2 is now available.
 

bluzfanmr1

Senior Member
Is this the new VLAN for Guest Network #1?

That must have been it! I just happened to set up a new guest network last night before upgrading to Beta 2 this afternoon. I just disabled Guest Network #1 and those entries disappeared from the routing table.. I then moved things to Guest Network #2 and I did not get those items again in the routing table. Thanks so much for the tip!
 

WillyTP

Regular Contributor
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 ...

Code:
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.

Unfortunately I confirm too this issue on Beta 2.
 

Stoonhea020

Occasional Visitor
I upgrade from beta 1 to 2 and factory reset my router RT-AX86U. Unfortunately the issue with the le certificate remains. The GUI remains in authorizing state and my (partial) log says:

Dec 14 20:40:37 kernel: Lets finalize the order, Le_OrderFinalize: https://acme-v02.api.letsencrypt.org/acme/finalize/106348865/6742417819
Dec 14 20:40:39 kernel: [Mon Dec 14 20:40:39 UTC 2020]
Dec 14 20:40:39 kernel: Download cert, Le_LinkCert: https://acme-v02.api.letsencrypt.org/acme/cert/04dd764c7cc83f38f1c358f41c6196300f34
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: Cert success.
Dec 14 20:40:40 kernel: cat: write error: Invalid argument
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: Your cert is in /jffs/.le/xxxxxxxxxx.asuscomm.com/xxxxxxxxxx.asuscomm.com.cer
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: Your cert key is in /jffs/.le/xxxxxxxxxx.asuscomm.com/xxxxxxxxx.asuscomm.com.key
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: The intermediate CA cert is in /jffs/.le/xxxxxxxxxx.asuscomm.com/ca.cer
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: And the full chain certs is there: /jffs/.le/xxxxxxxxxxx.asuscomm.com/fullchain.cer
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: Installing key to:/jffs/.le/xxxxxxxxxx.asuscomm.com/domain.key
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: Installing full chain to:/jffs/.le/xxxxxxxxx.asuscomm.com/fullchain.pem
Dec 14 20:40:41 kernel: CONSOLE: 047399.339 wl1.0: wlc_send_bar: for e0:d4:e8:99:54:80 seq 0x1 tid 4
Dec 14 19:41:00 rc_service: service 7744:notify_rc restart_letsencrypt
Dec 14 20:41:02 kernel: [Mon Dec 14 20:41:02 UTC 2020]
Dec 14 20:41:02 kernel: Domains not changed.
Dec 14 20:41:02 kernel: [Mon Dec 14 20:41:02 UTC 2020]
Dec 14 20:41:02 kernel: Skip, Next renewal time is: Fri Feb 12 19:40:40 UTC 2021
Dec 14 20:41:02 kernel: [Mon Dec 14 20:41:02 UTC 2020]
Dec 14 20:41:02 kernel: Add '--force' to force to renew.

It seems that the certificate gets successfully installed but is not shown as such on the GUI. Also the certificate isn't working since WAN access towards the GUI gives an NET::ERR_CERT_AUTHORITY_INVALID error.
 

swejuggalo

Regular Contributor
(dirty) update from 386.1 beta1> beta2
everything works and stable, Unfortunately "Let's Encrypt" (www.asus.com) still doesn't work :-(
View attachment 28493
Did you also reboot after enabling Let's Encypt? (never tried it since a clean install, since I knew it did not work anyway). I had it set to none before upgrading. Then enabled Let's encrypt after the update. Files were written to JFFS and the cerficiation seemed to actually pull through. But still not beyond just Authorizing in the GUI. So I rebooted it. Then NTP failed and I count not access internet, and no scripts worked. Had to restore JFFS. Now when I enable Let's encrypt not much seems to happen in the logs. Odd
 

swejuggalo

Regular Contributor
I upgrade from beta 1 to 2 and factory reset my router RT-AX86U. Unfortunately the issue with the le certificate remains. The GUI remains in authorizing state and my (partial) log says:

Dec 14 20:40:37 kernel: Lets finalize the order, Le_OrderFinalize: https://acme-v02.api.letsencrypt.org/acme/finalize/106348865/6742417819
Dec 14 20:40:39 kernel: [Mon Dec 14 20:40:39 UTC 2020]
Dec 14 20:40:39 kernel: Download cert, Le_LinkCert: https://acme-v02.api.letsencrypt.org/acme/cert/04dd764c7cc83f38f1c358f41c6196300f34
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: Cert success.
Dec 14 20:40:40 kernel: cat: write error: Invalid argument
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: Your cert is in /jffs/.le/xxxxxxxxxx.asuscomm.com/xxxxxxxxxx.asuscomm.com.cer
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: Your cert key is in /jffs/.le/xxxxxxxxxx.asuscomm.com/xxxxxxxxx.asuscomm.com.key
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: The intermediate CA cert is in /jffs/.le/xxxxxxxxxx.asuscomm.com/ca.cer
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: And the full chain certs is there: /jffs/.le/xxxxxxxxxxx.asuscomm.com/fullchain.cer
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: Installing key to:/jffs/.le/xxxxxxxxxx.asuscomm.com/domain.key
Dec 14 20:40:40 kernel: [Mon Dec 14 20:40:40 UTC 2020]
Dec 14 20:40:40 kernel: Installing full chain to:/jffs/.le/xxxxxxxxx.asuscomm.com/fullchain.pem
Dec 14 20:40:41 kernel: CONSOLE: 047399.339 wl1.0: wlc_send_bar: for e0:d4:e8:99:54:80 seq 0x1 tid 4
Dec 14 19:41:00 rc_service: service 7744:notify_rc restart_letsencrypt
Dec 14 20:41:02 kernel: [Mon Dec 14 20:41:02 UTC 2020]
Dec 14 20:41:02 kernel: Domains not changed.
Dec 14 20:41:02 kernel: [Mon Dec 14 20:41:02 UTC 2020]
Dec 14 20:41:02 kernel: Skip, Next renewal time is: Fri Feb 12 19:40:40 UTC 2021
Dec 14 20:41:02 kernel: [Mon Dec 14 20:41:02 UTC 2020]
Dec 14 20:41:02 kernel: Add '--force' to force to renew.

It seems that the certificate gets successfully installed but is not shown as such on the GUI. Also the certificate isn't working since WAN access towards the GUI gives an NET::ERR_CERT_AUTHORITY_INVALID error.
Same. And then it ran havoc after a reboot (see post above)
 

RMerlin

Asuswrt-Merlin dev
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

You won`t get anything from Let's Encrypt if you already have a certificate still valid for at least one month.

The bcm_i2c line has nothing to do with it.

Currently have AX88U with latest stable 384.19. If I install the beta 2 now, would I need to do the factory reset?

Update guidelines are in the first post.

Does anyone know why the heck this would be happening?

I believe one of the Guest Networks is dedicated to Facebook Wifi (it`s clearly labeled as such on the Guest Network page).
 

det721

Part of the Furniture
Just installed Beta 2 AX58U. Rocking right along no issues thus far. Thanks @Merlin !!
 

JWoo

Senior Member
Upgraded from Beta 1 to Beta 2 on my RT-AX58U. Seems solid. Aunt Budge very happy. New function reporting HW acceleration from HW instead of a parameter is a great idea.

1607988504797.png
 

cmillar6

Senior Member
Try doing a factory default reset first, configure just basic Wifi, then immediately proceed to flashing the new firmware. Your router might be crashing because you have settings that try to access the broken hardware acceleration system. If it still fails, flash it while in Recovery Mode.
By the way, my AX58u flashed just fine going from beta 1 to beta 2 so this was evidently the issue causing my router not to flash between all the Alpha's
 

EricTheRed

Occasional Visitor
I installed Beta 2 on an AX-86U and wiped all settings. Bandwidth monitor is still broken in anything but traditional QoS mode.
 

anotherengineer

Regular Contributor
Would it be wrong to wish for brand new Merlin FW for Christmas??? :)

I know it's one of the things on my list :)
 

isr25

Regular Contributor
On AX86U - LE still stuck on Authorizing. Ran the below command after installing Beta 2 and results are the same.

rm -rf /jffs/.le
service restart_letsencrypt
 

L&LD

Part of the Furniture
No, it wouldn't be wrong to wish for. But as far as I can see, we already got it with Beta 2. ;)
 

magwa_sc

Occasional Visitor
Anyone else having issues with DHCP from the ISP? I am getting the error message "your isp's dhcp does not function properly" I saw this in the changelog, but it seems to have caused an issue for me rather than fix anything:
- FIXED: DHCP could fail to renew its lease with some ISPs when Trend Micro engine was enabled (workaround provided by Asus)

Router: RT-AC5300
Firmware: 386.1 beta 1 (Also tried to use Beta 2 and also having same issue)
ISP: Spectrum
Upgrade Procedure to 386.1 beta 1: Dirty flash over 384.19
Modem Config: Bridge mode to give my Router a public ip address (75.X.X.X)

I tried rebooting my router and modem multiple times, tried to use a different MAC address and clone MAC Address and still seeing the issue. I tried to turn off the Trend Micro security features and reboot but that didnt resolve the issue. It would first get a 192.168.100.11 address and then try to get the bridged exteral IP address and would fail. I rolled back to 384.19 and it was able to perform then 192.168.100.11 to 75.X.X.X transition for the WAN ip address without issue and now I am back to working normally after rolling back. :(
 

Attachments

  • Capture.JPG
    Capture.JPG
    47.2 KB · Views: 113
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top