Asuswrt-Merlin 374.43 is out

[RMerlin]

Asuswrt-Merlin 374.43 is now available for RT-N16/RT-N66/RT-AC66.
EDIT:
Asuswrt-Merlin 374.43_2 is now available for the RT-AC68U
EDIT2:
AC56U build is now also available.


The focus of this release was fixing bugs and polishing things here and there.

• Traffic Monitoring for PPPoE users has been fixed, and should now report correct figures.
• A couple of webui-related issues were resolved, such as the problems with the new Media Server page, SSIDs with single quotes in their names breaking the webui, and a few others.
• dnsmasq now returns an empty string when queried for a WPAD proxy URL, which resolves log noise for broken clients such as Windows 7. Note that if you were using a custom dnsmasq.conf to provide a valid WPAD URL, you will need to change your config to use a Postconf script instead, to modify the default 252 option entry in dnsmasq.conf.
• A few component updates - miniupnpd and openssl were both updated to their latest versions. Additionally, a few additional ASM patches were backported from openssl 1.0.2, improving SHA performance for ARM-based routers.
• Guest clients were able to acess LAN devices when they weren't supposed to
• And a few other fixes, listed in the changelog.
• One new feature did trickle down into this release - you can now force a DDNS refresh after a configurable number of days.

Changelog is here.
Downloads are here.
More details can be found in the complete changelog.

MD5 checksums:

6c0f3e96c30896b06de74e47a22b2338  RT-AC66U_3.0.0.4_374.43_0.trx
c950755cdbc5f8d1078d2b8d4f105ab2  RT-N16_3.0.0.4_374.43_0.trx
78ebdd8b4c48fcfc7bef63111ad7ec4e  RT-N66U_3.0.0.4_374.43_0.trx

aa8091c9ddeb2f74e3f8a61e3fd12e18  RT-AC68U_3.0.0.4_374.43_2.trx
f357623534a2fa4ad9d4d4195a3139c3  RT-AC56U_3.0.0.4_374.43_2.trx

 

[jim769]

Dont see the new 43 for the 68u last entry is 42_2.


EDIT: Its there now not sure why it did not show before.

 

[toor]

whoot running and all good so far!

 

[jim769]

IPv6 with comcast is broke in this build 43_0 i have tried everything to get it to work its a no go. Reverting back to 42_0 fixes the problem reflash 43_0 and no go again.

 

[speedbump]

AC68U

I assume this did not require reset to factory defaults from 42_2, and I did not do it.

but my dnsmasq.conf.add does not work and when I try to go to one of the addresses I get : Firefox can't find the server at www.pandora.com.

This worked in 42_2, and here are the contents of the file:

admin@RT-AC68U-C378:/jffs/configs# more dnsmasq.conf.add
server=/netflix.com/21.23.43.50
server=/netflix.com/54.229.171.243
server=/pbs.org/21.23.43.50
server=/pbs.org/54.229.171.243
server=/pbskids.org/21.23.43.50
server=/pbskids.org/54.229.171.243
server=/bbc.co.uk/21.23.43.50
server=/bbc.co.uk/54.229.171.243
server=/4ondemand.com/21.23.43.50
server=/4ondemand.com/54.229.171.243
server=/itv.com/21.23.43.50
server=/itv.com/54.229.171.243
server=/youtube.com/21.23.43.50
server=/youtube.com/54.229.171.243
server=/hulu.com/21.23.43.50
server=/hulu.com/54.229.171.243
server=/pandora.com/21.23.43.50
server=/pandora.com/54.229.171.243
server=/smithsonianchannel.com/21.23.43.50
server=/smithsonianchannel.com/54.229.171.243
admin@RT-AC68U-C378:/jffs/configs# ls -l
-rwxrwxrwx 1 admin root 670 May 19 21:11 dnsmasq.conf.add
admin@RT-AC68U-C378:/jffs/configs#

my log does not appear to have any errors, but does seem to show the entries several times.

 

[speedbump]

my log does not appear to have any errors, but does seem to show the entries several times.

Dec 31 19:00:15 dnsmasq-dhcp[444]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Dec 31 19:00:15 dnsmasq-dhcp[444]: DHCP, sockets bound exclusively to interface br0
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain smithsonianchannel.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain smithsonianchannel.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain pandora.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain pandora.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain hulu.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain hulu.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain youtube.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain youtube.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain itv.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain itv.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain 4ondemand.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain 4ondemand.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain bbc.co.uk
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain bbc.co.uk
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain pbskids.org
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain pbskids.org
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain pbs.org
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain pbs.org
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain netflix.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain netflix.com
Dec 31 19:00:15 dnsmasq[444]: read /etc/hosts - 5 addresses
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain smithsonianchannel.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain smithsonianchannel.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain pandora.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain pandora.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain hulu.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain hulu.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain youtube.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain youtube.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain itv.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain itv.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain 4ondemand.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain 4ondemand.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain bbc.co.uk
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain bbc.co.uk
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain pbskids.org
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain pbskids.org
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain pbs.org
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain pbs.org
Dec 31 19:00:15 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain netflix.com
Dec 31 19:00:15 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain netflix.com
Dec 31 19:00:15 WAN Connection: Fail to connect with some issues.
Dec 31 19:00:15 dropbear[447]: Running in background
Dec 31 19:00:15 RT-AC68U: start httpd
Dec 31 19:00:15 crond[461]: crond: crond (busybox 1.20.2) started, log level 8
Dec 31 19:00:16 syslog: Generating SSL certificate...
Dec 31 19:00:20 disk monitor: be idle
Dec 31 19:00:20 kernel: gro enabled with interval 2
Dec 31 19:00:21 Samba Server: daemon is started
Dec 31 19:00:31 pppd[514]: Plugin rp-pppoe.so loaded.
Dec 31 19:00:31 pppd[514]: RP-PPPoE plugin version 3.11 compiled against pppd 2.4.5

 

[speedbump]

<continuation>
Dec 31 19:00:31 pppd[515]: pppd 2.4.5 started by admin, uid 0
Dec 31 19:00:31 pppd[515]: PPP session is 1 (0x1)
Dec 31 19:00:31 pppd[515]: Connected to via interface eth0
Dec 31 19:00:31 pppd[515]: Using interface ppp0
Dec 31 19:00:31 pppd[515]: Connect: ppp0 <--> eth0
Dec 31 19:00:35 pppd[515]: PAP authentication succeeded
Dec 31 19:00:35 pppd[515]: peer from calling number authorized
Dec 31 19:00:35 pppd[515]: local IP address
Dec 31 19:00:35 pppd[515]: remote IP address
Dec 31 19:00:36 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Dec 31 19:00:36 dnsmasq[444]: read /etc/hosts - 5 addresses
Dec 31 19:00:36 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain smithsonianchannel.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain smithsonianchannel.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain pandora.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain pandora.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain hulu.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain hulu.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain youtube.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain youtube.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain itv.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain itv.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain 4ondemand.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain 4ondemand.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain bbc.co.uk
Dec 31 19:00:36 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain bbc.co.uk
Dec 31 19:00:36 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain pbskids.org
Dec 31 19:00:36 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain pbskids.org
Dec 31 19:00:36 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain pbs.org
Dec 31 19:00:36 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain pbs.org
Dec 31 19:00:36 dnsmasq[444]: using nameserver 54.229.171.243#53 for domain netflix.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 21.23.43.50#53 for domain netflix.com
Dec 31 19:00:36 dnsmasq[444]: using nameserver 208.67.222.222#53
Dec 31 19:00:36 dnsmasq[444]: using nameserver 208.67.220.220#53
Dec 31 19:00:36 dnsmasq-dhcp[444]: DHCPREQUEST(br0) 192.168.1.64
Dec 31 19:00:36 dnsmasq-dhcp[444]: DHCPACK(br0) 192.168.1.64 android-aad4adbec95bd844
Dec 31 19:00:36 dnsmasq[444]: exiting on receipt of SIGTERM
Dec 31 19:00:37 dnsmasq[564]: started, version 2.69 cachesize 1500
Dec 31 19:00:37 dnsmasq[564]: asynchronous logging enabled, queue limit is 5 messages
Dec 31 19:00:37 dnsmasq-dhcp[564]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Dec 31 19:00:37 dnsmasq-dhcp[564]: DHCP, sockets bound exclusively to interface br0
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain smithsonianchannel.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain smithsonianchannel.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain pandora.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain pandora.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain hulu.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain hulu.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain youtube.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain youtube.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain itv.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain itv.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain 4ondemand.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain 4ondemand.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain bbc.co.uk
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain bbc.co.uk
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain pbskids.org
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain pbskids.org
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain pbs.org
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain pbs.org
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain netflix.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain netflix.com
Dec 31 19:00:37 dnsmasq[564]: read /etc/hosts - 5 addresses
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain smithsonianchannel.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain smithsonianchannel.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain pandora.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain pandora.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain hulu.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain hulu.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain youtube.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain youtube.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain itv.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain itv.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain 4ondemand.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain 4ondemand.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain bbc.co.uk
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain bbc.co.uk
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain pbskids.org
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain pbskids.org
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain pbs.org
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain pbs.org
Dec 31 19:00:37 dnsmasq[564]: using nameserver 54.229.171.243#53 for domain netflix.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 21.23.43.50#53 for domain netflix.com
Dec 31 19:00:37 dnsmasq[564]: using nameserver 208.67.222.222#53
Dec 31 19:00:37 dnsmasq[564]: using nameserver 208.67.220.220#53

 

[speedbump]

OK, weird it works NOW.... properly, is there a delay before the script is active after boot ?

I was able to get to this site but nothing that was added in the dnsmasq.conf.add file worked right after reboot

 

[InkyRag]

IPv6 with comcast is broke in this build 43_0 i have tried everything to get it to work its a no go. Reverting back to 42_0 fixes the problem reflash 43_0 and no go again.

Comcast IPv6 working fine here with 43_0.

 

[hackztor]

wol clear

What is the command to clear or reset the wake on lan page?

I did a search and only things I could find were

nvram set wol_list=""
nvram commit

But this is not working even after rebooting router.

 

[RMerlin]

IPv6 with comcast is broke in this build 43_0 i have tried everything to get it to work its a no go. Reverting back to 42_0 fixes the problem reflash 43_0 and no go again.

I get "it's now broken with Comcast" reported with every single new release, even when there was zero change to IPv6 code (like is the case with 374.43). Comcast's IPv6 support is simply quirky, the issue isn't the new firmware, it's the fact your router was rebooted, and it has trouble getting a new IPv6 connection established with Comcast - you would have experienced the same issue after a router reboot. Try a power cycle of your modem to fix it, that usually works.

 

[RMerlin]

What is the command to clear or reset the wake on lan page?

I did a search and only things I could find were

nvram set wol_list=""
nvram commit

But this is not working even after rebooting router.

The correct var name is wollist.

nvram set wollist=""
nvram commit

 

[RMerlin]

Dont see the new 43 for the 68u last entry is 42_2.


EDIT: Its there now not sure why it did not show before.

The original AC68U was accidentally uploaded to the AC66 directory - it was moved afterward.

 

[Poseidon]

I assume this will work with the RT-AC68W as well?

Also is it recommended to DISABLE "beamforming" w/ Merlin's 43 FW (as w/ Asus stock firmware) or can it be kept ENABLED?

 

[RMerlin]

I assume this will work with the RT-AC68W as well?

Yes. For all intent and purposes, the U, R and W SKUs are all the exact same hardware.

The only exception is the recently released RT-AC56S, which is a cut-down version (single core, only 128 MB RAM). This one is different from the other RT-AC SKUs.

Also is it recommended to DISABLE "beamforming" w/ Merlin's 43 FW (as w/ Asus stock firmware) or can it be kept ENABLED?

This will depend on your clients and your specific environment. In general, things are more stable without beamforming, but if you do have some dark spots you can try enabling it to see if it helps.

 

[jim769]

I get "it's now broken with Comcast" reported with every single new release, even when there was zero change to IPv6 code (like is the case with 374.43). Comcast's IPv6 support is simply quirky, the issue isn't the new firmware, it's the fact your router was rebooted, and it has trouble getting a new IPv6 connection established with Comcast - you would have experienced the same issue after a router reboot. Try a power cycle of your modem to fix it, that usually works.

I have been working with this all night my 68U will no longer obtain a IPv6 address no matter what firmware I flash on to it. Strange thing is it worked fine till I installed 43_0 I am in no way blaming the firmware but I can say this I hooked up my N66U and flashed 43_0 and it workers perfect instant IPv6 working great. Then I went back to the 68U and nothing no matter what I do it will not get v6. Back to N66 and all is perfect. I know strange indeed but this is what happened here maybe something has gone wonky with the 68U I don't know.

I also noticed the N66U has a much better signal output on the 2.4 ghz band much better so maybe my 68U is going bad. Thanks for your update and effort.

 

[RMerlin]

I have been working with this all night my 68U will no longer obtain a IPv6 address no matter what firmware I flash on to it. Strange thing is it worked fine till I installed 43_0 I am in no way blaming the firmware but I can say this I hooked up my N66U and flashed 43_0 and it workers perfect instant IPv6 working great. Then I went back to the 68U and nothing no matter what I do it will not get v6. Back to N66 and all is perfect. I know strange indeed but this is what happened here maybe something has gone wonky with the 68U I don't know.

I also noticed the N66U has a much better signal output on the 2.4 ghz band much better so maybe my 68U is going bad. Thanks for your update and effort.

Did you power off your modem for at least 5 mins when switching router? This is necessary with cable modems as they will usually only allocate leases to the first MAC that requests one from them. So if you swap routers without doing so, Comcast will reject requests from the new router.

 

[jim769]

Did you power off your modem for at least 5 mins when switching router? This is necessary with cable modems as they will usually only allocate leases to the first MAC that requests one from them. So if you swap routers without doing so, Comcast will reject requests from the new router.

Yes i did all that as i have been through this comcrap IPv6 issues many times before. Full factory resets complete reconfigure from scratch the whole nine yards. As stated no matter what i try or do the 68U will not get v6 funny the N66 obtains v6 instantly as soon as i reboot the modem then router.

I will look into this further tomorrow i have to work in the morning and have to hit the hay for tonight. But i am not sure what more i can try or do that i have not already done over the last 4 hours of playing with it.

 

[HawkInOz]

374.43 - Bad news with a guest network

This release blew up my RT-N66U. Could not access the web interface. Pings to the router's gateway address started timing out or taking 6+ ms instead of the normal "<1ms". I could not restore settings I saved right before upgrading from 374.42. The restore appeared to work, but random settings were restored while others were not. It was too much of a mess, so I did a factory reset which seemed to work. I started re-entering settings - mostly DHCP reservations for my devices and enabling SSH. As soon as I re-created my Guest Network, it blew up again. I again could not access the web interface, nor could I SSH into the router, and pings to the router became delayed or dropped entirely. I turned the router off and back on and managed to get into the web interface just long enough to disable the guest network, and things got right back to normal. There is something very broken with this release and a guest network. Mine was created on the 2.4GHz side. It was the only one. I'm shot from hours working on this, and will pick it up again after some sleep.

 

[avi68]

Hello everyone ,

Is it necessary to wipe when going to this build? I'm on 374.42 on my n66u. I have not wiped from my last two firmware upgrades, so that is why I'm asking.

Thanks again.