What's new

ASUS RT-AC68U Firmware version 3.0.0.4.378.6975

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I joined these forums in my frustrating journey to try and get OpenVPN server working on my RT-AC68U. In case anyone else stumbles on this post, I may have some information to save you time:

1. I tried following the guide here: http://www.smallnetbuilder.com/othe...-setting-up-and-using-openvpn-on-asus-routers . I could not get this to work, using the step-by-step method here. Through google research, I discovered that the likely issue with the error I was getting (TLS handshake) was that the ASUS router was trying to use 1024 TLS encryption, but that the new OpenSSL library and the newest versions of OpenVPN require 2048 encryption. So it is a "bug" that the generated VPN server creates a 1024 encryption protocol.

2. Okay, time to try and trouble-shoot the issue:

i) This link suggests manually going into the OpenVPN Advanced Server Settings and inputting a 2048 DH key. You could either generate one yourself (more complicated, see below) or use a generated on that they link you to. The thread is here: http://www.snbforums.com/threads/as...-fails-diffie-helmann-dh-key-too-small.25326/ , and the key they point you to is: https://raw.githubusercontent.com/R...ster/release/src/router/rom/others/dh2048.pem

ii) I tried copying the pre-generated link, but that gave me an error message regarding the DH key. I figured it might be "more secure" to generate my own DH key, though in the thread RMerlin states "No. In fact, that DH came from an RFC, and is used by various applications following that RFC. You just need to ensure that the DH is based on a prime number that can't be trivially cracked back - that's why I went with 2048-bit, and also for one from an RFC rather than one randomly generated."

iii) Time to try generating my own DH key. The first method I was going to try (I am on a Windows 8.1 machine) was to install OpenSSL and then use the windows command prompt to generate a key. The following blog had a nice guide on how to try and attempt this: https://jchornsey.wordpress.com/2015/03/17/installing-openssl-in-windows-8-1/ . Make sure if you try this method that you disable UAC, otherwise the command prompts won't work: http://superuser.com/questions/464758/how-do-i-disable-administrator-prompt-in-windows-8 , http://www.eightforums.com/system-s...e-windows-8-understand-you-administrator.html . I wasn't having much luck, and through searching found the next, and following guide:

iv) http://www.snbforums.com/threads/how-i-set-up-ovpn-on-my-asus-rt68r-for-android.17644/ ; although intended for Android use, it showed you how to create your own certificate, keys, etc using the OpenVPN software (make sure to download the program and check that you install ALL components). Was having some issues with some of the steps, but these primarily resolved once I disabled UAC completely (see previous step).

v) So I went through the whole guide above, got my keys and certs set up, and was ready to try inputting them into the router. After I did all that, and hit save, I got an error about the DH key again. When I went back to the section where I inputted all the certificates, I noticed everything was blank. Interesting. I also looked at the error log in the router, and it had something to do with generating the dh.pem file.

vi) Interestingly, when I visited ASUS Firmware page: https://www.asus.com/us/Networking/RTAC68U/HelpDesk_Download/ , 3.0.0.4.378.4850 is listed as the most current version. Within the Router GUI, .4850 was considered the most up to date. However, I saw some posts in this thread suggesting webserver is out of sync. Okay, I downloaded this one-two days ago, maybe since then there were some sync issues. Anyway, when I revisited the change-log for this version (Original Post):
- Fixed the saving issue in OpenVPN server -> content modification of keys & certification.

However, I wonder if the issue was truly fixed?! I certainly seemed to be having save issues of the keys and certs on this version of the firmware, and still can't get OpenVPN server to run on this router (talk about a long process/nightmare!)

Collection of Random Helpful Posts:
* http://www.snbforums.com/threads/asuswrt-merlin-378-54_2-is-now-available.24902/page-12#post-188181
* https://forums.openvpn.net/topic12096.html (regarding UAC)
* https://board.perfect-privacy.com/threads/openvpn-client-with-perfect-privacy-on-asus-rt-ac66u.302/
* http://www.sparklabs.com/forum/viewtopic.php?p=5307#p5307 :
this site actually has really good discussion. Upon re-visiting it, I wonder if this was my issue:

Maltz wrote:It appears that ASUS routers generate a 512-bit DH parameter, which is what was causing the error for me (on the Mac version w/ ASUS RT-N66U). Thankfully, it's easy to fix, without replacing the 1024-bit certificates and private key, if you have access to openssl.

  1. This command will generate a 2048-bit DH PEM file. It might take a couple of minutes if you're on an older machine.
    CODE: SELECT ALL
    openssl dhparam -out dh2048.pem 2048
  2. In the router's OpenVPN configuration, select Advanced Settings, then click on Content Modification of Keys and Certification
  3. The bad news here (at least in my firmware/browser) is that the router's web interface adds HTML encoded linefeeds in the keys (e.g. "
" etc) If you leave them there when you click SAVE, it will screw up the certificates. What I did is copy each certificate to a text editor, global replace the encoded strings with a linefeed, and then copy/replace it back into the browser window. It might be prudent to download a router configuration file before you start this, in case the certs get mangled beyond repair by the poorly written web interface.
  4. Now, just replace the contents of the Diffie Hellman parameters with the file that openssl generated above, and click SAVE. Then I think you also have to click APPLY when that window closes. I did, anyway.
That did it for me. Hope that helps!

I did try to "Paste as Plain Text", and I don't think I saw linefeed keys (as I was pasting from Notepad++), but I do want to try again and see if I was pasting with line-feeds.

Otherwise, I think this is ALL a bug with a REVOKED firmware version because they did not fix an error they claim in the changelog!

I wonder what anyone else's experience is ? Thanks!!
 
I've been sitting back on release 4585 for the AC68U for several weeks because the later level offerings were all beta. A few days back I noticed that 6975 was offered as non beta. I checked for issues and waited a bit more. Three days back I updated. Today I looked and 6975 is no longer up on the ASUS downloads.

What the hell is going on at ASUS? Some information and some stability would be excellent. Doesn't seem to be much of any of that from ASUS.
 
I'm in Australia. It never occurred to me that ASUS would have multiple download sites. I just Googled for the link and here is what I got. https://www.asus.com/au/Networking/RTAC68U/HelpDesk_Download/
and even when I go to asus.com and get this link http://www.asus.com/Networking/RTAC68U/HelpDesk_Download/ I still get the same result. See the image.
Capture.JPG


Edit: I've tried several ways into ASUS support and used Chrome as well as IE11 and I still get te same result. Can someone please post a link to support for RT-AC68U

thanks
Bob
 
Last edited:
Thanks msb , I compared the MD5's from that source to the file I have on my machine and they are identical. I will check both sources in the future for downloads.
 
Yes, I did note that the downloads referred to were for the RT-AC68P but it would seem that the code requirements for the two routers are so similar that they use EXACTLY the same code in release 6975. I compared the MD5 hashes and they were identical. I don't know if this is so for other releases or even if any other identical releases even exist for the two routers.
 
Last edited:
I'm in Australia. It never occurred to me that ASUS would have multiple download sites. I just Googled for the link and here is what I got. https://www.asus.com/au/Networking/RTAC68U/HelpDesk_Download/
and even when I go to asus.com and get this link http://www.asus.com/Networking/RTAC68U/HelpDesk_Download/ I still get the same result. See the image.
View attachment 4175

Edit: I've tried several ways into ASUS support and used Chrome as well as IE11 and I still get te same result. Can someone please post a link to support for RT-AC68U

thanks
Bob
It is the same on ASUS Canada site.
http://www.asus.com/ca-en/Networking/RTAC68U/HelpDesk_Download/
I'd like to have the opinion of Rmerlin.
 
The RT-AC68U, RT-AC68R and RT-AC68P all use the exact same firmware. When the firmware is compiled, it's compiled as RT-AC68U, the file is only renamed to distinguish it at download time.
 
So it appears that firmware 6975 for rt-ac68u is withdrawn for unknown reasons but that identical firmware is left available for the rt-ac68P. I'm sure that ASUS has very good reasons for what they do but I can only think of three words and that is WTF.
 
The RT-AC68U, RT-AC68R and RT-AC68P all use the exact same firmware. When the firmware is compiled, it's compiled as RT-AC68U, the file is only renamed to distinguish it at download time.
But version 6975 as been removed from ASUS. The latest official version remaining is 4585 dated 2015-03-12. And there is three BETA version 4850, 7410 and 7498. Very strange!
 
But version 6975 as been removed from ASUS. The latest official version remaining is 4585 dated 2015-03-12. And there is three BETA version 4850, 7410 and 7498. Very strange!

Makes no sense to keep the 6975 beta up if you need your users to test newer betas. Keep in mind that betas are meant either for test purposes, or for addressing specific issues. It only clutters the download page.
 
Well my version of 6975 certainly didn't fix the one thing I had hoped in the changelog! I can imagine that is at least one good reason they withdrew it.
 
Makes no sense to keep the 6975 beta up if you need your users to test newer betas. Keep in mind that betas are meant either for test purposes, or for addressing specific issues. It only clutters the download page.
The 6975 update was not in beta when I last saw it on the update list.
 
when i updated to 6975 i'm pretty sure it wasn't beta at the time.
 
I'm sure 6975 was not a BETA version. And there is a tread for it. I think ASUS did withdraw the 6975 for an unknown reason.
EDIT:
I found this on ASUS support for the RT-AC68W:
http://www.asus.com/ca-en/Networking/RTAC68W/HelpDesk_Download/
I just checked the MD5 hash on that against the file I downloaded last week from the RT-AC68U site and it is identical. The question is why is it missing from one web site but available on several others?
 
Makes no sense to keep the 6975 beta up if you need your users to test newer betas. Keep in mind that betas are meant either for test purposes, or for addressing specific issues. It only clutters the download page.
6975 was not and is not marked as a beta build for the RT-AC68P
 
I just checked the MD5 hash on that against the file I downloaded last week from the RT-AC68U site and it is identical. The question is why is it missing from one web site but available on several others?

As has been commented and repeated extensively, Asus' takes a while to replicate files to all their servers world wide.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Top