[Beta] Asuswrt-Merlin 382.1 Beta is available

[RMerlin]

Edit 17-Oct-2017: Added RT-AC88U and RT-AC3100 builds.
Edit 24-Oct-2017: Uploaded 382.1 Beta 2. Changelog:

2e8b7ce Updated documentation
c21d7dd rc: Do not prepend 3.0.0.4 to FW version (console boot log, and minidlna config file)
f8702e9 webui: DNSFilter - fix the "Add" button image, better identify the Client field as a MAC
ec8fdf5 webui: fix OUI lookups
9744754 webui: update OUI database
80787fe webui: fixed Ethernet table layout on Sysinfo page
a21c78d e2fs: add back tune2fs (to match AM380)
2bee3b5 Converted changelog-382.txt to Windows format (it's time for Microsoft to add UNIX EOL support to Notepad me thinks - everything else does already)
58e3058 webui: add missing "Custom" DDNS type
7c6e9c0 dnsfilter: split rules across multiple nvram on HND due to 255 chars limit
053ff57 shared: fix nvram_split_get() and enable it
8be8bf7 httpd: remove unused variable
d4db370 dnsfilter: free duplicated string after building iptables rules
3bfea15 openvpn: fix a few cases where we requested the incorrect certificate types at config time.
4d69911 nvram: implemented workarounds and safeguards for HND limiting non-Asus nvram additions to 255 chars max
419fb9c Bump revision to beta 2
e6fadd7 dhd,networkmap: add missing dhd and arpstorm exe recovered from firmware releases
9296183 webui: add missing model-specific files for RT-AC88U and RT-AC3100
62913a4 sdk7114: merge working binary blob for RT-AC88U

Edit 2-Nov-2017: Uploaded 382.1 Beta 3. Changelog:

4fe0847 Updated documentation
fe83c7e libvorbis: checkout files from AM380, as the AM382 files would often fail to configure/compile on ARM
2ac3f39c httpd: Retrieve max CPU clock on HND from bcm_cpuidle rather than kernel cpufreq (which was removed with last SDK update)
762d92c webui: Convert HND CPU temperature from float to integer values
71f5b52 HND: merge latest SDK files from GPL 382_18219, which should in theory include the KRACK fixes for that platform
54a132d iptables: updated to 1.4.15 (fixes iptables-restore on HND)
43bcb9e wget: add files filtered out by gitignore
6ba6cda wget: update to 1.19.2, fixing connectivity to some servers
b19a332 webui: remove username/password validation from code used for CUSTOM DDNS
798dd0f opnssl: re-add make depend from AM380
8416601 openssl: update to 1.0.2l (1.0.2j from GPL was initially merged in for 382)
2654afb minidlna: remove USE_DAEMON option from config files, as it would sometimes get re-enabled (and it doesn't work)
35a05e9 kernel41: enable XT_SET kernel module
6b56d48 Bumped revision to beta 3

Edit 9-Nov-2017: Uploaded beta 4. Changes:

98e3abf build: rename deploy script to publish; fix documentation location; start/stop ssh agent
2cf5a2c rc: disable update checks if merlinupdate isn't enabled
d8be69c libvpn: make _set_crt_parsed() skip cert text and start at the PEM
5408770 libvpn: removed legacy nvram support, as we only support JFFS storage from now on
f9a9996 libvpn: rewrite get_parsed_crt() to only work at the file level, resolving buffer truncate issue as well; made set_ovpn_key() create folder if needed, and changed way it raeds the data
11f376b shared: set max length of vpn_client_addr to 128 chars, as it can be a hostname, not just an IP
4212c90 httpd: write back the new cert instead of the one already in nvram/jffs
de7f7b5 build: added confirmation request to deploy script; also upload documentation
7497066 build: add new deploy script used for Sourceforge and Onedrive
9a80631 qos: remove duplicate include (no code change) (closes #47)
58670ea usb: disable USB3 interference reduction by default
eeac558 openvpn: when WAN comes up, start ovpn clients after iQoS/FW have been started
d8086bb Bump revision to beta 4

Asuswrt-Merlin 382.1 Beta is now available for the RT-AC86U, RT-AC88U and RT-AC3100 only. No other models are supported for now as Asus hasn't migrated them to the 382 code base yet.

Asuswrt-Merlin 382.xx was started from a clean GPL release, with the Asuswrt-Merlin changes re-applied on top of it. This was made necessary due to the large amount of changes between 380 and 382. Because of this, both branches will for the time being be developed in parallel, as models will gradually be ported over from the 380 code to the newer 382 code (as Asus progressively migrates them to this new code base).

Due to this, some old issues might be resolved, while new ones might also have been introduced.

The summary of changes between 380.68_4 and 382.1:

• Code re-implemented starting from a pristine 3.0.0.4.382_15098 GPL release
• Merged with GPL 3.0.0.4.380_16466
• Implemented support for the RT-AC86U. All previous Asuswrt-Merlin features are supported, except for IPTraffic, which is not compatible with the newer Linux kernel used by this model.
• Reworked OpenVPN implementation. Starting with 382_xxxx, Asus has made their OpenVPN implementation closed-source. Because of this, it was decided to stick to our (more advanced) existing implementation, and to fork away OpenVPN development from Asus's own. A lot of changes were made to the existing code as it no longer needed to remain in sync with Asus (and also to better interface with the new API Asus used with their new OpenVPN implementation). Because of this, it's also recommended to do a factory default reset when going back to Asus's stock firmware (or, be prepared to having to reconfigure your OpenVPN settings).
• Added Full Cone NAT support to the RT-AC86U.
• Added WiFi Radar to the RT-AC86U. This is Broadcom's own visualization engine, which can help troubleshoot wireless issues (for advanced users only). Make sure you read the full Changelog for more informations.
• SSH keys are now stored in /jffs/ssl/ rather than in nvram (in part to deal with a change in 382's nvram management that has problems with long nvram values).
• Updated OpenVPN to 2.4.4.
  [*]Various webui enhancements to the OpenVPN, Operational Mode and SNMP pages.
• Changes to the new firmware check process (new manifest format, and also the Beta channel will now also check for any newer version from the Release channel)

Make sure you read the complete Changelog for more information.

Things that need to be tested:

• Pretty much everything on the RT-AC86U, as it's a new model
• OpenVPN in particular, as a lot of code was changed there

Please keep discussions in this thread to this specific release.


Downloads are here.
Changelog is here.

 

[RMerlin]

• Webui oddities: do a shift-reload of the page, or flush your browser cache.

 

[RMerlin]

A couple of random notes:

The SDK 7114 code (for RT-AC88U/RT-AC3100/RT-AC5300) has been merged into the new code repository, however the RT-AC88U GPL release is broken (wifi doesn't work), and I have no way of testing if the RT-AC3100 suffers from the same issues, so for the time being only the RT-AC86U is supported. Once Asus issues working GPL code, other models will be added (either in 382.1 or 382.2, depending on how late during the beta cycle this happens).

The 382 code resides in a new Github repository. I took this opportunity to start with a fresh new repo, as I've been wanting for quite some time to trim the repo down a bit. The new repo is only 628 MB, versus 1.82 GB for the old one (which contains years of past versions of wireless drivers, all the old RT-N16U drivers, etc...). The toolchains were also moved to their own separate repo, so they no longer get cloned every time you clone the project code. This should improve git performance in general.

The Wiki on the previous repository will remain the primary documentation - Wiki support won't be enabled on the 382 repo.

The project website got a bit of a reorganization to handle the two parallel branches. I'm not 100% satisfied with these changes yet, so I might tweak them a bit further in the future.

At this point, it's highly likely that I won't be moving the RT-N66U and RT-AC66U models to the new 382 codebase, even if Asus does so. This is to make the project workload more manageable for a single individual, by eliminating the whole MIPS model branch. I might still issue some security issues for these models through the 380.xx branch for at least some time. If you own one of these models and would prefer to get a more actively developed firmware, I recommend moving to @john9527 fork as it's actively developed, and you won't be losing much from my firmware (since these two models don't support the Trend Micro engine that's missing in John's fork). I will see how things develop in the coming months to determine how actively and for how long I want to continue providing at least basic security fixes for these two older models.

If someone with the required technical know-how wants to work the 382 code and provide their own N66U/AC66U support, feel free to fork the 382 project on Github.

The RT-AC86U support (through its new Broadcom HND SDK) has been the most difficult one to implement so far. It took me roughly 3 weeks to implement ARM support back when the RT-AC56U came out. I think it took me about twice as much time for the RT-AC86U, and I see Asus themselves are still working on getting it fully done. Broadcom's HND SDK is really painful to work with - it's simply a large mess. I'm surprised Asus still managed to get that to work within Asuswrt. I can still see a lot of Broadcom leftovers all over the place though, with many unused config files being included in the firmware image.

The GT-AC5300 is not supported because it has a lot of unique features that would require a additional work to maintain specifically for that one single model. And at least one of these (VPN Fusion) would clash with Asuswrt-Merlin's own Policy Rule system. If someone feels inclined in supporting that model (and taking responsibility for providing user support for it!), adding GT-AC5300 support shouldn't be too hard, as the HND platform itself is implemented.

And in case by now you've already forgotten what I wrote before (I sure do get long-winded now and then!): do not ask me if/when other models will be supported. The first thing that is necessary is for me to get access to working GPL code to merge in Asuswrt-Merlin. This is outside of my control.

 

[XIII]

RT-AC66U owner here. If this indeed is (the start of) the end of the ride: thanks, it was a good one!

In fact, I'm considering upgrading to an RT-AC68U or RT-AC86U, just because of the Asuswrt-Merlin firmware...

PS: Hope you can still fix KRACK for the MIPS platform; if Asus releases a fix:

https://arstechnica.com/information...l-leaves-wi-fi-traffic-open-to-eavesdropping/

 

[Vexira]

RT-AC66U owner here. If this indeed is (the start of) the end of the ride: thanks, it was a good one!

In fact, I'm considering upgrading to an RT-AC68U or RT-AC86U, just because of the Asuswrt-Merlin firmware...

PS: Hope you can still fix KRACK for the MIPS platform; if Asus releases a fix:

https://arstechnica.com/information...l-leaves-wi-fi-traffic-open-to-eavesdropping/

get an 86u your better off

 

[XIII]

get an 86u your better off

Probably, but the AC86U is €250 (and have to import from another EU country), while the AC68U is €150 over here.

I guess in some time they will both run Asuswrt-Merlin 382 (the topic of this thread).

 

[Pir8pete]

@merlin

tested beta 1, and the only minor things I can see so far;

-I'd switch the smart connect rule and Wi-Fi Radar around or put both under the Wireless section would make more sense. Also instead of Wi-Fi Radar use WiFi Radar without the dash looks better.

-Changelog-382.txt is all outta place when opened with windows note pad.


I hope theres a fix for this asap -> https://www.krackattacks.com/

 

[Vexira]

Probably, but the AC86U is €250 (and have to import from another EU country), while the AC68U is €150 over here.

I guess in some time they will both run Asuswrt-Merlin 382 (the topic of this thread).

which eu country is that

 

[joegreat]

I hope theres a fix for this asap -> https://www.krackattacks.com/

Good news: There might be no update needed for the routers...

See: https://www.snbforums.com/threads/s...bility-disclosure-imminent.41658/#post-352561

 

[RMerlin]

I'd switch the smart connect rule and Wi-Fi Radar around or put both under the Wireless section would make more sense. Also instead of Wi-Fi Radar use WiFi Radar without the dash looks better.

These are in the same location and with the same name as Asus (WiFi Radar comes from the GT-AC5300). I don't want to move them around, otherwise people will get confused.

 

[XIII]

which eu country is that

Amazon Germany offers the RT-AC86U for those that want to try the Asuswrt-Merlin 382.1 Beta firmware.

 

[infatality]

@RMerlin I understand ac66u will be highly likely be dropped out off support.. How about ac66u b1? Will it still be supported by you when Asus drop 382 source?


Sent from my iPad using Tapatalk

 

[Zakalwe]

Will the RT-AC87U continue to be supported?

Thanks for the work on Asuswrt-Merlin. Hopefully the KRACK vuln. can be patched soon.

 

[Antony Williams]

That's great news that the AC-86U has moved to the 4.1 kernel.
Is Asus backporting the 4.1 kernel to any other devices? (I'm guessing no, as that would require new drivers from Broadcom....)
With all the security flaws being posted these days, you'd think the easiest solution would be to make the 1 time effort to move to an LTS kernel, and stay up to date.

 

[sveinan]

@RMerlin: Thanks for the beta Going through the motions of configuring my new RT-AC86U with 382.1_beta1, and factory reset. One small issue. I assign most of my devices manual IP through DHCP. For some reason I cannot get over 25 entries on the 'DHCP Server' tab. Not been a problem before, and limit according to page should be 128. Problem works like this. Whenever adding entries, and total gets over 25. Apply. None of the last 'batch' of IP's gets applied. Delete one entry. Apply. 24. Add one entry. Apply. 25. Add one more. Apply. Not applied, still 25.

 

[thelonelycoder]

Will the RT-AC87U continue to be supported?

If only people would read, I'm quoting Merlin in the release post at the top here, emphasis added:

And in case by now you've already forgotten what I wrote before (I sure do get long-winded now and then!): do not ask me if/when other models will be supported. The first thing that is necessary is for me to get access to working GPL code to merge in Asuswrt-Merlin. This is outside of my control.

 

[Makaveli]

If only people would read, I'm quoting Merlin in the release post at the top here, emphasis added:

lol the ability to read and comprehend like common sense is a rare thing these days

 

[thelonelycoder]

lol the ability to read and comprehend like common sense is a rare thing these days

I was overjoyed when the 382.xx codebase was announced for the 86U router.
Only I read it as 68U...

Humans, they're just like us.

 

[RMerlin]

@RMerlin I understand ac66u will be highly likely be dropped out off support.. How about ac66u b1? Will it still be supported by you when Asus drop 382 source?


Sent from my iPad using Tapatalk

Ac66 B1 is actually Rt-AC68U hardware, so it will be supported once that model gets migrated to 382 by Asus.

Sent from my P027 using Tapatalk

 

[MacG32]

On the first attempt to update from the alpha, I got this message, "Firmware upgrade unsuccessful. This may result from incorrect image or error transmission. Please check the version of firmware and try again." I rebooted the router and the update went smoothly.

Noticed this in my OpenVPN log: auth-token received, disabling auth-nocache for the authentication token. Hopefully, the authentication will not fail anymore after a time out for inactivity. Update 1: Authentication failed again. Added: pull-filter ignore "auth-token" to Custom Configuration. Back to testing. Update 2: Adding that worked!

Thank you again for all of your hard work and dedication @RMerlin ! It is greatly appreciated!