[Release 384/NG] Asuswrt-Merlin 384.4 is now available

[XIII]

Upgraded from 384.4 Beta 3 to 384.4 final on my AC86U.

Everything seems fine (including keeping my custom SSL certificates), except IPsec VPN, which did not work in Beta 3 either (though it did work in an earlier beta).

 

[AndreiV]

Thanks Eric , AC3200 , flashed over the beta 3 . all looking good.

 

[predatorz]

Updated to 384.4 from 384.3 smoothly.

 

[Zentachi]

Updated to 384.4 from 384.3 yesterday.
Uptime 11 hours and no issues

 

[armsAC3100]

Since a Factory reset is suggested is there a recommended / easy way to capture current settings for easier application to new release?

I am currently operating on 380.69.2 and have many settings for static IP, VPN, etc

Al

 

[owiecc]

86U: upgraded from 384.3 ok. IPsec VPN server works ok.
DNLA still does not scan all of the files.
I had few DLNA crashes also:

Mar 17 10:04:17 kernel: minidlna[8071]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007
Mar 17 10:04:17 kernel: pgd = ffffffc0164ee000
Mar 17 10:04:17 kernel: [00000000] *pgd=0000000014005003, *pud=0000000014005003, *pmd=0000000011303003, *pte=0000000000000000
Mar 17 10:04:17 kernel: CPU: 1 PID: 8071 Comm: minidlna Tainted: P O 4.1.27 #2
Mar 17 10:04:17 kernel: Hardware name: Broadcom-v8A (DT)
Mar 17 10:04:17 kernel: task: ffffffc019378b40 ti: ffffffc005fd0000 task.ti: ffffffc005fd0000
Mar 17 10:04:17 kernel: PC is at 0xf74499a4
Mar 17 10:04:17 kernel: LR is at 0x0
Mar 17 10:04:17 kernel: pc : [<00000000f74499a4>] lr : [<0000000000000000>] pstate: 80070010
Mar 17 10:04:17 kernel: sp : 00000000f6e7f0e8
Mar 17 10:04:17 kernel: x12: 0000000000000001
Mar 17 10:04:17 kernel: x11: 00000000f65abd90 x10: 00000000f658c9f0
Mar 17 10:04:17 kernel: x9 : 0000000000000000 x8 : 00000000f6e81bd0
Mar 17 10:04:17 kernel: x7 : 00000000f658d5a0 x6 : 0000000000000000
Mar 17 10:04:17 kernel: x5 : 0000000000000000 x4 : 00000000f75c9ce0
Mar 17 10:04:17 kernel: x3 : 00000000f75c9ce0 x2 : 0000000000000400
Mar 17 10:04:17 kernel: x1 : 0000000000000000 x0 : 00000000f6e7f124

 

[Netbug]

installed 7 hours ago on rt-ac86u and all seems good, nothing abnormal looking in logs. Thanks RMerlin.

Just noticed in log, not got a clue what it means but thought i would post it, seems to do with QoS, i had QoS enabled yesterday but then disabled it yesterday but just spotted this.

Mar 17 10:32:16 kernel: ERR[update_qos_data_by_mac:3568] Failed to find udb entry by skb src-MAC!
Mar 17 10:32:16 kernel: ERR[update_qos_data_by_mac:3568] Failed to find udb entry by skb src-MAC!
Mar 17 10:32:16 kernel: ERR[update_qos_data_by_mac:3568] Failed to find udb entry by skb src-MAC!
Mar 17 10:35:10 kernel: ERR[update_qos_data_by_mac:3568] Failed to find udb entry by skb src-MAC!
Mar 17 10:35:10 kernel: ERR[update_qos_data_by_mac:3568] Failed to find udb entry by skb src-MAC!
Mar 17 10:35:10 kernel: ERR[update_qos_data_by_mac:3568] Failed to find udb entry by skb src-MAC!
Mar 17 10:35:10 kernel: ERR[update_qos_data_by_mac:3568] Failed to find udb entry by skb src-MAC!
Mar 17 10:35:14 kernel: ERR[update_qos_data_by_mac:3568] Failed to find udb entry by skb src-MAC!
Mar 17 10:35:14 kernel: ERR[update_qos_data_by_mac:3568] Failed to find udb entry by skb src-MAC!

 

[stambeccuccio]

Merlin 384.4 - Everything I use seems ok. Thank You so much for Your hard and tireless work really appreciated.
A real pity that AiMesh is not supported and above all we do not know if Merlin will ever support it

 

[Nurofen]

Merlin 384.4 Asus 87U.

Why this button ?

 

[skeal]

Sorry for this targeted message to you.

Can you humour me and see if your USB ports work?

On my hw rev A6 ac3100 and my hw rev A1 ac68 they don’t seem to be ever since the 384 branch was started both Merlin and stock firmware. Tried both a sandisk 2gig USB key and a wd mybook 4 tb drive.

Just trying to see if others see this before I report more fully. You happen to have the same hardware (though perhaps different hw rev) as me.

Yes both usb ports work. I rely on the usb 3 port for my installed scripts...

 

[skeal]

Since a Factory reset is suggested is there a recommended / easy way to capture current settings for easier application to new release?

I am currently operating on 380.69.2 and have many settings for static IP, VPN, etc

Al

I recommend not importing any settings with any utility. Take screen shots of your settings before you flash and then reset to defaults after the flash and setup from your screen shots.

 

[thelonelycoder]

I'm surprised that the modified version of entware-setup.sh does not follow the suggestions posted here:
https://www.snbforums.com/threads/t...tion-for-better-environment-management.39176/

I know the Entware merge was done practically overnight and without prior notice of any downstream parties.
But now would have been a good time to remove a major interrupter for all of us guided-install-script writers.
The modified entware-setup.sh also still removes any existing scripts and replaces them with its own.

 

[Grisu]

Merlin 384.4 Asus 87U.

Why this button ?

to clear just everything incl. jffs and logs.

 

[RMerlin]

Since a Factory reset is suggested is there a recommended / easy way to capture current settings for easier application to new release?

I am currently operating on 380.69.2 and have many settings for static IP, VPN, etc

Al

People usually go with screenshots of their settings.

 

[RMerlin]

I had few DLNA crashes also:

Could be corrupted files, that would also prevent the scanning from completing. Try isolating which specific file or folder is causing it to crash.

I'm surprised that the modified version of entware-setup.sh does not follow the suggestions posted here:

I would have needed time to better study how it works and how it interacts with Entware (I didn't write the original script), which I didn't. It happened too close to release time to ensure proper testing of any further changes.

 

[mokkurkalve]

When I updated from 380.x to 384.3 I did a full factory reset and configured everything anew by hand.
Now I updated from 384.3 to 384.4. Things seem to work OK, except one thing that changed. Firefox 59.0 just times out when trying to connect to webui. No way I can make Firefox connect any longer. On the other hand, Chromium connects OK, so I'm good. Just wondering if anybody else got problem with Firefox after upgrading from .3 to .4...?
I'm using https port 8443 for webui and my desktop OS is Arch Linux current. And of course I emptied browser cache before trying....

 

[lijiacheng51]

Asuswrt-Merlin 384.4 is now available for all supported models. The focus of this release was porting the last remaining models to the 384/NG code branch, and updating to the latest GPL available, bringing us back in sync with Asus's latest release.

The highlights of this release:

• Merged with GPL 384_20379 (with some binary components from 382_50010 and 384_20308 depending on models)
• Added support for the RT-AC5300 and RT-AC87U, completing the task of migrating models to the new 384/NG code branch. As a reminder, the RT-N66U and the original RT-AC66U will NOT be migrated to the 384 code base, and support for these two is going to be dropped.
• Added IPSEC server support to the RT-AC86U.
• Moved Entware to the new 3x-NG merged repository, and added 64bit Entware support to the RT-AC86U (user-configurable when running entware-setup)
• Changed Samba protocol support, now defaults to SMBv1 + SMBv2 support. This means SMB sharing will be a bit slower than with SMBv1, but more secure. The protocol settings now allow you to chose between SMBv1 (faster but not secure), SMBv2 (secure but not compatible with everything) and SMBv1 + SMBv2 (the new default, matches the behaviour of the old SMBv2 setting in previous releases). I personally recommend switching to SMBv2, unless you have embedded devices which do not support SMBv2 yet.
• The telnet server support has been removed, for security purposes. Please use SSH instead.
• Merlin NAT loopback was removed, as it was becoming increasingly problematic with the constant low-level changes to the firewall
• A few other fixes, please read the changelog for details

As a reminder, if you are migrating to a 384 firmware for the first time:

• Clear your browser cache or do a forced reload the first time you access the router under 384 (to refresh your cached CSS files)
• If coming from 380.xx, it's strongly recommended to do a factory default after flashing 384, and manually reconfiguring. Things might work correctly if you don't, but you might have to double check some of your previous settings, for instance OpenVPN's.

Also note that AiMesh is NOT supported, and there are currently no new information as to whether it will eventually be supported or not.

The focus will now be on issuing one final 380.70 release to bring closure to the 380 branch. This release should be fairly minor, bringing mostly a few bug fixes.

Please keep discussions in this thread to this specific release.


Downloads are here.
Changelog is here.

OpenVPN Error after my ac68u upgrade
log:
Mar 18 00:46:28 ovpn-client1[1652]: [LJCS] Inactivity timeout (--ping-restart), restarting
Mar 18 00:46:28 ovpn-client1[1652]: SIGUSR1[soft,ping-restart] received, process restarting
Mar 18 00:46:28 ovpn-client1[1652]: Restart pause, 5 second(s)
Mar 18 00:46:33 ovpn-client1[1652]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mar 18 00:46:33 ovpn-client1[1652]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mar 18 00:46:33 ovpn-client1[1652]: TCP/UDP: Preserving recently used remote address: [AF_INET]116.235.159.34:1194
Mar 18 00:46:33 ovpn-client1[1652]: Socket Buffers: R=[122880->122880] S=[122880->122880]
Mar 18 00:46:33 ovpn-client1[1652]: UDP link local: (not bound)
Mar 18 00:46:33 ovpn-client1[1652]: UDP link remote: [AF_INET]116.235.159.34:1194
Mar 18 00:46:33 ovpn-client1[1652]: TLS: Initial packet from [AF_INET]116.235.159.34:1194, sid=6ab6d4aa 8aee2ecf
Mar 18 00:46:33 ovpn-client1[1652]: VERIFY OK: depth=1, CN=LJC
Mar 18 00:46:33 ovpn-client1[1652]: VERIFY OK: depth=0, CN=LJCS
Mar 18 00:46:33 ovpn-client1[1652]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1541', remote='link-mtu 1558'
Mar 18 00:46:33 ovpn-client1[1652]: WARNING: 'cipher' is used inconsistently, local='cipher BF-CBC', remote='cipher AES-128-CBC'
Mar 18 00:46:33 ovpn-client1[1652]: WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'
Mar 18 00:46:33 ovpn-client1[1652]: Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Mar 18 00:46:33 ovpn-client1[1652]: [LJCS] Peer Connection Initiated with [AF_INET]116.235.159.34:1194
Mar 18 00:46:34 ovpn-client1[1652]: SENT CONTROL [LJCS]: 'PUSH_REQUEST' (status=1)
Mar 18 00:46:34 ovpn-client1[1652]: PUSH: Received control message: 'PUSH_REPLY,route 10.10.11.0 255.255.255.0,route 10.8.0.0 255.255.255.0,topology net30,ping 15,ping-restart 60,ifconfig 10.8.0.6 10.8.0.5,peer-id 0,cipher AES-256-GCM'
Mar 18 00:46:34 ovpn-client1[1652]: OPTIONS IMPORT: timers and/or timeouts modified
Mar 18 00:46:34 ovpn-client1[1652]: OPTIONS IMPORT: --ifconfig/up options modified
Mar 18 00:46:34 ovpn-client1[1652]: OPTIONS IMPORT: route options modified
Mar 18 00:46:34 ovpn-client1[1652]: OPTIONS IMPORT: peer-id set
Mar 18 00:46:34 ovpn-client1[1652]: OPTIONS IMPORT: adjusting link_mtu to 1624
Mar 18 00:46:34 ovpn-client1[1652]: OPTIONS IMPORT: data channel crypto options modified
Mar 18 00:46:34 ovpn-client1[1652]: Data Channel: using negotiated cipher 'AES-256-GCM'
Mar 18 00:46:34 ovpn-client1[1652]: Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mar 18 00:46:34 ovpn-client1[1652]: Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mar 18 00:46:34 ovpn-client1[1652]: Preserving previous TUN/TAP instance: tun11
Mar 18 00:46:34 ovpn-client1[1652]: Initialization Sequence Completed
Mar 18 00:46:49 ovpn-client1[1652]: write to TUN/TAP : Invalid argument (code=22)
Mar 18 00:47:04 ovpn-client1[1652]: write to TUN/TAP : Invalid argument (code=22)
Mar 18 00:47:19 ovpn-client1[1652]: write to TUN/TAP : Invalid argument (code=22)
Mar 18 00:47:34 ovpn-client1[1652]: write to TUN/TAP : Invalid argument (code=22)
Mar 18 00:47:49 ovpn-client1[1652]: write to TUN/TAP : Invalid argument (code=22)
Mar 18 00:48:04 ovpn-client1[1652]: write to TUN/TAP : Invalid argument (code=22)
Mar 18 00:48:20 ovpn-client1[1652]: write to TUN/TAP : Invalid argument (code=22)
Mar 18 00:49:20 ovpn-client1[1652]: [LJCS] Inactivity timeout (--ping-restart), restarting
Mar 18 00:49:20 ovpn-client1[1652]: SIGUSR1[soft,ping-restart] received, process restarting
Mar 18 00:49:20 ovpn-client1[1652]: Restart pause, 5 second(s)

 

[Dresden919]

Upgraded 5300 from 380 to 384. Open VPN doesn't work. Was working fine on 380 but will not start. Logs show below. It took all the settings, but then client doesn't start. I did a full factory reset after upload. Any suggestions.

Error log says:

Mar 17 10:11:55 rc_service: httpd 383:notify_rc start_vpnclient2
Mar 17 10:11:55 rc_service: waitting "restart_time;restart_wireless" via httpd ...
Mar 17 10:12:10 rc_service: skip the event: start_vpnclient2.

Update:
I did a browser refresh, cleared cache and settings and guess what it shows the VPN is up and running fine. Weird but glad it's working.

 

[ozzed]

Since a Factory reset is suggested is there a recommended / easy way to capture current settings for easier application to new release?

I am currently operating on 380.69.2 and have many settings for static IP, VPN, etc

Al

I like to use this utility: https://www.snbforums.com/threads/user-nvram-save-restore-utility-r26-2.19521/ but I'm not sure if it would work when migrating from 380 to NG. Personally I'm going to wait and see if this gets cleared up or not. The utility has been by go-to and I feel like I have too many settings to sit and do them all manually.

 

[IsaacFL]

If doing a reset/initialize to the router configuration, I used to know where the certificates for https were and would manually put them back, using scp. Now that I have Lets Encrypt certificate being magically generated by Asus, I am not sure where the certs are located?

Do I just let them be magically generated again? What about my OpenVPN server certs?