Asuswrt-Merlin 374.42_2 is out

[matthew_eli]

This is the log about the device trying to register to GUEST wifi and then, after disabled and then renabled it, finally managing to do this (the mac address involved is a0:0b:ba:b6:d4:e6):

May 11 19:56:53 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:56:53 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:56:54 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:56:54 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:57:02 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:57:02 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:57:18 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:57:18 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:57:27 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:57:27 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:57:27 dnsmasq-dhcp[1112]: DHCPREQUEST(br0) 192.168.1.24 d0:22:be:35:a6:33 
May 11 19:57:27 dnsmasq-dhcp[1112]: DHCPACK(br0) 192.168.1.24 d0:22:be:35:a6:33 note3Mat
May 11 19:57:27 dnsmasq-dhcp[1112]: DHCPREQUEST(br0) 192.168.1.24 d0:22:be:35:a6:33 
May 11 19:57:27 dnsmasq-dhcp[1112]: DHCPACK(br0) 192.168.1.24 d0:22:be:35:a6:33 note3Mat
May 11 19:57:28 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:57:28 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:57:36 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:57:36 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:57:38 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) d0:22:be:35:a6:33 
May 11 19:57:38 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.24 d0:22:be:35:a6:33 
May 11 19:57:42 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) d0:22:be:35:a6:33 
May 11 19:57:42 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.24 d0:22:be:35:a6:33 
May 11 19:57:51 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) d0:22:be:35:a6:33 
May 11 19:57:51 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.24 d0:22:be:35:a6:33 
May 11 19:57:51 dnsmasq-dhcp[1112]: DHCPREQUEST(br0) 192.168.1.24 d0:22:be:35:a6:33 
May 11 19:57:51 dnsmasq-dhcp[1112]: DHCPACK(br0) 192.168.1.24 d0:22:be:35:a6:33 note3Mat
May 11 19:57:52 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) d0:22:be:35:a6:33 
May 11 19:57:52 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.24 d0:22:be:35:a6:33 
May 11 19:57:52 dnsmasq-dhcp[1112]: DHCPREQUEST(br0) 192.168.1.24 d0:22:be:35:a6:33 
May 11 19:57:52 dnsmasq-dhcp[1112]: DHCPACK(br0) 192.168.1.24 d0:22:be:35:a6:33 note3Mat
May 11 19:57:52 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:57:52 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:58:17 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:58:17 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:58:18 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:58:18 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:58:27 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:58:27 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:58:27 rc_service: httpd 595:notify_rc restart_wireless
May 11 19:58:30 kernel: device eth1 left promiscuous mode
May 11 19:58:30 kernel: br0: port 2(eth1) entering forwarding state
May 11 19:58:30 kernel: device eth2 left promiscuous mode
May 11 19:58:30 kernel: br0: port 3(eth2) entering forwarding state
May 11 19:58:30 kernel: device wl0.1 left promiscuous mode
May 11 19:58:30 kernel: br0: port 4(wl0.1) entering forwarding state
May 11 19:58:31 kernel: Interface wl0.1 doesn't exist
May 11 19:58:31 kernel: Interface eth2 doesn't exist
May 11 19:58:31 kernel: Interface eth1 doesn't exist
May 11 19:58:35 kernel: wl_module_init: passivemode set to 0x0
May 11 19:58:35 kernel: wl_module_init: txworkq set to 0x1
May 11 19:58:35 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
May 11 19:58:35 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
May 11 19:58:35 syslog: module proxyarp not found in modules.dep
May 11 19:58:35 kernel: device eth1 entered promiscuous mode
May 11 19:58:35 kernel: br0: topology change detected, propagating
May 11 19:58:35 kernel: br0: port 2(eth1) entering forwarding state
May 11 19:58:35 kernel: br0: port 2(eth1) entering forwarding state
May 11 19:58:35 kernel: device eth2 entered promiscuous mode
May 11 19:58:35 kernel: br0: topology change detected, propagating
May 11 19:58:35 kernel: br0: port 3(eth2) entering forwarding state
May 11 19:58:35 kernel: br0: port 3(eth2) entering forwarding state
May 11 19:58:52 dnsmasq-dhcp[1112]: DHCPREQUEST(br0) 192.168.1.24 d0:22:be:35:a6:33 
May 11 19:58:52 dnsmasq-dhcp[1112]: DHCPACK(br0) 192.168.1.24 d0:22:be:35:a6:33 note3Mat
May 11 19:58:57 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) 04:46:65:4b:84:4c 
May 11 19:58:57 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.11 04:46:65:4b:84:4c 
May 11 19:58:57 dnsmasq-dhcp[1112]: DHCPREQUEST(br0) 192.168.1.11 04:46:65:4b:84:4c 
May 11 19:58:57 dnsmasq-dhcp[1112]: DHCPACK(br0) 192.168.1.11 04:46:65:4b:84:4c SII-Eli
May 11 19:59:07 rc_service: httpd 595:notify_rc restart_wireless
May 11 19:59:10 kernel: device eth1 left promiscuous mode
May 11 19:59:10 kernel: br0: port 2(eth1) entering forwarding state
May 11 19:59:10 kernel: device eth2 left promiscuous mode
May 11 19:59:10 kernel: br0: port 3(eth2) entering forwarding state
May 11 19:59:10 kernel: Interface eth2 doesn't exist
May 11 19:59:10 kernel: Interface eth1 doesn't exist
May 11 19:59:14 kernel: wl_module_init: passivemode set to 0x0
May 11 19:59:14 kernel: wl_module_init: txworkq set to 0x1
May 11 19:59:14 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
May 11 19:59:14 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
May 11 19:59:14 syslog: module proxyarp not found in modules.dep
May 11 19:59:14 kernel: device eth1 entered promiscuous mode
May 11 19:59:14 kernel: br0: topology change detected, propagating
May 11 19:59:14 kernel: br0: port 2(eth1) entering forwarding state
May 11 19:59:14 kernel: br0: port 2(eth1) entering forwarding state
May 11 19:59:14 kernel: device eth2 entered promiscuous mode
May 11 19:59:14 kernel: br0: topology change detected, propagating
May 11 19:59:14 kernel: br0: port 3(eth2) entering forwarding state
May 11 19:59:14 kernel: br0: port 3(eth2) entering forwarding state
May 11 19:59:14 kernel: device wl0.1 entered promiscuous mode
May 11 19:59:14 kernel: br0: topology change detected, propagating
May 11 19:59:14 kernel: br0: port 4(wl0.1) entering forwarding state
May 11 19:59:14 kernel: br0: port 4(wl0.1) entering forwarding state
May 11 19:59:20 dnsmasq-dhcp[1112]: DHCPREQUEST(br0) 192.168.1.11 04:46:65:4b:84:4c 
May 11 19:59:20 dnsmasq-dhcp[1112]: DHCPACK(br0) 192.168.1.11 04:46:65:4b:84:4c SII-Eli
May 11 19:59:32 dnsmasq-dhcp[1112]: DHCPREQUEST(br0) 192.168.1.24 d0:22:be:35:a6:33 
May 11 19:59:32 dnsmasq-dhcp[1112]: DHCPACK(br0) 192.168.1.24 d0:22:be:35:a6:33 note3Mat
May 11 19:59:46 dnsmasq-dhcp[1112]: DHCPDISCOVER(br0) a0:0b:ba:b6:d4:e6 
May 11 19:59:46 dnsmasq-dhcp[1112]: DHCPOFFER(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:59:46 dnsmasq-dhcp[1112]: DHCPREQUEST(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 
May 11 19:59:46 dnsmasq-dhcp[1112]: DHCPACK(br0) 192.168.1.236 a0:0b:ba:b6:d4:e6 android-f8591c33874aff40

I forgot to mention the problem didn't occur with .41 firmware.

 

[Ford Prefect]

See the list of changes between 374.39 and 374.42, and decide for your self. The security fixes alone should be a good reason to upgrade.

THX Merlin for your response.

However, THIS looks like a feature downgrade to me:

374.41 (18-Apr-2014)
[...]
  - REMOVED: The Media server database location is no longer
             configurable, as we've switched to Asus's new 
             automatic location selection.
[...]

What's the logic implemented in this new feature?
I don't want to have this db ending up on the wrong disk. (seeing me just pull the
disk/stick with the DB on it - without knowing - when I leave home and capability
to stream media gets lost...not a real WAF).

 

[fink.nottle]

Traffic manager logs

I am using .40 on n66u, which works great. I recently started paying more attention to traffic manager's monthly usage logs since Comcast has implemented a new data cap in some areas. I noticed that these logs don't persist across reboots. The counters reset to zero after every reboot. Is this a known limitation ?

 

[tyvar1]

The Turbo button does not work with newer versions of the bootloader.

Aah Okey thank you!

Skickat från min SM-N9005 via Tapatalk

 

[bitbyter]

lost Ipv6

RT-N66U upgraded to 374.42. lost IPv6. Tried reboots and resetting, reverted back to 374.41 IPv6 working again. On Comcast in Denver area.

 

[Paxsat]

 transmission-daemon[2006]: Transmission 2.82 (14160) started (session.c:744)
May 12 13:49:20 transmission-daemon[2006]: RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:828)
May 12 13:49:20 transmission-daemon[2006]: RPC Server Adding address to whitelist: *.*.*.* (rpc-server.c:828)
May 12 13:49:20 transmission-daemon[2006]: RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:1035)
May 12 13:49:20 transmission-daemon[2006]: RPC Server Whitelist enabled (rpc-server.c:1039)
May 12 13:49:20 transmission-daemon[2006]: UDP Failed to set receive buffer: requested 4194304, got 237568 (tr-udp.c:78)
May 12 13:49:20 transmission-daemon[2006]: UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:83)
May 12 13:49:20 transmission-daemon[2006]: UDP Failed to set send buffer: requested 1048576, got 237568 (tr-udp.c:89)
May 12 13:49:20 transmission-daemon[2006]: UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:94)
May 12 13:49:20 transmission-daemon[2006]: UDP Failed to set receive buffer: requested 4194304, got 237568 (tr-udp.c:78)
May 12 13:49:20 transmission-daemon[2006]: UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:83)
May 12 13:49:20 transmission-daemon[2006]: UDP Failed to set send buffer: requested 1048576, got 237568 (tr-udp.c:89)
May 12 13:49:20 transmission-daemon[2006]: UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:94)
May 12 13:49:20 transmission-daemon[2006]: DHT Generating new id (tr-dht.c:310)

error in .42

 

[ryzhov_al]

error in .42

It's not an error, the Transmission inform user about some optimal settings when working on PC (and not optimal for embedde device). Just ignore it.

 

[oversim]

Hello!
Before .42 firmware, I was using a simple adblock method, based on a file of

address=/hostname2block/127.0.0.1

entries. I'm using a OpenVPN Server in N66U, and a squid proxy.

So, when I'm in office, I can access to blocked sites using my OpenVPN and my squid proxy.

BUT, with .42 firmware (and I suppose this is related to OpenVPN server update) at the 127.0.0.1 address OpenVPN redirect request to 192.168.1.1, that is N66U local IP.

So, every hostname to block, 127.0.0.1 redirect to 192.168.1.1 cause a login-password popup prompt of the used browser. And this is frustrating

 

[jim769]

42 has been rock solid for me here but I see this in the log this morning I have never been good a understanding what these entries mean can someone tell me if this is anything to worry about. I don't seem to be having any problems. Thanks Jim !

{\rtf1\ansi\ansicpg1252
{\fonttbl\f0\fnil\fcharset0 CourierNewPSMT;}
{\colortbl;\red255\green255\blue255;\red255\green255\blue255;\red71\green90\blue95;}
\deftab720
\pard\pardeftab720\sl420\partightenfactor0

\f0\fs22 \cf2 \cb3 \expnd0\expndtw0\kerning0
\outl0\strokewidth0 \strokec2 May 11 22:26:34 rc_service: dhcp6c-state 2365:notify_rc start_radvd\
May 11 22:26:34 rc_service: dhcp6c-state 2365:notify_rc start_httpd\
May 11 22:26:34 rc_service: waitting "start_radvd" via dhcp6c-state ...\
May 11 22:26:34 radvd[665]: attempting to reread config file\
May 11 22:26:34 radvd[665]: resuming normal operation\
May 11 22:26:35 RT-AC68U: start httpd\
May 11 22:27:50 rc_service: dhcp6c-state 2380:notify_rc start_radvd\
May 11 22:27:50 rc_service: dhcp6c-state 2380:notify_rc start_httpd\
May 11 22:27:50 rc_service: waitting "start_radvd" via dhcp6c-state ...\
May 11 22:27:50 radvd[665]: attempting to reread config file\
May 11 22:27:50 radvd[665]: resuming normal operation\
May 11 22:27:51 RT-AC68U: start httpd\
}

 

[RMerlin]

THX Merlin for your response.

However, THIS looks like a feature downgrade to me:

374.41 (18-Apr-2014)
[...]
  - REMOVED: The Media server database location is no longer
             configurable, as we've switched to Asus's new 
             automatic location selection.
[...]

What's the logic implemented in this new feature?

Asus completely redesigned that page. Merging both code versions together would have caused too many issues, so for the time being I reverted all my own changes and used theirs. Once I know this part is stable, I will look at possibly re-adding the location selection code in.

 

[InkyRag]

RT-N66U upgraded to 374.42. lost IPv6. Tried reboots and resetting, reverted back to 374.41 IPv6 working again. On Comcast in Denver area.

I am on Comcast in the Denver area and IPv6 is working fine with .42. This is by far the best build yet for my purposes.

 

[cmoskowitz]

Coming from 3.0.0.4.372.31

Hi Folks, I have the above build and am looking to upgrade to the latest. Are there any known gotchas or problems? Mainly I want to ensure my openvpn config stays intact as I rely on it daily. Thank You.

 

[gvellema]

You will have to do a factory reset with the .42 as well. All builds for the N66 are now by default the EM build. When you go from an non EM build to an EM build a reset is necessary.

I did just a reboot today and was able to update without problems from .38_2 to .42.0.

Thanks for your advice!

As the router is working now is a factory reset mandetory? Because I have the feeling everything is working well and I also see no strange things in the logging as well..

GV

 

[wolf12x]

I'm now on 374.42 thanx Merlin

I'm now on 374.42.
Thanx Merlin for the wonderful work you are doing

 

[RMerlin]

Hi Folks, I have the above build and am looking to upgrade to the latest. Are there any known gotchas or problems? Mainly I want to ensure my openvpn config stays intact as I rely on it daily. Thank You.

Coming from such an old version, you will probably need to do a factory default reset and manually reconfigure your router afterward, or else you might face stability issues, especially with wifi.

 

[RMerlin]

I did just a reboot today and was able to update without problems from .38_2 to .42.0.

Thanks for your advice!

As the router is working now is a factory reset mandetory? Because I have the feeling everything is working well and I also see no strange things in the logging as well..

Test your wireless, as this is what is usually showing problems after switching driver version like you did.

 

[clayhans]

Bug or No Bug?

Hi everyone,

374.42 is now available for download for all supported models. This release is mostly a maintenance version.

Highlights of this release:

• Merged with Asus's 374_5656 GPL, which included a few additional security fixes, and a reworked web interface for FTP/SMB management.
• Various user-contributed tweaks and fixes related to IPv6 were merged in.
• OpenVPN and miniupnpd were updated to their latest versions. The miniupnpd update includes some improvements to PCP support.

Additional details:
The 3G/4G USB support should work better in this build than the 374.41 build in the case of MIPS-based routers (N16/N66/AC66). That's because I didn't have the latest kernel code for these routers for 374.41, which means I was missing the new cdc_ncm driver which is now used by various devices. Let me know if you get better luck with this release with 3G/4G devices if they stopped working in 374.41.

Also, if you have a Mac and had issues with Time Machine in 374.41, let me know if it's fixed in this build. Some people reported that it stopped working in the previous release, yet if people were recompiling the firmware themselves it would work again. Mac users, also see if PCP now works properly for you (an Asuswrt-Merlin user reported an issue to the miniupnpd author, who has since fixed it - this build includes his fixed version).

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

MD5 checksums:

4bb39a92912c50efeb22eb84a210385b  RT-AC56U_3.0.0.4_374.42_0.trx
3e559f06d9a72dceb0a704b61ec40438  RT-AC66U_3.0.0.4_374.42_0.trx
fc40bb66ec5d541021da8b9777eebaa4  RT-AC68U_3.0.0.4_374.42_0.trx
f0171e4dbb7b55bce68e7ce124495cff  RT-N16_3.0.0.4_374.42_0.trx
8d30f1ee3e14dabcbd75bc5d3b22693b  RT-N66U_3.0.0.4_374.42_0.trx

Enjoy!

Thanks Merlin for all your great work.

Strange behavior! I installed 374.42 FW on my AC68U router and I have two Samsung smart TV’s on the home network. With the wireless Reducing USB 3.0 interference enabled my TV’s Allshare feature can see the router and the connected usb drives just fine. Now here is the rub, when I disable wireless Reducing USB 3.0 interference to get faster transfer speeds to my usb3 drive, than my TV’s don’t see the router anymore. The wifi still works on the TV’s but the Allshare feature doesn’t work and I can’t connect to my usb drives to use DLNA for my saved movies. Is this a bug? I believed the function worked fine on 374.41 FW. Because of this my transfer speeds to the usb drives is cut in half. I have tested this by turning the Reducing USB 3.0 off and on a few times. I did a complete Restore and factory default reset but the problem is still there. Any one any thoughts?

 

[cheatgamer100]

Hello merlin,

Thanks for the .42 firmware but I am having issues with IPv6 on my comcast connection. I was using .42_3alpha just fine from Adamm's website address that uploads new firmware and IPv6 works fine on there. But in .42 my GUI is showing an IPv6 address numbers (wan and LAN) are there but on my computers/tablets etc it says NO IPv6 address is running. comcast6.net doesn't detect one, test-ipv6.com either.

Thanks for all you do, hope this info helps.

PS: Comcast IPv6 native (Indiana area)

edit: Forgot to mention using AC68R model.

 

[Job314]

IRC Client

Hi Merlin,

you will add an IRC client in RT-N66u ? Like XCHAT for example

It's the only thing that is missing, then it would be perfect.

 

[cmoskowitz]

follow up to Merlin

That stinks, I don not use the wireless anymore (I moved to ubnt). But I do understand. I think this was the latest last summer :-/

Coming from such an old version, you will probably need to do a factory default reset and manually reconfigure your router afterward, or else you might face stability issues, especially with wifi.