[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

[dopefish]

Next release is out! (With a couple of new features since the last Beta )

Hi John,

i am a long time user of your firmware and would like to give you some feedback. First of all thank you for all your hard work, i am very satisfied with all your firmware versions.

I just installed Update-24E2 and activated DFS for my RT-N66U, i am using the RT-N66U as Hotspot only. Now i am not sure if it works. My Oneplus 3 says that i am connected to my AP via 5GHz with CH44(46) and 5220MHz. According to wikipedia it already uses DFS but i am not sure!? See https://en.wikipedia.org/wiki/List_of_WLAN_channels
(Germany requires DFS and TPC capabilities on 5.250–5.350 GHz and 5.470–5.725 GHz as well; in addition the frequency range 5.150–5.350 GHz is only allowed for indoor use, leaving only 5.470–5.725 GHz for outdoor and indoor use.[23])

Channel: 44l
Capability: ESS
HT Capable
Extension channel: 46
Chanspec: 5GHz Channel Width 40MHz (0xd82e)

THANK YOU JOHN!

 

[ColinTaylor]

@dopefish Just because you have enabled the DFS channels doesn't mean that they will be used by default. If you want to use a specific DFS channel you must select it in the menu.

 

[RMerlin]

@dopefish Just because you have enabled the DFS channels doesn't mean that they will be used by default. If you want to use a specific DFS channel you must select it in the menu.
View attachment 9068

Asus has a checkbox to enable using DFS channels while in Auto channel selection. That option probably tweaks the channels passed to acsd (I didn't really look at the details since part of it is in the binary blobs).

 

[ColinTaylor]

Asus has a checkbox to enable using DFS channels while in Auto channel selection. That option probably tweaks the channels passed to acsd (I didn't really look at the details since part of it is in the binary blobs).

Also keep an eye on the syslog for "radar detection" messages. I found with my N66U that it wouldn't stay on the DFS channels for very long before it switched to a non-DFS channel.

 

[YasharF]

Next release is out! (With a couple of new features since the last Beta )
LATEST RELEASE: Update-24E2

• ...
• Added support for moving SSH and OpenVPN certs to JFFS to free NVRAM space - @zonnebril @czekker
• ...

This is awesome, specially for folks with RT-N16 that has smaller nvram. I recall, OpenVPN was specifically disabled on RT-N16 since there wasn't enough room to store the certs in nvram. Is that still the case?

Thanks

 

[wiz]

Just updated mij N66u to 24e2. Thanks John for another great update!

 

[czekker]

just updated my RT-N16 to 24E2 - no problems so far..
tommorow will try to free some nvram
thanx John!

 

[czekker]

Given the N16 limitations, anyone recommend a good stable version for this router?
Did see a comment from John that 13Ex was a well respected stable version, so was wondering is there another!

i always update my RT-N16 with the latest LTS release as soon as possible.
it handles 120/12 easy.

 

[ajp2k14]

@john9527 : How does "random dnscrypt resolver" work? How often does it change?

 

[john9527]

@john9527 : How does "random dnscrypt resolver" work? How often does it change?

The Random option is really a building block. It causes DNSCrypt to select a random, non-logging, DNSSEC enabled resolver when it starts. It then uses this resolver until the next time it is stopped/started.

So, how often? That's up to you. You would need to set up a cron job with the command
service restart_dnscrypt
which would restart dnscrypt with a new random server.

Maybe a future gui option

 

[ajp2k14]

The Random option is really a building block. It causes DNSCrypt to select a random, non-logging, DNSSEC enabled resolver when it starts. It then uses this resolver until the next time it is stopped/started.

So, how often? That's up to you. You would need to set up a cron job with the command
service restart_dnscrypt
which would restart dnscrypt with a new random server.

Maybe a future gui option

Ah ok, I see! I was just wondering if I missed something..

 

[Fredex]

I have a RT-N16 still running stock ASUS firmware. It is currently the latest beta (now a year old) from the Asus web site, their version # is 9.0.0.4.380_2985-gfca31e3.

I saw some mention of some issue when updating with this firmware over Asus firmware that was "too new".

So, I'm wondering, am I safe to update using this LTS release on a router running that Asus version?

thanks in advance!

 

[L&LD]

I have a RT-N16 still running stock ASUS firmware. It is currently the latest beta (now a year old) from the Asus web site, their version # is 9.0.0.4.380_2985-gfca31e3.

I saw some mention of some issue when updating with this firmware over Asus firmware that was "too new".

So, I'm wondering, am I safe to update using this LTS release on a router running that Asus version?

thanks in advance!

You shouldn't have any issues. Just make sure to flash the router using the Asus Restoration Utility following the proper steps to get the router into recovery mode.

https://www.asus.com/uk/support/FAQ/109961/

Afterwards, you want to do a full reset to factory defaults, clear the nvram and format the jffs partition and reboot at least three times for each one. At this point; you should have a solid install on your router and you can properly test john9527's firmware for your uses.

https://www.snbforums.com/threads/n...l-and-manual-configuration.27115/#post-205573

https://www.snbforums.com/threads/rt-ac66u-slow-wan-to-lan.12973/page-3#post-269410

https://www.snbforums.com/threads/faq-nvram-and-factory-default-reset.22822/

 

[john9527]

I have a RT-N16 still running stock ASUS firmware. It is currently the latest beta (now a year old) from the Asus web site, their version # is 9.0.0.4.380_2985-gfca31e3.

The firmware level that prevents loading an older level is around 380.3000 or later. You are right on the cusp, and there are differences in the 'block' level between router models. You can give it a try through the gui, but if it fails, then you will have to use the ASUS Firmware Restoration Tool. Be patient, the tool can take a long time on MIPS routers (sometimes more than 1 hour).

For either method, follow with @L&LD 's advice on the factory reset/jffs reformat and reconfigure.

 

[dopefish]

Asus has a checkbox to enable using DFS channels while in Auto channel selection. That option probably tweaks the channels passed to acsd (I didn't really look at the details since part of it is in the binary blobs).

View attachment 9070

Also keep an eye on the syslog for "radar detection" messages. I found with my N66U that it wouldn't stay on the DFS channels for very long before it switched to a non-DFS channel.

Thank you but unfortunately this checkbox is not visible on my side, even in auto mode. Is this option bound to router mode only (i am using it as an AP)? DFS has been enabled on my side with
nvram set wl_dfs_enable=1
nvram commit && reboot

see screenshot. Did i forget something? Do i need to factory reset first? Furthermore i can see the DFS channels:

 

[ColinTaylor]

@dopefish You're right. It looks like that checkbox doesn't appear on the N66U for EU routers (which possibly explains why I didn't remember it). I think that's because it wasn't part of the original code base and is only enabled by manually setting that NVRAM variable.

    if(country == "EU"){ //display checkbox of DFS channel under 5GHz
        if(based_modelid == "RT-AC68U" || based_modelid == "RT-AC68U_V2" || based_modelid == "DSL-AC68U" || based_modelid == "RT-AC69U"
        || based_modelid == "RT-AC87U"){
            if(document.form.wl_channel.value  == '0' && '<% nvram_get("wl_unit"); %>' == '1')
                $('dfs_checkbox').style.display = "";
        }
    }

It was added into the later firmwares which is why it appears in Merlin's.

    else if(country == "EU"){        //display checkbox of DFS channel under 5GHz
        if(based_modelid == "RT-AC68U" || based_modelid == "RT-AC68A" || based_modelid == "4G-AC68U" || based_modelid == "DSL-AC68U"
        || based_modelid == "RT-AC87U"
        || based_modelid == "RT-AC3200"
        || (based_modelid == "RT-AC66U" && wl1_dfs == "1")        //0: A2 not support, 1: B0 support
        || based_modelid == "RT-N66U"){
                if(document.form.wl_channel.value  == '0' && wl_unit == '1'){
                        document.getElementById('dfs_checkbox').style.display = "";
                        check_DFS_support(document.form.acs_dfs_checkbox);
                }
        }

Personally I wouldn't use the Auto setting anyway. Just set it to something like channel 100 and see how it works out.

 

[john9527]

@dopefish You're right. It looks like that checkbox doesn't appear on the N66U for EU routers (which possibly explains why I didn't remember it). I think that's because it wasn't part of the original code base and is only enabled by manually setting that NVRAM variable.

Thanks for doing the debug/checking on this. It's something I missed trying to add when I added the base DFS channel support. I'll take a crack at adding it for the next beta (it's more than just the gui change...and it looks like it my depend on some prebuilt ASUS binaries, so will need help from someone to test it).

 

[john9527]

Pushed a quick update containing just a single commit to address problems with the latest Chrome 58 and https.

If you are updating to Update-24 for the first time, please take the time to review the first post full release notes.

LATEST RELEASE: Update-24E3
22-April-2017
Merlin fork 374.43_2-24E3j9527
Download http://bit.ly/1YdgUcP
============================

Contains the following update (full changelog is in the zip files)

• Support Subject Alternative Names in the router self-signed cert
  The latest Chrome 58 release changed the way certificates were handled, and the router self-signed certificate could no longer be recognized as valid. This change allows the router to generate an https certificate conforming to the new standard.

The fastest way to generate a new certificate for import to your browser if you are already using https access is via telnet/ssh.

nvram set https_crt_gen=1
nvram set https_crt_save=1
nvram commit
service restart_httpd

Close the current router window, and reconnect via https://192.168.1.1:8443 (or the url using your own router address and https port number). The browser will complain about an insecure connection due to a self-signed certificate. Use the procedure specific to your browser to accept the certificate and add it to the certificate store.

Alternatively, via the gui on the Administration > System tab,

1. Set 'Save HTTPS certificate' to No, and Apply (the router will reboot)
2. Close the current router window, and reconnect via https://192.168.1.1:8443 (or the url using your own router address and https port number). The browser will complain about an insecure connection due to a self-signed certificate. Use the procedure specific to your browser to accept the certificate and add it to the trusted certificate store.
3. In the router gui, set 'Save HTTPS certificate' to Yes and Apply (do not reboot the router before this step or a new certificate will be generated and you will need to repeat from step 2.

As always, a reminder to users with MIPS routers to have a backup of /jffs in case the jffs space needs to be reformatted due to increases in firmware size.

SHA256

76f1e5dcaa0fb4f69414e58670e3ff0cf7a83f0206b842ae47e757fd2e8e4fbf  RT-AC56U_3.0.0.4_374.43_2-24E3j9527.trx
4b75264326f599471cc8911af811fea333298ff6c372103672939259964b3958  RT-AC68U_3.0.0.4_374.43_2-24E3j9527.trx
b89595401f1adda4ed7daaff8118bd8a618b8c621d3161ce10f4dbe74bdfa9f0  RT-N16_3.0.0.4_374.43_2-24E3j9527.trx
4b4d2e050f63b5af66eef925214060fc916f288eef87802543943813958bc745  RT-AC66U_3.0.0.4_374.43_2-24E3j9527.trx
d63fbc4271a61cf49a7b17d85835a3c85089e3bb770ddf9a6280f3e703fd9ea9  RT-N66U_3.0.0.4_374.43_2-24E3j9527.trx

 

[cybrnook]

Thank you @john9527

 

[zonnebril]

Wow @john9527, what an awesome changlog! I am away for the weekend, but can't wait to check it out!

As always, thanks for your hard work and awesome support.