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

[Lotta Cox]

I dont see it under switch control

 

[Lotta Cox]

Did you mean NAT acceleration? Turned it of and seems to have fixed it.

 

[john9527]

Did you mean NAT acceleration? Turned it of and seems to have fixed it.

That's the one...
CTF acceleration == HW acceleration == NAT acceleration (terms are used interchangeably)

 

[Lotta Cox]

That's the one...
CTF acceleration == HW acceleration == NAT acceleration (terms are used interchangeably)

Turning it off definetly fixed it

 

[john9527]

Turning it off definetly fixed it

Thanks for verifying it....working on a fix now.

 

[Lotta Cox]

Glad to help!

 

[RMerlin]

Thanks for verifying it....working on a fix now.

If you update CTF, don't forget to also update the kernel - Asus made some changes for it these past few months, related mostly to UDP, PPPoE and IPv6 in relation to CTF.

 

[tyspeed42]

My AC68W is running the Alpha, running lighting fast no issues so far, but when I tried it on my AC68U it has some quirky issues, not all sure what it was but the whole fam had issues with webpages loading, page stalling, loaded back 28E2 for now make them all happy. Haven't loaded on my AC66U to test yet, still running 28E2, running well. Thanks John for keeping this fork going.

 

[HardCat]

Hot off the presses! Alpha updated to V29A8 which includes the KRACK fix for the AC68 series.
Driver version wl0: Nov 29 2017 14:54:27 version 6.37.14.126 (r561982)

If anyone is using the AC68 as a Repeater/Media Bridge, would appreciate it if they could give this code a try.

It also includes backported fixes for 3 Samba CVEs (thanks Merlin)

That leaves only the AC56U...Asus activity on that has been rather quiet, so we'll need to wait and see. A reminder that the N16 will not receive the KRACK fix.

ALPHA RELEASE: Update-29A8 for the AC66U, N66U and AC68U
2-December-2017
Merlin fork 374.43_29A8j9527
Download https://1drv.ms/f/s!Ainhp1nBLzMJlW1TnFp4Sh2wvQva
============================

SHA256

(Default Build - All supported routers - Alpha for 'E' Builds)
3986b8e3413abd2c4b4f5dab6a1db8524832b17701ed7153fc15594775dfe39b  RT-N16_374.43_29A8j9527.trx
15510bf5db56c2c29082cc7d94ab195d0b18756f43ce640ea629cd84534456ac  RT-AC66U_374.43_29A8j9527.trx
ed11d7e6455c55259ca53c1aced11f7c80de5c107543529e45e534415455a8b4  RT-N66U_374.43_29A8j9527.trx
af1733d33fd0a22321fb70ff05515e574c25bc7e58d23df15051e1fcbe87d8db  RT-AC68U_374.43_29A8j9527.trx
3f0c2f34a68df53b167fa162d6cdc2f7d8ad6a14cf398b1cf110299cab404776  RT-AC56U_374.43_29A8j9527.trx

@john9527

I currently have a AC68U configured in Media Bridge mode Using ASUS's 382_18881 and am willing to give your alpha build a try, however I noticed later in the thread you are working on a CTF fix. Should I wait for the next update?

And, is there something specific you would like tested from the Media Bridge mode?

 

[john9527]

@john9527

I currently have a AC68U configured in Media Bridge mode Using ASUS's 382_18881 and am willing to give your alpha build a try, however I noticed later in the thread you are working on a CTF fix. Should I wait for the next update?

And, is there something specific you would like tested from the Media Bridge mode?

Thanks for the offer to help out. I'd just like someone with a stable setup to verify it keeps working, so nothing special to test.

Please hold off until the next update. I want to understand this bug a bit more.

 

[john9527]

but when I tried it on my AC68U it has some quirky issues, not all sure what it was but the whole fam had issues with webpages loading, page stalling, loaded back 28E2 for now make them all happy.

Likely the same bug with CTF....watch for the next update.

 

[kappagus2]

Dear @john9527,
Thanks very much for continuing to support our Asus routers with your outstanding releases. I was just wondering if you could update OpenVpn to allow AES-256-GCM ciphers on the Gui. It ( Aes-256-GCM ) is supported on OpenVpn 2.4 and beyond. Also, if you know of a way to configure GCM ciphers in Custom Configurations or from command line - please let me know. The Alpha most recent one ( of December 2nd ) is running well on ACP B1 - rt-ac68u. Again - you are very modest, dedicated and diligent in that you did not even want to let us know how long it took you to get the Krack protection working. I - for one - am very appreciative of those traits and qualities which you consistently exhibit and exemplify always. By the way, is there any thing that we need to do in order to enable Krack protection or is it working out of the box?
Thanks again. Happy Holidays and God Bless You and Yours - Always in God's Peace and Grace,

DIT

 

[john9527]

Thanks very much for continuing to support our Asus routers with your outstanding releases. I was just wondering if you could update OpenVpn to allow AES-256-GCM ciphers on the Gui. It ( Aes-256-GCM ) is supported on OpenVpn 2.4 and beyond.

It's already supported in the gui....

The Cipher Negotiation and Negotiable ciphers fields are for OpenVPN 2.4.....it is there you specify the GCM ciphers (You need to type them in....there currently isn't a construct for selecting multiple pulldown items). If you are connecting to a VPN server 2.3 or earlier, it will then fall back to use the Legacy cipher (or not connect if you set Cipher Negotiation to just Enable)

By the way, is there any thing that we need to do in order to enable Krack protection or is it working out of the box?

Transparent to the user when running in Repeater or Media Bridge modes.....nothing you need to do.

Thanks for the kind words......appreciated.

 

[kappagus2]

It's already supported in the gui....
View attachment 11102

The Cipher Negotiation and Negotiable ciphers fields are for OpenVPN 2.4.....it is there you specify the GCM ciphers (You need to type them in....there currently isn't a construct for selecting multiple pulldown items). If you are connecting to a VPN server 2.3 or earlier, it will then fall back to use the Legacy cipher (or not connect if you set Cipher Negotiation to just Enable)


Transparent to the user when running in Repeater or Media Bridge modes.....nothing you need to do.

Thanks for the kind words......appreciated.

Dear John,
Hello and thanks for the swift and informative reply. I got AES-256-GCM working I belive. I put " Cipher Negotiation " to Enable. Then I left " Negotiable ciphers " to default ( AES-128-GCM:AES-256-GCM:AES-128-CBC:AES-256-CBC ) in that field. Lastly, I entered " cipher AES-256-GCM " in the " Custom Configuration " box at the bottom of the OpenVPN Client Settings page. I just want to confirm that I did this correctly. Did I ? From your changelog - I see that you added * CHANGED: openvpn: update to 2.4.4 in 374.43_28E3j9527 (8-October-2017) ARM SDK. So I believe that I am using OpenVpn 2.4 as I am using your most recent Alpha release of yesterday.
Again - thanks for your assistance and do enjoy the Holidays.

In Peace and Grace,

DIT

 

[Uncle_Gadget]

I'm running v28L2 on 2 RT-AC68U's - 1 as a Router and the 2nd as an Access Point.

Since it's now time again for me to update my Let's Encrypt certs, I used to the cheat sheet I used the last time to update the certs on my Access Point. However, the steps I successfully used the last time (probably on 26E4) are no longer working. I always end up with the default certs in place. Could someone please review the steps I'm using and tell me where I'm going wrong? Since this method has worked fine for me in the past, I'm assuming a recent change has made them no longer work for me.

Sorry for using pastebin, but Cloudflare is blocking me from inserting the text anywhere in the message (even with code tags).

https://pastebin.com/raw/29nWUgvt

 

[john9527]

I'm assuming a recent change has made them no longer work for me.

Depending on when you last did it, there was a change to move the save location on jffs to be compatible with Merlin builds. The code should handle it, but just to double check....
after you do the first step of 'https2nvram', try entering the following commands

rm -rf /jffs/ssl
rm -rf /jffs/https

 

[john9527]

Alpha updated to V29A9 which addresses the problem with CTF reported by @phx28777 @Lotta Cox @tyspeed42

Although the problem was only reported on the AC68, a corresponding commit was also present on the MIPS builds and I suspect the problem was lurking there as well. If you are running the Alpha on the AC66 or N66, you may want to update to the A9 build to pick up this change.

Thanks again to everyone for the feedback.

ALPHA RELEASE: Update-29A9 for the AC66U, N66U and AC68U
3-December-2017
Merlin fork 374.43_29A9j9527
Download https://1drv.ms/f/s!Ainhp1nBLzMJkEFTnFp4Sh2wvQva
============================

SHA256

(Default Build - All supported routers - Alpha for 'E' Builds)
1c49d6da5628d4add6258fe1cdabdd445d8d1afed702a50669b081d15d9a3878  RT-AC56U_374.43_29A9j9527.trx
e83a10f8817cdc781e664564b6a846fc02921b945f267870012a23204affd9cd  RT-AC66U_374.43_29A9j9527.trx
bf16a48fe2863afed424a926fbc695ff204e5589fc0a5e9a6d169eff505d61dd  RT-AC68U_374.43_29A9j9527.trx
6911683f75995dea62f26632df522f49aa46b40c4afffeb4af1cd5c64a77263b  RT-N16_374.43_29A9j9527.trx
d208d460454105c78be9194f73bdaebebc6fe2e2dd945aa89dd2406f176c63b7  RT-N66U_374.43_29A9j9527.trx

 

[Lotta Cox]

will test at 9pm est

 

[phx28777]

RT-AC-68P
Loaded V29A9 over V28E8

CTF enabled before and afterwards

Uptime 35 minutes
Everything looking great as of now

Disconnected Ooma and it reconnected without problems

Win10 wired and wireless OK

IOS 11 Devices OK

New wireless driver works with all my devices tested to date

No need to forget network on any devices

Will post if any problems become apparent

 

[marnold]

Same symptoms as the previous alpha with NAT accel enabled.
Flashed, turned off the router. Rebooted modem, started modem and let boot, boot router, enable nat, forget wifi, and exactly the same as before

John's link is wrong. It takes you to the previous alpha. If you follow that link, click TestBuilds at the top, then click on Update-29A9 and proceed from there.