[Release] Asuswrt-Merlin 384.15 (and 384.13_4) are now available

Status
Not open for further replies.

Jacob

Occasional Visitor
Hello,

After upgrade to 384.15 - VPN Shows connected , but no IPs present and VPN IPs are not on VPN - regular provider IP (kill switch not working) probably it thinks its on VPN

Will revert to 384.14 now and report


View attachment 21302
Similar thing happening here. after rebooting i do get an ip from vpn provider but there is no connection. i have to turn it off and then on for the vpn tunnel to work.
 

GHammer

Senior Member
Hey,
I'm currently at my AX88U 384.15 going all the way dirty from 384.15_alpha1...

I'm using Native IPV6 with DHCP-PD (either stateless or stateful) and even though IPV6 works good for all my clients,
The router has NO IPV6 connectivity.... any attempts to ping6 from ssh or the network tools timeout... I cannot update ep over amtm... it also timeout....
Once I disable IPV6 all the issues disappear and amtm works like a charm..

Could someone with native IPV6 could ssh into the router and try to ping6 google.com or even skip the DNS and directly ping6 2001:4860:4860::8888

BR,
Ankh
Code:
ASUSWRT-Merlin RT-AC86U 384.15_0 Sat Feb  8 18:41:28 UTC 2020
[email protected]:/tmp/home/root# ping6 2001:4860:4860::8888
PING 2001:4860:4860::8888 (2001:4860:4860::8888): 56 data bytes
64 bytes from 2001:4860:4860::8888: seq=0 ttl=55 time=16.786 ms
64 bytes from 2001:4860:4860::8888: seq=1 ttl=55 time=23.532 ms
64 bytes from 2001:4860:4860::8888: seq=2 ttl=55 time=18.181 ms
64 bytes from 2001:4860:4860::8888: seq=3 ttl=55 time=16.628 ms
64 bytes from 2001:4860:4860::8888: seq=4 ttl=55 time=23.993 ms
^C
--- 2001:4860:4860::8888 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 16.628/19.824/23.993 ms
 

killeriq

Regular Contributor
Similar thing happening here. after rebooting i do get an ip from vpn provider but there is no connection. i have to turn it off and then on for the vpn tunnel to work.

"PublicIP" VPN profile is giving issues - before upgrade was fine...
Even after "factory reset" still the same :(

"NAT" profile from VPN provider works fine...

EDIT:Cant add log.txt file and if i use code get notification about banned...
 

Butterfly Bones

Very Senior Member
"PublicIP" VPN profile is giving issues - before upgrade was fine...
Even after "factory reset" still the same :(

"NAT" profile from VPN provider works fine...

EDIT:Cant add log.txt file and if i use code get notification about banned...
Add the log to www.pastebin.com and provide a link to it here. That is the wonderful [email protected]#$%& Cloudflare SPAM protection kicking in. (grumble, grumble, grumble ;) )
 

PDinDetroit

Regular Contributor
Running 384.15 on AX88U (Router) and 2 AC86Us (Access Points). They were all on 384.15 Beta 1 prior to upgrade, did dirty flash (removed USB from AX88U though). Running AMTM, Diversion, and Skynet. All have been up for 18 hours and running just fine including all WiFi devices.

My work laptop has 2 physical network connections: 1 onboard and 1 in the docking station. I run Virtual Machines for various clients using the 1 in the dock and using Bridged Connections, replicating physical connection state. Each VM is getting its own IP apart from what my laptop gets. Running exactly as expected.

Thank you Eric and all that helped make this a great build!
 

killeriq

Regular Contributor
"PublicIP" VPN profile is giving issues - before upgrade was fine...
Even after "factory reset" still the same :(

"NAT" profile from VPN provider works fine...

EDIT:Cant add log.txt file and if i use code get notification about banned...

Here is the log: https://paste2.org/a3N82Xxe
Actually i did try other server, was able to connect, then after 2h tried the 1st one and works also...

But new problem occured, getting tons of those errors in log:
Code:
Feb 10 21:05:13 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:13 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:13 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:13 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:13 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:13 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:13 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:18 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:18 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:20 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:20 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:20 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:23 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:23 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:23 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:23 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:23 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:25 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:25 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:25 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:25 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:26 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:26 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:26 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:27 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:29 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:29 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:30 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:30 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:32 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:32 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:32 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:32 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:32 kernel: protocol 0800 is buggy, dev eth0
Feb 10 21:05:32 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:32 kernel: protocol 0800 is buggy, dev br0
Feb 10 21:05:32 kernel: protocol 0800 is buggy, dev br0
 

PeterDNA

Occasional Visitor
ever since updating to 384.15 from 384.14 all runs fine except I do have one error event showing up once every few hours.

Feb 10 11:51:08 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
 

delaveganz

New Around Here
Dirty upgrade over 384.14_2 on all my Asus devices: RT-AC86U Router + RT-AC86U AIMesh node + RT-AC68U Media Bridge

No issues upgrading. All running fine at the moment.
 

orion44

Occasional Visitor
No issues upgrading RT-AC5300 to 384.15 but I'm seeing syslog flooded with these errors now:
Code:
Feb 10 10:47:28 dnsmasq-script[1256]: connect error: No such file or directory
Feb 10 10:47:28 dnsmasq-script[1256]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.

Do I need to adjust some DNS settings to make this error go away – or is it safe to ignore?
 

RMerlin

Asuswrt-Merlin dev
No issues upgrading RT-AC5300 to 384.15 but I'm seeing syslog flooded with these errors now:
Code:
Feb 10 10:47:28 dnsmasq-script[1256]: connect error: No such file or directory
Feb 10 10:47:28 dnsmasq-script[1256]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.

Do I need to adjust some DNS settings to make this error go away – or is it safe to ignore?

This message is related to AiMesh. No idea what it's about, AiMesh is outside of my control.
 

doczenith1

Very Senior Member
Been playing around with OpenVPN. Seems to work great. Currently using OpenVPN for Android (beta) with OpenVPN 3 Core active. Have removed fallbacks to 128bit encryptions. Works fine it seems.
But if I have forgotten it on and return home the VPN fails when WiFi connects... I can't seem to find a good solution to either make sure it automatically does not use VPN when connected to home WiFi or make the VPN stop shutting down internet access.
Anyone messing around with these things and have a solution? Tasker?

In the vpn profile in the openvpn app on your Android device go to the advanced tab. On that tab check the box for "Allow floating server". I was having the same issue of not being able to connect when I'm on my wifi and this fixed it.
 
Last edited:

orion44

Occasional Visitor
This message is related to AiMesh. No idea what it's about, AiMesh is outside of my control.
Thanks for the quick reply. I don't use AiMesh or have any related features enabled, so I'll just ignore the error for now.
 
Last edited:

Smokey613

Very Senior Member
Hey,
I'm currently at my AX88U 384.15 going all the way dirty from 384.15_alpha1...

I'm using Native IPV6 with DHCP-PD (either stateless or stateful) and even though IPV6 works good for all my clients,
The router has NO IPV6 connectivity.... any attempts to ping6 from ssh or the network tools timeout... I cannot update ep over amtm... it also timeout....
Once I disable IPV6 all the issues disappear and amtm works like a charm..

Could someone with native IPV6 could ssh into the router and try to ping6 google.com or even skip the DNS and directly ping6 2001:4860:4860::8888

BR,
Ankh

Works fine on mine....

F1D7125B-6F27-4302-A286-C33075D88578.jpeg
 

DarnellG

Occasional Visitor
Did a dirty upgrade of my AX88U from the .15 beta to the release. Still seeing these errors that showed up with the .15 Alpha. Would a reset stop these? What exactly is causing this?

Feb 9 07:51:11 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set

I'm getting the same error too after a dirty upgrade.

kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
 

Asad Ali

Very Senior Member
@RMerlin Advanced apologies for a little off-topic question but I feel like it didn't justify a new thread of its own.

In the Syslog, I see a line that shows the total PPPoE connected time since the last disconnect.

Something like this :
"pppd: Total connected time Xxx minutes "
I want to know is there any way I can fetch that total time duration from within a script? Like if I want to email myself with that information every time my PPPoE link goes down.

So is there any NVRAM variable where that information is stored or my only option is to grep it out from the Syslog?
 

swejuggalo

Regular Contributor
In the vpn profile in the openvpn app on your Android device go to the advanced tab. On that tab check the box for "Allow floating server". I was having the same issue of not being able to connect when I'm on my wifi and this fixed it.
Have tried that too. But I'll try that app and setting again.
Tested with the latest firmware? It's a AX88 in my case. Never tried this before so I have no way to tell if it is a recent issue in my current phone/router combo.

Tried a 3rd app... https://play.google.com/store/apps/details?id=it.colucciweb.vpnclientpro .
This works instantly. Odd.
 
Last edited:

XIII

Very Senior Member
When I woke up this morning about 50% of the devices in my network were no longer connected to my AC86U.
The same happened in the weekend with the beta. I then thought it was a fluke, but now I'm not so sure anymore.

I power cycled some of those devices, but none of them did get back online.

A (remote) reboot of the router did not help either; I can't connect to the router any longer (SSH + OpenVPN both not working).

(To be continued later today)
 

SheikhSheikha

Senior Member
I have noticed that on my RT-AC5300's the NAT Passthrough for L2TP and IPSec no longer work with 384.15.
 
Status
Not open for further replies.

Similar threads

Sign Up For SNBForums Daily Digest

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