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.