What's new

Beta Asuswrt-Merlin 386.1 Beta is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Having issues accessing cameras via OPENVPN Server on AX-86U on both Beta 2 and Beta 3. This is from OVPN client on Iphone. The logs from OPENVPN and SYSLOG follow. Anyone else having issues with OPENVPN Server on AX-86U?


Code:
Dec 29 14:08:25 RT-AX86U-AC30 ovpn-server2[3021]: client/1.129.110.41:19678 SIGTERM[soft,remote-exit] received, client-instance exiting
Dec 29 14:08:39 RT-AX86U-AC30 ovpn-server1[2734]: Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Dec 29 14:08:39 RT-AX86U-AC30 ovpn-server1[2734]: Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Dec 29 14:08:39 RT-AX86U-AC30 ovpn-server1[2734]: TCP connection established with [AF_INET]1.129.110.41:1714
Dec 29 14:08:39 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 TLS: Initial packet from [AF_INET]1.129.110.41:1714, sid=b24fb0c1 bef02c69
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 VERIFY OK: depth=1, C=TW, ST=TW, L=Taipei, O=ASUS, OU=Home/Office, CN=RT-AX86U, emailAddress=me@asusrouter.lan
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 VERIFY OK: depth=0, C=TW, ST=TW, L=Taipei, O=ASUS, OU=Home/Office, CN=client, emailAddress=me@asusrouter.lan
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 peer info: IV_VER=3.git::2952f561
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 peer info: IV_PLAT=ios
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 peer info: IV_NCP=2
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 peer info: IV_TCPNL=1
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 peer info: IV_PROTO=2
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 peer info: IV_IPv6=0
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 peer info: IV_GUI_VER=net.openvpn.connect.ios_3.2.2-3507
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 peer info: IV_SSO=openurl
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 peer info: IV_BS64DL=1
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 PLUGIN_CALL: POST /usr/lib/openvpn-plugin-auth-pam.so/PLUGIN_AUTH_USER_PASS_VERIFY status=0
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 TLS: Username/Password authentication succeeded for username 'joescian'
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 2048 bit RSA
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: 1.129.110.41:1714 [client] Peer Connection Initiated with [AF_INET]1.129.110.41:1714
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: client/1.129.110.41:1714 MULTI_sva: pool returned IPv4=10.8.0.2, IPv6=(Not enabled)
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: client/1.129.110.41:1714 MULTI: Learn: 10.8.0.2 -> client/1.129.110.41:1714
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: client/1.129.110.41:1714 MULTI: primary virtual IP for client/1.129.110.41:1714: 10.8.0.2
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: client/1.129.110.41:1714 Data Channel: using negotiated cipher 'AES-256-GCM'
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: client/1.129.110.41:1714 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: client/1.129.110.41:1714 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: client/1.129.110.41:1714 PUSH: Received control message: 'PUSH_REQUEST'
Dec 29 14:08:40 RT-AX86U-AC30 ovpn-server1[2734]: client/1.129.110.41:1714 SENT CONTROL [client]: 'PUSH_REPLY,route 192.168.2.0 255.255.255.0 vpn_gateway 500,dhcp-option DOMAIN RT-AX86U-DOMAIN,dhcp-option DNS 192.168.2.242,redirect-gateway def1,route-gateway 10.8.0.1,topology subnet,ping 15,ping-restart 60,ifconfig 10.8.0.2 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Dec 29 14:10:31 RT-AX86U-AC30 ovpn-server1[2734]: client/1.129.110.41:1714 Connection reset, restarting [0]
Dec 29 14:10:31 RT-AX86U-AC30 ovpn-server1[2734]: client/1.129.110.41:1714 SIGUSR1[soft,connection-reset] received, client-instance restarting
Dec 29 14:10:33 RT-AX86U-AC30 ovpn-server2[3021]: 1.129.110.41:14158 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Dec 29 14:10:33 RT-AX86U-AC30 ovpn-server2[3021]: 1.129.110.41:14158 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Dec 29 14:10:33 RT-AX86U-AC30 ovpn-server2[3021]: 1.129.110.41:14158 TLS: Initial packet from [AF_INET]1.129.110.41:14158, sid=06b57b9f dd8734ca
Dec 29 14:10:34 RT-AX86U-AC30 ovpn-server2[3021]: 1.129.110.41:14158 VERIFY OK: depth=1, C=TW, ST=TW, L=Taipei, O=ASUS, OU=Home/Office, CN=RT-AX86U, emailAddress=me@asusrouter.lan
Dec 29 14:10:34 RT-AX86U-AC30 ovpn-server2[3021]: 1.129.110.41:14158 VERIFY OK: depth=0, C=TW, ST=TW, L=Taipei, O=ASUS, OU=Home/Office, CN=client, emailAddress=me@asusrouter.lan
D

Code:
Dec 29 14:07:51 RT-AX86U-AC30 kernel: CONSOLE: 077364.104 wl1: wlc_ampdu_recv_addba_resp: 54:60:09:7c:93:9e: Failed. status 37 wsize 16 policy 1
Dec 29 14:08:51 RT-AX86U-AC30 kernel: CONSOLE: 077423.796 wl1: wlc_ampdu_recv_addba_resp: 54:60:09:7c:93:9e: Failed. status 37 wsize 16 policy 1
Dec 29 14:09:51 RT-AX86U-AC30 kernel: CONSOLE: 077483.489 wl1: wlc_ampdu_recv_addba_resp: 54:60:09:7c:93:9e: Failed. status 37 wsize 16 policy 1
Dec 29 14:10:51 RT-AX86U-AC30 kernel: CONSOLE: 077543.182 wl1: wlc_ampdu_recv_addba_resp: 54:60:09:7c:93:9e: Failed. status 37 wsize 16 policy 1
Dec 29 14:11:51 RT-AX86U-AC30 kernel: CONSOLE: 077602.874 wl1: wlc_ampdu_recv_addba_resp: 54:60:09:7c:93:9e: Failed. status 37 wsize 16 policy 1
Dec 29 14:12:51 RT-AX86U-AC30 kernel: CONSOLE: 077662.568 wl1: wlc_ampdu_recv_addba_resp: 54:60:09:7c:93:9e: Failed. status 37 wsize 16 policy 1
Dec 29 14:13:51 RT-AX86U-AC30 kernel: CONSOLE: 077722.262 wl1: wlc_ampdu_recv_addba_resp: 54:60:09:7c:93:9e: Failed. status 37 wsize 16 policy 1
Dec 29 14:14:42 RT-AX86U-AC30 kernel: wl0: random key value: FF71090D3A1EEA3215BE004E8EA680869EEBAF29E5FB0C3BA5C3CDB7FF6A67CB
Dec 29 14:14:42 RT-AX86U-AC30 hostapd: eth6: STA 04:d4:c4:45:f4:41 IEEE 802.11: disassociated
Dec 29 14:14:42 RT-AX86U-AC30 kernel: wl0: set timeout 5 secs to wait dev reg finish
Dec 29 14:14:42 RT-AX86U-AC30 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 0
Dec 29 14:14:42 RT-AX86U-AC30 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 29 14:14:42 RT-AX86U-AC30 kernel: br0: port 10(wds0.0.1.0) entered disabled state
Dec 29 14:14:42 RT-AX86U-AC30 kernel: br1: port 9(wds0.0.1.501) entered disabled state
Dec 29 14:14:42 RT-AX86U-AC30 kernel: device wds0.0.1 left promiscuous mode
Dec 29 14:14:42 RT-AX86U-AC30 kernel: br0: port 11(wds0.0.1) entered disabled state
Dec 29 14:14:42 RT-AX86U-AC30 kernel: br0: port 10(wds0.0.1.0) entered disabled state
Dec 29 14:14:42 RT-AX86U-AC30 kernel: br1: port 9(wds0.0.1.501) entered disabled state
Dec 29 14:14:42 RT-AX86U-AC30 kernel: [0;33;41m[ERROR vlan] vlanIoctl ,657: Failed to delete VLAN device wds0.0.1.501[0m
Dec 29 14:14:42 RT-AX86U-AC30 kernel: [0;33;41m[ERROR vlan] vlanIoctl ,657: Failed to delete VLAN device wds0.0.1.0[0m
Dec 29 14:14:51 RT-AX86U-AC30 kernel: CONSOLE: 077781.957 wl1: wlc_ampdu_recv_addba_resp: 54:60:09:7c:93:9e: Failed. status 37 wsize 16 policy
It's out of necessity, not by choice. Asus has been working on that model's GPL for almost two weeks now, and I didn't want to delay any longer just for that model. Beside, those components are still compatible with the newer GPL code in use, and didn't require any special kludge or separate code branching.


I just updated to beta 3 after having run on the latest 386 stock firmware on the AX88U. I had run beta 2 in the past with no issues. Unfortunately, this time, I lost all access to the internet. I rebooted the router, but no joy. Then I rolled back to stock and was ok with internet access again.

Any ideas what could have happened? The router showed internet access was good. All devices, however were blocked. It's possible it was a 5 band issue, since all clients were on that band at the time.

I can try again in the AM, but if anyone has any ideas, that would be great.
 
All Updated to Beta 3 Working Great Thank You :)
 
Updated to the latest github commit. Running great on both AX88U and AC86U with AiMesh.
The only thing I found was skynet does not run.

Router Model;
Skynet Version; (01/12/2020) (358a0e65e85afa8425897a993eb84b8c)
iptables v1.4.15 - (eth0 @ 192.168.1.1)
ipset v7.6, protocol version: 7
IP Address;
FW Version; 386.1_beta3-g1b79675d07 (Dec 28 2020) (4.1.51)
Install Dir; /tmp/mnt/sda1/skynet (50.6G / 56.2G Space Available)

/jffs/scripts/firewall: line 1: arithmetic syntax error
admin@RT-AX88U-5918:/tmp/home/root#
 
And what's on that line?

Just the #!/bin/sh line.

#!/bin/sh
#############################################################################################################
# #
# ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^u^w ^v^h ^v^h ^u^w ^v^h ^v^h ^u^w ^v^h ^v^h>
# ^v^h ^v^h ^u^t ^u^p ^u^p ^u^p ^u^p ^u^} ^v^h ^v^h ^u^q ^v^h ^v^h ^u^t ^u^} ^u^z >
# ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^u^w ^v^h ^v^h ^v^h ^v^h ^v^h ^u^t ^u^} ^u^z>
# ^u^z ^u^p ^u^p ^u^p ^u^p ^v^h ^v^h ^u^q ^v^h ^v^h ^u^t ^u^p ^v^h ^v^h ^u^w ^u^>
# ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^u^q ^v^h ^v^h ^u^q ^v^h ^v^h ^u^w ^v^h ^>
# ^u^z ^u^p ^u^p ^u^p ^u^p ^u^p ^u^p ^u^} ^u^z ^u^p ^u^} ^u^z ^u^p ^u^} ^u^z ^>
# #
# Router Firewall And Security Enhancements #
# By Adamm - https://github.com/Adamm00/IPSet_ASUS #
# 01/12/2020 - v7.2.3 #
#############################################################################################################
 
Just the #!/bin/sh line.

#!/bin/sh
#############################################################################################################
# #
# ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^u^w ^v^h ^v^h ^u^w ^v^h ^v^h ^u^w ^v^h ^v^h>
# ^v^h ^v^h ^u^t ^u^p ^u^p ^u^p ^u^p ^u^} ^v^h ^v^h ^u^q ^v^h ^v^h ^u^t ^u^} ^u^z >
# ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^u^w ^v^h ^v^h ^v^h ^v^h ^v^h ^u^t ^u^} ^u^z>
# ^u^z ^u^p ^u^p ^u^p ^u^p ^v^h ^v^h ^u^q ^v^h ^v^h ^u^t ^u^p ^v^h ^v^h ^u^w ^u^>
# ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^v^h ^u^q ^v^h ^v^h ^u^q ^v^h ^v^h ^u^w ^v^h ^>
# ^u^z ^u^p ^u^p ^u^p ^u^p ^u^p ^u^p ^u^} ^u^z ^u^p ^u^} ^u^z ^u^p ^u^} ^u^z ^>
# #
# Router Firewall And Security Enhancements #
# By Adamm - https://github.com/Adamm00/IPSet_ASUS #
# 01/12/2020 - v7.2.3 #
#############################################################################################################

Maybe this line. Since it does not display the model.


Extended_DNSStats() {
case "$1" in
1)
if [ "$lookupcountry" = "enabled" ]; then
country="($(curl -fsL --retry 3 --connect-timeout 3 -A "ASUSWRT-Merlin $model v$(nvram get buildno)_$(nvram get extendno) / $(tr -cd 0-9 </dev/urandom | head -c 20)" "https://api.db-ip.com/v2/free/${statdata}/countryCode/"))"
if [ -z "$country" ]; then country="*"; fi
fi

Router Model;
Skynet Version; (01/12/2020) (358a0e65e85afa8425897a993eb84b8c)
 
Unfortunately the issue with the LE certificate still hasn't been resolved with Beta3 on my RT-AX86U.
After the upgrade I formatted the jffs partition and factory reset my router. The very first thing I did after reboot was to enable DDNS, filled in my domain name and requested a LE certificate.

According to syslog everything went ok:
Dec 29 06:33:41 kernel: [Tue Dec 29 06:33:41 UTC 2020]
Dec 29 06:33:41 kernel: Removing DNS records.
Dec 29 06:33:41 kernel: [Tue Dec 29 06:33:41 UTC 2020] It seems that your api file doesn't define dns_asusapi_rm
Dec 29 06:33:41 kernel: [Tue Dec 29 06:33:41 UTC 2020]
Dec 29 06:33:41 kernel: Verify finished, start to sign.
Dec 29 06:33:42 kernel: [Tue Dec 29 06:33:41 UTC 2020]
Dec 29 06:33:42 kernel: Lets finalize the order, Le_OrderFinalize: https://acme-v02.api.letsencrypt.org/acme/finalize/107733821/7002973417
Dec 29 06:33:43 kernel: [Tue Dec 29 06:33:43 UTC 2020]
Dec 29 06:33:43 kernel: Download cert, Le_LinkCert: https://acme-v02.api.letsencrypt.org/acme/cert/046cb1718db4d6e53dae89d84f837604357b
Dec 29 06:33:44 kernel: [Tue Dec 29 06:33:44 UTC 2020]
Dec 29 06:33:44 kernel: Cert success.
Dec 29 06:33:44 kernel: cat: write error: Invalid argument
Dec 29 06:33:44 kernel: [Tue Dec 29 06:33:44 UTC 2020]
Dec 29 06:33:44 kernel: Your cert is in /jffs/.le/****************.asuscomm.com/**************.asuscomm.com.cer
Dec 29 06:33:44 kernel: [Tue Dec 29 06:33:44 UTC 2020]
Dec 29 06:33:44 kernel: Your cert key is in /jffs/.le/**************.asuscomm.com/***************.asuscomm.com.key
Dec 29 06:33:44 kernel: [Tue Dec 29 06:33:44 UTC 2020]
Dec 29 06:33:44 kernel: The intermediate CA cert is in /jffs/.le/**********.asuscomm.com/ca.cer
Dec 29 06:33:44 kernel: [Tue Dec 29 06:33:44 UTC 2020]
Dec 29 06:33:44 kernel: And the full chain certs is there: /jffs/.le/************.asuscomm.com/fullchain.cer
Dec 29 06:33:44 kernel: [Tue Dec 29 06:33:44 UTC 2020]
Dec 29 06:33:44 kernel: Installing key to:/jffs/.le/************.asuscomm.com/domain.key
Dec 29 06:33:44 kernel: [Tue Dec 29 06:33:44 UTC 2020]
Dec 29 06:33:44 kernel: Installing full chain to:/jffs/.le/***********.asuscomm.com/fullchain.pem
Dec 29 05:34:00 rc_service: service 7634:notify_rc restart_letsencrypt
Dec 29 06:34:01 kernel: [Tue Dec 29 06:34:01 UTC 2020]
Dec 29 06:34:01 kernel: Domains not changed.
Dec 29 06:34:01 kernel: [Tue Dec 29 06:34:01 UTC 2020]
Dec 29 06:34:01 kernel: Skip, Next renewal time is: Sat Feb 27 05:33:44 UTC 2021
Dec 29 06:34:01 kernel: [Tue Dec 29 06:34:01 UTC 2020]
Dec 29 06:34:01 kernel: Add '--force' to force to renew.

But even after several reboots of my router, the status on the GUI remains in "authorizing" state on the WAN -> DDNS tab. Exactly the same behavior as with the previous builds.
 
Last edited:
  • Like
Reactions: GDT
386.1 Beta 3 is now available.
Note that the RT-AX86U build is a Frankenbuild containing pieces from four different releases...

Changes since beta 2:

Code:
94adc38000 build: remove exception that disabled Ookla speedtest on RT-AX56U/RT-AX58U


Not sure if it's just the dirty flash on my RT-AX58U from Beta 2 but I don't see the SpeedTest tab in Adaptive QoS. If I go directly to the AdaptiveQoS_InternetSpeed.asp URL, I can use it now but I need to type the URL to get to it,

Omi8aFM.png
 
What are the differences/changes in the ASUS GPL code from Beta 2 to 3? Is there a such change log? I can see all Merlin's changes/updates through his own provided change log, but nothing specific from ASUS between GPL code updates. Do ASUS even provide that to you Merlin, e.g. anything specific to AiMesh? As I am aware that is out of your control.

I have been running Beta 3 across my setup now for around 5 hours, after a total reset and manual build, and all is good.. Nothing to report as yet. Thanks Merlin again.
 
Last edited:
Not that this is part of Merlin's portion, but with Beta 3 (386.41350), as soon as I enabled a guest network on my 68u aimesh nodes (ie. sync to all), which has no intranet access, then I see massive packet loss on devices connected to the node. Simply change to "router only" and no packet loss. Wish asus would be able to reproduce this.
 
Unfortunately the issue with the LE certificate still hasn't been resolved with Beta3 on my RT-AX86U.

The RT-AX86U is running older components, as I didn't have a GPL update in time for this model to be included in beta 3.

They didn't have any ETA yesterday about the RT-AX86U GPL, so I decided to just go ahead and release with what I had for now. And a few hours after releasing Beta 3 with what I had, the RT-AX86U 386_41491 GPL shows up on my FTP server. Eh.

I'll have to see if it's compatible with the 41350 GPL code I use for other models. If it is, I might issue a separate test build for the RT-AX86U. Too late tonight to start looking into that, will have to wait tomorrow.

What are the differences/changes in the ASUS GPL code from Beta 2 to 3? Is there a such change log

There are no changelog. All I get is a 1.7 GB archive containing source code, without any documentation.
 
Last edited:
The RT-AX86U is running older components, as I didn't have a GPL update in time for this model to be included in beta 3.

They didn't have any ETA yesterday about the RT-AX86U GPL, so I decided to just go ahead and release with what I had for now. And a few hours after releasing Beta 3 with what I had, the RT-AX86U 386_41491 GPL shows up on my FTP server. Eh.

I'll have to see if it's compatible with the 41350 GPL code I use for other models. If it is, I might issue a separate test build for the RT-AX86U. Too late tonight to start looking into that, will have to wait tomorrow.



There are no changelog. All I get is a 1.7 GB archive containing source code, without any documentation.
Got ya thanks for the response on that
 
The RT-AX86U is running older components, as I didn't have a GPL update in time for this model to be included in beta 3.

They didn't have any ETA yesterday about the RT-AX86U GPL, so I decided to just go ahead and release with what I had for now. And a few hours after releasing Beta 3 with what I had, the RT-AX86U 386_41491 GPL shows up on my FTP server. Eh.

I'll have to see if it's compatible with the 41350 GPL code I use for other models. If it is, I might issue a separate test build for the RT-AX86U. Too late tonight to start looking into that, will have to wait tomorrow.



There are no changelog. All I get is a 1.7 GB archive containing source code, without any documentation.

Yes thanks Eric. Just wondering whether anyone including yourself can replicate issues im having with OPENVPN Server on the AX-86U.
 
Just loaded beta3 and working just fine. Vpn-client and vpn-server working fine.

a1d0a960e4 openvpn: use iproute2 instead of netlink for all platforms, seems working fine

Code:
Table 254
default via 158.174.112.1 dev eth0
Table 111
0.0.0.0/1 via 10.128.0.1 dev tun11
default via 10.128.0.1 dev tun11
128.0.0.0/1 via 10.128.0.1 dev tun11
Table 112
Table 113
0.0.0.0/1 via 10.129.0.1 dev tun13
default via 10.129.0.1 dev tun13
128.0.0.0/1 via 10.129.0.1 dev tun13
Table 114
Table 115

Thank you for new build!
 
I just updated to beta 3 after having run on the latest 386 stock firmware on the AX88U. I had run beta 2 in the past with no issues. Unfortunately, this time, I lost all access to the internet. I rebooted the router, but no joy. Then I rolled back to stock and was ok with internet access again.

Any ideas what could have happened? The router showed internet access was good. All devices, however were blocked. It's possible it was a 5 band issue, since all clients were on that band at the time.

I can try again in the AM, but if anyone has any ideas, that would be great.
Had a similar experience on beta 2 (updated from beta 1) - if I recall the versions correctly. Saw Let's Encrypt successfully downloading and installing files on JFFS (according to logs)... But the certification still was in "Authorizing" so I did a reboot. Lost internet everywhere (including cable). Restored my JFFS partion and regained access. No issues with beta 2 to beta 3 upgrades. Still no certificate though. Wonder what it will do next time it downloads though...
 
  • Like
Reactions: GDT
The issue with the LE certificate still hasn't been resolved with Beta3 on my RT-AX88U.
After the upgrade I formatted the jffs partition and factory reset my router.
 
Still having the same issues with my VPN clients on Beta 3 as I was having with Alpha3 and Beta1. When I enable the VPN client to purevpn with 1 client in the policy list, it works fine. As soon as I add another ip to the policy list, my whole WAN connection breaks, no internet across all devices.

The only fix is rebooting the router. More people recognize this issue who are also using policy lists?

Force Internet traffic through tunnel: Policy rules
2 entries: Laptop + Desktop with their respective IP's, Iface set to VPN.
 
Still having the same issues with my VPN clients on Beta 3 as I was having with Alpha3 and Beta1. When I enable the VPN client to purevpn with 1 client in the policy list, it works fine. As soon as I add another ip to the policy list, my whole WAN connection breaks, no internet across all devices.

The only fix is rebooting the router. More people recognize this issue who are also using policy lists?

Force Internet traffic through tunnel: Policy rules
2 entries: Laptop + Desktop with their respective IP's, Iface set to VPN.
Can you attach a screen shot on VPN routing page?
 
Hi all and thank you RMerlin for your great work.

I own an Asus RT-AC86U and I use the Asus Merlin 386.1 beta 2. All is working fine but the Traffic Analyzer (both Traffic Monitor and Statistics) and the QOS Bandwidth Monitor.

The QOS Bandwidth Monitor shows only a few Kb/s when the real usage of the bandwidth is over 50 Mb/s. The Traffic Monitor starts to show traffic but, after a while, it goes completely out of scale (screenshot below):

View attachment 28808

Another example, in the QOS Classification I correctly see a 24,39 GB of "Video and Audio Streaming" traffic (screenshot below):

View attachment 28809

but in Traffic Analyzer Statistics I only have a few hundreds of MB of traffic in the same time range (screenshot below):

View attachment 28810

I state that I have also performed a factory reset and configured the router from scratch, but nothing has changed.

Is there someone who can help me to solve this problem?

Thank you.

Bye.

Hi Merlin and hi all,
I installed the 386.1 beta 3 on my RT-AC86U, but I still have the problem above.

Is it a bug or is it just a problem with my router? How can I solve it?

Thank you very much.

Bye.
 
Status
Not open for further replies.

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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