Changes:
- NEW: Temporarily reorganized code in separate branches, to handle Asus's currently scattered firmware source code releases.
- NEW: Added NFS client support (V2 and V3) to the RT-AC86U and RT-AX88U (already present in older models)
- NEW: Report the number of spatial streams and the PHY type used by wireless clients for models supporting it
- NEW: Display tracked connections on the QoS Stats page (now relabeled "Classification"). Fields can be sorted by clicking on the column headers. Thanks to FreshJr for his help in deciphering the packet mark values.
- NEW: Implemented ipsec.postconf and strongswan.postconf scripts.
- KNOWN ISSUE: dcd process crashing on RT-AC86U (bug in Trend Micro's code, outside of my control).
- KNOWN ISSUE: IPv6s on Tracked Connections have their last two bytes set to 00 (bug in Trend Micro's code truncating the last two bytes).
- KNOWN ISSUE: No IPS events logged (bug in Asus's code, IPS should work, just fails to log hits)
- KNOWN ISSUE: Networkmap listing may be unreliable. (Bug in Asus's code)
- KNOWN ISSUE: Users failing to read changelogs will probably complain about the above issues. (Outside of my control).
- CHANGED: Updated wget to 1.20.
- CHANGED: Updated nano to 3.2.
- CHANGED: Updated curl to 7.62.0.
- CHANGED: Updated Chart.js to 2.7.3.
- CHANGED: Updated dnsmasq to 2.80-32-g28cfe36 (themiron)
- CHANGED: Optimized some JS files to reduce their size
- CHANGED: OpenVPN clients can now accept CNs up to 255 chars when using it to validate the certificate.
- CHANGED: No longer reset the OpenVPN client's description, policy mode and existing rules when uploading an .ovpn config file.
- CHANGED: No longer accept any server-provided route when OpenVPN client set to Policy (Strict).
- CHANGED: Clients bound to DNSFilter rules will no longer bypass it by using DoT. DNSFilter servers that support DoT (like Quad9) will only allow filtered clients to use that server
- FIXED: Firmware update checks would not run at boot time on the RT-AX88U.
- FIXED: Name resolution issues for /etc/hosts entries on HND models (themiron)
- FIXED: Syslog not properly copied to JFFS on reboot (John Bacho)
- FIXED: Volumes not properly unmounted on HND platform (John Bacho)
- FIXED: Added missing TEE Netfilter target on the RT-AC86U
- FIXED: SSH brute force protection didn't work in Dual WAN load balancing mode.
- FIXED: httpd crashes on RT-AC86U (themiron)
- FIXED: DNSFilter clients could use a different nameserver when using an IPv6 connection
- FIXED: USB disk idle config changes not applying without a reboot.
- FIXED: "Strict" DNS mode wasn't working properly with OpenVPN clients
- FIXED: Cannot upload JFFS backup on HND models
The GPL situation for this release is as follow:
- RT-AX88U: Merged GPL 384_5329
- Other models: Merged GPL 384_45149.
- Special binary blobs provided by Asus for the RT-AC87U and RT-AC3200 (compatible with 384_45149).
Flash instructions, read carefully:
- Backup the /jffs partition because the flashing will erase all data;
- When coming from 380 to 384/NG You MUST flash the 380.70 build first;
- You MUST to do a factory default reset after flashing the NG build;
- Clear your browser cache after flashing the 384/NG.
Installation:
Simply flash it like any regular update. You should not need to reset to factory defaults. You can revert back to an original Asus firmware at any time just by flashing a firmware downloaded from Asus's website.
NOTE:
resetting to factory default after flashing is strongly recommended for the following cases:
- Updating from a firmware version that is more than 3 releases older
- Switching from a Tomato/DD-WRT/OpenWRT firmware
If upgrading from anything older and you experience issues, then consider doing a factory default reset then as well. Always read the changelog, as mandatory resets will be mentioned there when they are necessary.
In all of these cases, do NOT load a saved copy of your settings! This would be the same thing as NOT resetting at all, as you will simply re-enter any invalid setting you wanted to get rid of. Make sure to create a new backup of your settings after reconfiguring.
Installation Notes:
- This custom firmware can be applied like any regular update.
- You should not need to reset to factory defaults.
- You can revert back to an original ASUS firmware at any time.
- Do not load a saved copy of your settings.
About Router Firmware:
Before you consider downloading this firmware, go to the system information page of the router and make sure that the currently installed version isn't either newer or matching this release.
Due to the large variety of router models and different methods for upgrading the device, it is highly recommended that you read and, above all, understand the installation steps before you apply the new firmware, even if you are a power user.
In theory, these steps shouldn't be much of a hassle for anyone, because manufacturers try to make them as easy as possible, even if they don't always succeed. Basically, you must upload the new firmware to the router through its administration page and allow it to upgrade.
If you install a new version, you can expect increased security levels, different vulnerability issues to be resolved, improved overall performance and transfer speeds, enhanced compatibility with other devices, added support for newly developed technologies, as well as several other changes.
If you're looking for certain safety measures, remember that it would be best if you perform the upload using an Ethernet cable rather than a wireless connection, which can be interrupted easily. Also, make sure you don't power off the router or use its buttons during the installation, if you wish avoid any malfunctions.
If this firmware meets your current needs, get the desired version and apply it to your router unit; if not, check with our website as often as possible so that you don't miss the update that will improve your device.
- CATEGORY:
- Router / Switch / AP
- COMPATIBLE WITH:
- OS Independent
- file size:
- 62.9 MB
- filename:
- R7000_384.9_0.zip