What's new

[Preview 384/NG] Asuswrt-Merlin 384.5 early test builds

  • 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!

RMerlin

Asuswrt-Merlin dev
Preview builds of 384.5 are now available in the Test Builds folder. These builds will be occasionally refreshed.

No support will be provided for these.
 
Merlin,

Just a few reports, likely you know, but us late night owls like looking at the new goodness.

  1. VPN Server page OpenVpn "Invalid Character" -- Issue persists after default
  2. VPN Server page IPSec Vpn "Invalid Character" -- Issue persists after default
  3. Asus DDNS "Un authorized error ... " -- Fixed by default of fw
 
Last edited:
Under Administration=> feedback should it be there in 384.5-alpha1 ?
 
Unsupported cipher 256-GCM ?
Apr 1 17:15:09 ovpn-server1[2631]: event_wait : Interrupted system call (code=4)
Apr 1 17:15:14 ovpn-server1[2761]: Unsupported cipher in --ncp-ciphers: 256-GCM
Apr 1 17:15:14 ovpn-server1[2761]: Options error: NCP cipher list contains unsupported ciphers.
Apr 1 17:15:14 ovpn-server1[2761]: Use --help for more information.

Sorry, it's AES-256-GCM :p
 
Last edited:
System Log - Active Connections
Problem with Refresh -> No Refresh (no list of tracked connections)
 
Probable bug. If you do:
Network Tools - Network Analysis -> Diagnose
and then
System Log - Active Connections -> Refresh
Result:

refresh.jpg


... confusion between the two functions
 
GitHub isn’t showing many commits, does this include the newer GPL?

I need to fix a build issue on the RT-AC3200 within the past few commits before I can push the fixed commits to Github (you cannot modify a commit after you have pushed it to Github, at least not without breaking a lot of things).
 
Under Administration=> feedback should it be there in 384.5-alpha1 ?

No. Asus changed some capabilities definitions in rc/init.c with that GPL, I haven't adjusted to those changes yet.
 
Getting this panic on AC86U...

Apr 1 18:29:49 rc_service: watchdog 826:notify_rc stop_aae
Apr 1 18:29:49 NAT_Tunnel: AAE Service is stopped
Apr 1 18:29:49 rc_service: watchdog 826:notify_rc start_mastiff
Apr 1 18:29:49 rc_service: waitting "stop_aae" via watchdog ...
Apr 1 18:29:49 NAT_Tunnel: AAE Service is stopped
Apr 1 18:29:50 NAT_Tunnel: AAE Service is stopped
Apr 1 18:29:50 AAE: AAE Service is started
Apr 1 18:29:50 Mastiff: init
Apr 1 18:30:25 kernel: pgd = ffffffc008d78000
Apr 1 18:30:25 kernel: [007d2242] *pgd=00000000150db003, *pud=00000000150db003, *pmd=0000000000000000
Apr 1 18:30:25 kernel: CPU: 0 PID: 6839 Comm: mastiff Tainted: P O 4.1.27 #2
Apr 1 18:30:25 kernel: Hardware name: Broadcom-v8A (DT)
Apr 1 18:30:25 kernel: task: ffffffc019330b80 ti: ffffffc01513c000 task.ti: ffffffc01513c000
Apr 1 18:30:25 kernel: PC is at 0xf6c80218
Apr 1 18:30:25 kernel: LR is at 0x0
Apr 1 18:30:25 kernel: pc : [<00000000f6c80218>] lr : [<0000000000000000>] pstate: 60010010
Apr 1 18:30:25 kernel: sp : 00000000ffb4cfe0
Apr 1 18:30:25 kernel: x12: 00000000ffb4d004
Apr 1 18:30:25 kernel: x11: 00000000f6d4d7a8 x10: 00000000f6d4d7d8
Apr 1 18:30:25 kernel: x9 : 00000000007d2236 x8 : 0000000000000030
Apr 1 18:30:25 kernel: x7 : 0000000000000000 x6 : 000000000045c2a8
Apr 1 18:30:25 kernel: x5 : 0000000000000050 x4 : 000000000045c258
Apr 1 18:30:25 kernel: x3 : 00000000f6d4d800 x2 : 0000000000000031
Apr 1 18:30:25 kernel: x1 : 0000000000000000 x0 : 0000000000000000
Apr 1 18:30:50 rc_service: watchdog 826:notify_rc stop_aae
Apr 1 18:30:50 NAT_Tunnel: AAE Service is stopped
Apr 1 18:30:50 NAT_Tunnel: AAE Service is stopped
Apr 1 18:30:50 rc_service: watchdog 826:notify_rc start_mastiff
Apr 1 18:30:50 NAT_Tunnel: AAE Service is stopped
Apr 1 18:30:50 AAE: AAE Service is started
Apr 1 18:30:50 Mastiff: init
Apr 1 18:31:25 kernel: pgd = ffffffc014ebc000
Apr 1 18:31:25 kernel: [007d2242] *pgd=000000000aa34003, *pud=000000000aa34003, *pmd=0000000000000000
Apr 1 18:31:25 kernel: CPU: 0 PID: 6895 Comm: mastiff Tainted: P O 4.1.27 #2
Apr 1 18:31:25 kernel: Hardware name: Broadcom-v8A (DT)
Apr 1 18:31:25 kernel: task: ffffffc0192d9440 ti: ffffffc01513c000 task.ti: ffffffc01513c000
Apr 1 18:31:25 kernel: PC is at 0xf6e45218
Apr 1 18:31:25 kernel: LR is at 0x0
Apr 1 18:31:25 kernel: pc : [<00000000f6e45218>] lr : [<0000000000000000>] pstate: 60010010
Apr 1 18:31:25 kernel: sp : 00000000ff8b3690
Apr 1 18:31:26 kernel: x12: 00000000ff8b36b4
Apr 1 18:31:26 kernel: x11: 00000000f6f127a8 x10: 00000000f6f127d8
Apr 1 18:31:26 kernel: x9 : 00000000007d2236 x8 : 0000000000000038
Apr 1 18:31:26 kernel: x7 : 00000000003aa5c8 x6 : 00000000003aa080
Apr 1 18:31:26 kernel: x5 : 0000000000000050 x4 : 00000000003aa030
Apr 1 18:31:26 kernel: x3 : 00000000f6f12800 x2 : 00000000f6f127b8
Apr 1 18:31:26 kernel: x1 : 0000000000000000 x0 : 0000000000000000
Apr 1 18:31:50 rc_service: watchdog 826:notify_rc stop_aae
Apr 1 18:31:50 NAT_Tunnel: AAE Service is stopped
Apr 1 18:31:50 NAT_Tunnel: AAE Service is stopped
Apr 1 18:31:50 rc_service: watchdog 826:notify_rc start_mastiff
Apr 1 18:31:50 NAT_Tunnel: AAE Service is stopped
Apr 1 18:31:50 AAE: AAE Service is started
Apr 1 18:31:50 Mastiff: init
Apr 1 18:32:27 Mastiff: Got SIGABRT
 
after updating.jpg after updating 2.jpg
after updating.jpg
after updating 2.jpg
Preview builds of 384.5 are now available in the Test Builds folder. These builds will be occasionally refreshed.

No support will be provided for these.

Okay So I just update my RT-AC5300 to this branch from 384.4_2 and I would like to report I am now seeing an unauthorized Registration Request Message for my DDNS it was prior registered with Lets Encrypt on previous build and on the main page has an yellow exclamation point over it now.
mXutAS
jPyyc7
 
I am now seeing an unauthorized Registration Request Message for my DDNS it was prior registered with Lets Encrypt on previous build and on the main page has an yellow exclamation point over it now.

For me I was able to fix it by defaulting the build and rebuilding from scratch. I didn't mind blowing away the data as I had a bunch of things screwy in the 384 builds and I defaulted more than a few times. I am not suggesting you do this as it may be an easy fix on the next build, but for me I went all in. :cool:
 
also IPV6 for some odd reason stopped working I tried turning it off and back on and it will not receive address like it use to.
 
So i did a initialize reset i will see if this will fix it for me
 
Okay just reporting that if anyone experiences issues i have experienced the solution is to do an initialize restore. Loading saved settings after will not work. You have to manually redo everything.
 
I can't log into the router using the asus Router mobile app on my RT-AC5300.
Anyone else having problems?
 
I can't log into the router using the asus Router mobile app on my RT-AC5300.
Anyone else having problems?
Okay you may have to initialize yours under factory restore. I had to do that with mine to get nearly half my stuff to function right on my RT-AC5300. It was as if I upgraded from 380 to 384, but I went from 384.4_2 to 384.5 alpha 1. You cannot use restore settings though so you have to input your settings back in manually, but trust me it is worth it. The Router will appreciate it.
 

Latest threads

Sign Up For SNBForums Daily Digest

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