1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

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

Discussion in 'Asuswrt-Merlin' started by RMerlin, Feb 8, 2020.

Thread Status:
Not open for further replies.
  1. Jacob

    Jacob Occasional Visitor

    Joined:
    Feb 8, 2020
    Messages:
    13
    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.
     
  2. GHammer

    GHammer Senior Member

    Joined:
    Jan 25, 2015
    Messages:
    278
    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
    
     
    ankhazam and L&LD like this.
  3. killeriq

    killeriq Regular Contributor

    Joined:
    Jul 22, 2017
    Messages:
    55
    "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...
     
  4. Butterfly Bones

    Butterfly Bones Very Senior Member

    Joined:
    Apr 10, 2017
    Messages:
    1,342
    Location:
    USA
    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 ;) )
     
  5. bigsinky1966

    bigsinky1966 New Around Here

    Joined:
    Jan 14, 2020
    Messages:
    7
    Running 384.15 on AX88U. Smooth as silk install yetserday and rock solid performance so far.
     
    Quoc Huynh, Vexira, kernol and 2 others like this.
  6. PDinDetroit

    PDinDetroit Regular Contributor

    Joined:
    Dec 14, 2017
    Messages:
    75
    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!
     
  7. netware5

    netware5 Very Senior Member

    Joined:
    Mar 9, 2013
    Messages:
    540
    Location:
    Bulgaria
  8. killeriq

    killeriq Regular Contributor

    Joined:
    Jul 22, 2017
    Messages:
    55
    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
     
    Vexira likes this.
  9. PeterDNA

    PeterDNA New Around Here

    Joined:
    Mar 13, 2018
    Messages:
    8
    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
     
    jhonzah and neil0311 like this.
  10. delaveganz

    delaveganz New Around Here

    Joined:
    Oct 1, 2019
    Messages:
    2
    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.
     
  11. orion44

    orion44 Occasional Visitor

    Joined:
    Jan 4, 2017
    Messages:
    44
    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?
     
  12. RMerlin

    RMerlin Super Moderator

    Joined:
    Apr 14, 2012
    Messages:
    33,288
    Location:
    Canada
    This message is related to AiMesh. No idea what it's about, AiMesh is outside of my control.
     
    StefanP and Vexira like this.
  13. doczenith1

    doczenith1 Very Senior Member

    Joined:
    Sep 19, 2014
    Messages:
    691
    Location:
    MI
    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: Feb 10, 2020
  14. orion44

    orion44 Occasional Visitor

    Joined:
    Jan 4, 2017
    Messages:
    44
    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: Feb 11, 2020
  15. Smokey613

    Smokey613 Senior Member

    Joined:
    Feb 21, 2019
    Messages:
    288
    Location:
    Redneck Riviera, USA
    Works fine on mine....

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

    DarnellG Occasional Visitor

    Joined:
    Jan 15, 2020
    Messages:
    36
    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
     
    neil0311 likes this.
  17. Asad Ali

    Asad Ali Very Senior Member

    Joined:
    May 25, 2017
    Messages:
    802
    Location:
    Pakistan
    @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?
     
  18. swejuggalo

    swejuggalo Regular Contributor

    Joined:
    Feb 5, 2019
    Messages:
    70
    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: Feb 11, 2020
  19. XIII

    XIII Very Senior Member

    Joined:
    Feb 27, 2014
    Messages:
    1,154
    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)
     
  20. SheikhSheikha

    SheikhSheikha Regular Contributor

    Joined:
    Mar 20, 2019
    Messages:
    159
    Location:
    The Desert
    I have noticed that on my RT-AC5300's the NAT Passthrough for L2TP and IPSec no longer work with 384.15.
     
Thread Status:
Not open for further replies.