[Beta] Asuswrt-Merlin 384.14 Beta is now available

[DigitizedMe]

Tested both with asuscomm (DNS-based auth) and afraid (HTTP-based auth), both had no issue obtaining a Let's Encrypt certificate for me on my RT-AX88U.

Try clearing the content of /jffs/.le/ and /jffs/.certs/ first. If it still fails, send me your system log containing the acme.sh debug output.

EDIT: btw, all this "cat" command does is output the content of the certificate to the console, which is only useful when running acme.sh manually. The error message is simply because that output can't be sent to syslog.

  if [ "$Le_LinkCert" ]; then
    _info "$(__green "Cert success.")"
    cat "$CERT_PATH"

    _info "Your cert is in $(__green " $CERT_PATH ")"

    if [ -f "$CERT_KEY_PATH" ]; then
      _info "Your cert key is in $(__green " $CERT_KEY_PATH ")"
    fi

    if [ ! "$USER_PATH" ] || [ ! "$ACME_IN_CRON" ]; then
      USER_PATH="$PATH"
      _saveaccountconf "USER_PATH" "$USER_PATH"
    fi
  fi

I just gave that a try, and same problem. Neither cert.pem or chain.pem were automatically created from the fullchain.pem.

Which acme.sh command should I append --debug to?

 

[MarkRH]

Since using the 14 betas on my RT-AC68U, I've been seeing these spikes in data transfer. Since putting on beta 3, in the last 24 hour section:

Note: this spike is only in the WAN section. Does not appear in the Wired or Wireless tabs.

I do have NAT acceleration disabled:

Anyone else experience this?

 

[Elmer]

Upgraded ax88 to beta3 from beta2. Zero problems. Thanks.

 

[DigitizedMe]

Upgraded ax88 to beta3 from beta2. Zero problems. Thanks.

Can you verify that Let's Encrypt status is authorizing for your DDNS? Feel free to start a conversation with me to avoid bloating the thread more.

 

[skeal]

Can you verify that Let's Encrypt status is authorizing for your DDNS? Feel free to start a conversation with me to avoid bloating the thread more.

Make sure that on the administration page that you have set access to the webui to "both" http and https, (regardless of if you intend to use both or not). Close your browser and log back in. Check the status of your renewal on the DDNS page. May have to restart the router to get it to work.

 

[ryannathans]

RT-AC5300

Since upgrading to beta 3 I'm getting WiFi (5GHz) drops on my desktop PC that I haven't had on the previous stable version.

The WiFi "stays connected" according to Windows but with no internet and without the ability to even ping the router. My internet stays disconnected until I turn my PC's WiFi off and on again. After this happens my PC's download speed is limited to 30-40 megabit until I reboot the PC - despite showing as connected at 650mb/s.

After reconnect while speed is stuck slow:

The general log is FILLED with thousands of lines of the below, with the one leading line about deauthentication.


Dec 9 10:45:52 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 9 10:45:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 10:45:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 10:45:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 10:45:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 10:45:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)

 

[DigitizedMe]

Make sure that on the administration page that you have set access to the webui to "both" http and https, (regardless of if you intend to use both or not). Close your browser and log back in. Check the status of your renewal on the DDNS page. May have to restart the router to get it to work.

You da man! (Or woman)! It worked.

I don't want to derail the thread any longer, but I'm guessing something changed in the behavior to generate the LE SSL certs for the DDNS?

I only ask since I had web UI set to http only prior, and the LE cert was being created correctly before.

In my case, I use this cert for IPSEC IKEv2. However, I only access the web UI internally, so there was no need for https.

Merlin and SNB community exceeds my expectations once more!

 

[Butterfly Bones]

RT-AC5300

Since upgrading to beta 3 I'm getting WiFi (5GHz) drops on my desktop PC that I haven't had on the previous stable version.

The WiFi "stays connected" according to Windows but with no internet and without the ability to even ping the router. My internet stays disconnected until I turn my PC's WiFi off and on again. After this happens my PC's download speed is limited to 30-40 megabit until I reboot the PC - despite showing as connected at 650mb/s.

After reconnect while speed is stuck slow:
View attachment 20192

The general log is FILLED with thousands of lines of the below, with the one leading line about deauthentication.


Dec 9 10:45:52 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 9 10:45:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 10:45:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 10:45:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 10:45:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 10:45:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)

Below is the RMerlin reply when this was posted a couple pages back.
https://www.snbforums.com/threads/b...ta-is-now-available.60037/page-30#post-530933
More detailed RMerlin explanation.
https://www.snbforums.com/threads/r...13-is-now-available.57860/page-35#post-515660

 

[LimJK]

Beta 3 has been uploaded

RMerlin,
Thanks for Beta3, I noticed that WPA3 is no more there; it was there in the last Test Build for AX (RT-AX88U_384.14_beta2-new-gfec6767101).

 

[ryannathans]

Below is the RMerlin reply when this was posted a couple pages back.
https://www.snbforums.com/threads/b...ta-is-now-available.60037/page-30#post-530933
More detailed RMerlin explanation.
https://www.snbforums.com/threads/r...13-is-now-available.57860/page-35#post-515660

The difference is that I'm getting wifi drops that coincide with this deauth log, on the previous version these wifi drops did not exist. My WiFi does not reconnect until I manually reconnect in Windows - and then it's slow until the PC reboots (simply turning WiFi off and on again isn't enough)

Due to the new binary blobs for the AC5300 - would I need to do a full reset/wipe?

 

[Hawk]

RMerlin,
Thanks for Beta3, I noticed that WPA3 is no more there; it was there in the last Test Build for AX (RT-AX88U_384.14_beta2-new-gfec6767101).

View attachment 20197

It was special test build for rtax88u, Eric mentioned that GPL which has WPA3 support is buggy and will not be supported in 384.14.

Maybe in next version we might see support for it.

 

[RMerlin]

Selecting the simple share option does not make it simple (so turning that on does not work). (I'm sorry but I do not know how else to describe it)

Just tested it on my RT-AX88U and it's working for me. Which router model?

Make sure you aren't overriding smb.conf through a /jffs/configs/ config file.

Thanks for Beta3, I noticed that WPA3 is no more there; it was there in the last Test Build for AX (RT-AX88U_384.14_beta2-new-gfec6767101).

The "-new" in the version indicated it was a special test build with the new SDK. The new SDK is too buggy so it will not be merged in 384.14.

Due to the new binary blobs for the AC5300 - would I need to do a full reset/wipe?

Try forgetting the SSID on your client then reconnect it. Based on the error message, it seems your client is the one leaving the AP.

 

[ryannathans]

Try forgetting the SSID on your client then reconnect it. Based on the error message, it seems your client is the one leaving the AP.

Done - hopefully this stops me needing to reboot my PC every 15mins! I wonder why the router update started making my PC behave strangely. Maybe something to do with the smart connect (I have both 5GHz bands as one SSID)?

 

[SheikhSheikha]

Just tested it on my RT-AX88U and it's working for me. Which router model?

Make sure you aren't overriding smb.conf through a /jffs/configs/ config file.



The "-new" in the version indicated it was a special test build with the new SDK. The new SDK is too buggy so it will not be merged in 384.14.



Try forgetting the SSID on your client then reconnect it. Based on the error message, it seems your client is the one leaving the AP.

RT-AC5300

 

[ryannathans]

RT-AC5300

Interesting, I had SMB problems with my RT-AC5300 too - https://www.snbforums.com/threads/b...ta-is-now-available.60037/page-30#post-530959

 

[SheikhSheikha]

Interesting, I had SMB problems with my RT-AC5300 too - https://www.snbforums.com/threads/b...ta-is-now-available.60037/page-30#post-530959

Make sure that immediately after the update to 384.14B3 you configure on the LAN IP tab the Host name and Domain Name (as it is set to a default with the update). (at least I think that there your problem originated).

 

[ryannathans]

Make sure that immediately after the update to 384.14B3 you configure on the LAN IP tab the Host name and Domain Name (as it is set to a default with the update). (at least I think that there your problem originated).

It seems the IP address persisted from the last update but the domain name is now an empty text box. I will add a domain but not sure if I'll be able to reproduce the original problem

 

[ryannathans]

Try forgetting the SSID on your client then reconnect it. Based on the error message, it seems your client is the one leaving the AP.

Unfortunately this did not fix the issue. It's so odd, restarting the router or my network in windows doesn't return me back to full speed (stuck at 40 megabit after first drop) - only rebooting the PC.

When this problem happens windows thinks it's still connected to the AP but with "no internet" until I manually disconnect and reconnect.

Is eth2 and eth3 the two 5ghz networks?

Dec 9 15:43:57 syslog: WLCEVENTD wlceventd_proc_event(420): eth3: Auth 50:E0:85:9D:46:08, status: 0, reason: d11 RC reserved (0)
Dec 9 15:43:57 syslog: WLCEVENTD wlceventd_proc_event(430): eth3: ReAssoc 50:E0:85:9D:46:08, status: 0, reason: d11 RC reserved (0)
Dec 9 15:43:57 syslog: WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 9 15:43:57 dnsmasq-dhcp[6603]: DHCPREQUEST(br0) 192.168.1.6 50:e0:85:9d:46:08
Dec 9 15:43:57 dnsmasq-dhcp[6603]: DHCPACK(br0) 192.168.1.6 50:e0:85:9d:46:08 DESKTOP-C7MMC3O
Dec 9 15:44:18 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 9 15:44:18 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 15:44:18 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 15:44:18 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 15:44:19 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 9 15:44:19 syslog: WLCEVENTD wlceventd_proc_event(386): eth3: Deauth_ind 50:E0:85:9D:46:08, status: 0, reason: Class 3 frame received from nonassociated station (7)

 

[Damian987]

DDNS not working

Dec 9 06:21:17 kernel: [Mon Dec 9 06:21:17 UTC 2019]
Dec 9 06:21:17 kernel: Registering account
Dec 9 06:21:19 kernel: [Mon Dec 9 06:21:19 UTC 2019]
Dec 9 06:21:19 kernel: Already registered
Dec 9 06:21:19 kernel: [Mon Dec 9 06:21:19 UTC 2019]
Dec 9 06:21:19 kernel: ACCOUNT_THUMBPRINT='4tTNdkrA7-vr2B_Wb-zEBtneWJsP61EiSFN7d6ZS8Fs'
Dec 9 06:21:19 kernel: [Mon Dec 9 06:21:19 UTC 2019]
Dec 9 06:21:19 kernel: Single domain='DamianPogoda.asuscomm.com'
Dec 9 06:21:19 kernel: [Mon Dec 9 06:21:19 UTC 2019]
Dec 9 06:21:19 kernel: Getting domain auth token for each domain
Dec 9 06:21:21 kernel: [Mon Dec 9 06:21:21 UTC 2019]
Dec 9 06:21:21 kernel: Getting webroot for domain='DamianPogoda.asuscomm.com'
Dec 9 06:21:21 kernel: [Mon Dec 9 06:21:21 UTC 2019]
Dec 9 06:21:21 kernel: get to authz error.
Dec 9 06:21:21 kernel: [Mon Dec 9 06:21:21 UTC 2019]
Dec 9 06:21:21 kernel: _authorizations_map='damianpogoda.asuscomm.com,{"identifier":{"type":"dns","value":"damianpogoda.asuscomm.com"},"status":"pending","expires":"2019-12-16T04:57:06Z","challenges":[{"type":"http-01","status":"pending","url":"https://acme-v02.api.letsencrypt.org/acme/chall-v3/1628891205/7_SHNg","token":"lQPoAAxz5sXen7NUtxWDS8Hj3j_xpfzgzt-s_qzuBa4"},{"type":"dns-01","status":"pending","url":"https://acme-v02.api.letsencrypt.org/acme/chall-v3/1628891205/zq3S9Q","token":"lQPoAAxz5sXen7
Dec 9 06:21:21 kernel: '
Dec 9 06:21:21 kernel: [Mon Dec 9 06:21:21 UTC 2019]
Dec 9 06:21:21 kernel: Please add '--debug' or '--log' to check more details.
Dec 9 06:21:21 kernel: [Mon Dec 9 06:21:21 UTC 2019]
Dec 9 06:21:21 kernel: See: https://github.com/Neilpang/acme.sh/wiki/How-to-debug-acme.sh

 

[RMerlin]

These messages are related to Let's Encrypt, not DDNS. Status pending probably means throttling.

Sent from my SM-T720 using Tapatalk