Asuswrt-Merlin 376.44 is out

[ColinTaylor]

Utorrent with upnp works fine for me and i do have a bunch of port forwards set to the same system.

Just to clarify, I wasn't suggesting he not use port forwarding at all, rather that he shouldn't setup manual port forwarding rules for his torrent programs when they are setup to use UPNP (use one method or the other). Manual port forwarding for other applications would be fine.

 

[xcrunner529]

Anyone unable to see hostnames now after upgrading to 44? It could have been something I did, but I can't figure it out. The network map shows clients as 0 and when I click on it and it tries searching it never finds anything.

I am using HTTPS only if that helps. The interface is very slow, usually requiring manual browser refreshes just to load some pages using just HTTPS, I might add. N66U here.

 

[cvx01]

Yes, it is very regrettable but it does look like .43 is the end of the road if wireless performance on n66u is important. I'm grateful to Merlin for 43 as I believe it is pretty secure, does most of the tricks and I don't think there is much in 44 to get excited about.

If only it didn't regularly and simultaneously disconnect all our Kindles.

Bob.

I had the same "disconnect" issues with .43 on various devices. Switched back to .42 and been flawless for 14 days now since I reverted.

 

[bill1228]

Yes, it is very regrettable but it does look like .43 is the end of the road if wireless performance on n66u is important. I'm grateful to Merlin for 43 as I believe it is pretty secure, does most of the tricks and I don't think there is much in 44 to get excited about.

If only it didn't regularly and simultaneously disconnect all our Kindles.

Bob.

I also had wireless issues on my N66U with 43. Yes I did a reset and new config. Everything would work fine until I would watch Hulu. When watching a movie about 20 minutes into the move would start getting lots of buffering messages with pauses in the movie of course. When I would check speed to Internet I would be down to around 1Mbps down. Rebooting router would run correctly for again about 20 minutes then Hulu would start buffering again. Dropping back to 42 corrected this issue. I did not bother to try trouble shooting problem as I knew that 42 worked fine.

I am now on 44 and things, including Hulu, seem to be working fine. I did see a slight drop in wireless signal but does not seem to be effecting my speed in these lower areas in my small, 1800 sq foot, 1 1/2 story, house. Router in basement where Uverse comes in rather then 1st floor.

As an aside, we are one of the "lucky" ones in SE Michigan that got a flooded basement from 6 inches of rain in a short time frame. We had 21 inches in the basement at one point coming from floor drains connected to sewer system. Now testing how well the router works in a very humid environment. Have fans running to help dry out as well as humidifier. Have clean up crew coming to deal with sanitation and mold issues. Expensive They will be bringing big humidifiers and lots more fans.

--bill

 

[mackworth]

You should do speed tests..
50% signal could be very good or very bad... it could also be that 50 signal on 44 is faster than 60 on 43. Your test does mean anything since in all positions the signal is valid and we know nothing about speeds. To test speeds don't look at windows bu measure the time taken to transfer a single file or use a specific tool.

Thats a good point. If I do this again I will try and do a speed test. I am probably just going to stick with 44 though, since I don't really care that much about wireless range/speed. Most of my wireless clients just need basic video streaming and internet access and it looks like I am still capable of that. Maybe I would care more if I lived in a bigger place.

 

[Deleted member 22229]

Hey Bill good luck with the basement I also live in SE Michigan we were lucky we didn't have any damage but many did what a mess that was one hell of a rain storm. Sorry this post was off topic.

 

[kibosh]

Unfortunately I have had to return to .43 from .44. Every couple of days I would lose my internet connection completely. I think it occurs when the lease is up with the ISP. Something similar used to happen with older versions of the firmware and it seems to have returned with this version.

Here is what was in my log:

Aug 16 09:33:46 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 09:33:46 miniupnpd[724]: Failed to get IP for interface eth0
Aug 16 09:33:46 miniupnpd[724]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Aug 16 09:33:46 dnsmasq[657]: read /etc/hosts - 5 addresses
Aug 16 09:33:46 dnsmasq[657]: read /etc/hosts.dnsmasq - 3 addresses
Aug 16 09:33:46 dnsmasq-dhcp[657]: read /etc/ethers - 3 addresses
Aug 16 09:33:46 dnsmasq[657]: using nameserver 64.71.255.204#53
Aug 16 09:33:46 dnsmasq[657]: using nameserver 64.71.255.198#53
Aug 16 09:33:49 WAN Connection: ISP's DHCP did not function properly.
Aug 16 09:33:49 stop_nat_rules: apply the redirect_rules!
Aug 16 09:33:50 dnsmasq[657]: exiting on receipt of SIGTERM
Aug 16 09:33:50 dnsmasq[2084]: started, version 2.72test3 cachesize 1500
Aug 16 09:33:50 dnsmasq[2084]: warning: interface ppp1* does not currently exist
Aug 16 09:33:50 dnsmasq[2084]: asynchronous logging enabled, queue limit is 5 messages
Aug 16 09:33:50 dnsmasq-dhcp[2084]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Aug 16 09:33:50 dnsmasq[2084]: read /etc/hosts - 5 addresses
Aug 16 09:33:50 dnsmasq[2084]: read /etc/hosts.dnsmasq - 3 addresses
Aug 16 09:33:50 dnsmasq-dhcp[2084]: read /etc/ethers - 3 addresses
Aug 16 09:33:50 dnsmasq[2084]: using nameserver 64.71.255.204#53
Aug 16 09:33:50 dnsmasq[2084]: using nameserver 64.71.255.198#53
Aug 16 09:36:41 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 09:36:41 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:25 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:25 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:29 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:29 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address

 

[jim769]

Unfortunately I have had to return to .43 from .44. Every couple of days I would lose my internet connection completely. I think it occurs when the lease is up with the ISP. Something similar used to happen with older versions of the firmware and it seems to have returned with this version.

Here is what was in my log:

Aug 16 09:33:46 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 09:33:46 miniupnpd[724]: Failed to get IP for interface eth0
Aug 16 09:33:46 miniupnpd[724]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Aug 16 09:33:46 dnsmasq[657]: read /etc/hosts - 5 addresses
Aug 16 09:33:46 dnsmasq[657]: read /etc/hosts.dnsmasq - 3 addresses
Aug 16 09:33:46 dnsmasq-dhcp[657]: read /etc/ethers - 3 addresses
Aug 16 09:33:46 dnsmasq[657]: using nameserver 64.71.255.204#53
Aug 16 09:33:46 dnsmasq[657]: using nameserver 64.71.255.198#53
Aug 16 09:33:49 WAN Connection: ISP's DHCP did not function properly.
Aug 16 09:33:49 stop_nat_rules: apply the redirect_rules!
Aug 16 09:33:50 dnsmasq[657]: exiting on receipt of SIGTERM
Aug 16 09:33:50 dnsmasq[2084]: started, version 2.72test3 cachesize 1500
Aug 16 09:33:50 dnsmasq[2084]: warning: interface ppp1* does not currently exist
Aug 16 09:33:50 dnsmasq[2084]: asynchronous logging enabled, queue limit is 5 messages
Aug 16 09:33:50 dnsmasq-dhcp[2084]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Aug 16 09:33:50 dnsmasq[2084]: read /etc/hosts - 5 addresses
Aug 16 09:33:50 dnsmasq[2084]: read /etc/hosts.dnsmasq - 3 addresses
Aug 16 09:33:50 dnsmasq-dhcp[2084]: read /etc/ethers - 3 addresses
Aug 16 09:33:50 dnsmasq[2084]: using nameserver 64.71.255.204#53
Aug 16 09:33:50 dnsmasq[2084]: using nameserver 64.71.255.198#53
Aug 16 09:36:41 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 09:36:41 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:25 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:25 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:29 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:29 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address

Yep it seems the new version is not very popular most have either rolled back or avoided it all together.

 

[Ronv42]

Some led lights stay on on AC87R when USB3 port is used

I am moving my asusware/opt from a usb 2.0 thumb drive to a usb 3.0 thumb drive.

Now the issue I have been able to reproduce is when there is a device in the USB 3.0 port the one of the two used lan port lights stay on and so does the wan port light. I can move the cables around to 3 and 4 and again either 3 or 4 stays on along with the wan port. If I take out drive from the USE 3.0 port all lights go out a few moments after the reboot.

For those that play with hot plugging a drive into this router, just a warning the mount point of the USB 2.0 device moved from sda1 to sdc1 when I hot plugged into the USB 3.0 port causing my testing of Squid and Privoxy to fail. The USB 3.0 device mounted as sdb1. All corrected after a reboot. USB 2.0 port returned to sda1 and USB 3.0 became sdb1.

 

[ColinTaylor]

For those that play with hot plugging a drive into this router, just a warning the mount point of the USB 2.0 device moved from sda1 to sdc1 when I hot plugged into the USB 3.0 port causing my testing of Squid and Privoxy to fail. The USB 3.0 device mounted as sdb1. All corrected after a reboot. USB 2.0 port returned to sda1 and USB 3.0 became sdb1.

It has always been the case that the name of the mount point can change depending on how many USB devices you have and where/when they are plugged in. To avoid any problems it is best to give each USB device a volume label. That way the name of the mount point is always the same.

 

[Ronv42]

It has always been the case that the name of the mount point can change depending on how many USB devices you have and where/when they are plugged in. To avoid any problems it is best to give each USB device a volume label. That way the name of the mount point is always the same.

I usually do label when I have a more permanent configuration but this was just doing a hot plug with an existing USB device already mounted. Most folks don't label with out of box solutions when they just want to plug in and grab files, they just leave the drives as they came in the package. Haven't had this happen before with Tomato on my N66U or N16's. Oh well.

I will say one thing. The USB 3.0 flash drive is a heck of a lot faster than the USB 2.0 version. Haven't captured real stats yet but when I copied from my cifs backup of the USB 2.0 device to the USB 3.0 device it took less than a minute vs well over 3 minutes last time I restored the backup to USB 2.0.

 

[alabrand]

My issue with the speed suddenly plunging and taking an hour to return to normal before doing the same an hour later has gone away. No idea what caused it or what fixed it but I'm glad either way.

 

[Sniegov]

Unfortunately I have had to return to .43 from .44. Every couple of days I would lose my internet connection completely. I think it occurs when the lease is up with the ISP. Something similar used to happen with older versions of the firmware and it seems to have returned with this version.

Here is what was in my log:

Aug 16 09:33:46 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 09:33:46 miniupnpd[724]: Failed to get IP for interface eth0
Aug 16 09:33:46 miniupnpd[724]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Aug 16 09:33:46 dnsmasq[657]: read /etc/hosts - 5 addresses
Aug 16 09:33:46 dnsmasq[657]: read /etc/hosts.dnsmasq - 3 addresses
Aug 16 09:33:46 dnsmasq-dhcp[657]: read /etc/ethers - 3 addresses
Aug 16 09:33:46 dnsmasq[657]: using nameserver 64.71.255.204#53
Aug 16 09:33:46 dnsmasq[657]: using nameserver 64.71.255.198#53
Aug 16 09:33:49 WAN Connection: ISP's DHCP did not function properly.
Aug 16 09:33:49 stop_nat_rules: apply the redirect_rules!
Aug 16 09:33:50 dnsmasq[657]: exiting on receipt of SIGTERM
Aug 16 09:33:50 dnsmasq[2084]: started, version 2.72test3 cachesize 1500
Aug 16 09:33:50 dnsmasq[2084]: warning: interface ppp1* does not currently exist
Aug 16 09:33:50 dnsmasq[2084]: asynchronous logging enabled, queue limit is 5 messages
Aug 16 09:33:50 dnsmasq-dhcp[2084]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Aug 16 09:33:50 dnsmasq[2084]: read /etc/hosts - 5 addresses
Aug 16 09:33:50 dnsmasq[2084]: read /etc/hosts.dnsmasq - 3 addresses
Aug 16 09:33:50 dnsmasq-dhcp[2084]: read /etc/ethers - 3 addresses
Aug 16 09:33:50 dnsmasq[2084]: using nameserver 64.71.255.204#53
Aug 16 09:33:50 dnsmasq[2084]: using nameserver 64.71.255.198#53
Aug 16 09:36:41 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 09:36:41 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:25 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:25 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:29 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:29 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address

Hi. It happened to me as well but you need only paste your proper mac address into field
and I know you can see it’s there sometimes but u need to re-type this again - sound stupid
but worked for me.

 

[Builder71]

Hi. It happened to me as well but you need only paste your proper mac address into field
and I know you can see it’s there sometimes but u need to re-type this again - sound stupid
but worked for me.

To my understanding that MAC field is only used if your ISP has forced their router equipment on you.
So they will only give you a WAN IP if it sees that specific MAC address.
You can clone that MAC address into your ASUS router for it to work as well.

My ISP doesn't care what stuff I use, so I can leave that MAC field empty.
(Thus effectively using the MAC from my RT-N66U WAN interface.)

Edit: Sniegov, your signature is showing a non existent FW version.

 

[Jobine]

Known issue in Asus's code, also happens with Italian. I think it was also mentioned earlier in this thread.


Can you elaborate? Make sure you are not trying to access the site in HTTPS.

I have several websites blocked via the firewall. with version 43 everything works, but with the 44 nothing is blocked.

 

[reddice]

Yep it seems the new version is not very popular most have either rolled back or avoided it all together.

I agree as I rolled back to 374.43 as the new version had terrible WiFi range on 5Ghz. Wireless range is more important than having the latest security features.

Still don't get how Merlin can be so cozy with the FCC allowing this. Maybe he should change the firmware so it does not look like the Asus firmware yes another type of DD-WRT or Tomato then he can do whatever he wants and screw the FCC stupid power reduction rules.

 

[Deleted member 22229]

I agree as I rolled back to 374.43 as the new version had terrible WiFi range on 5Ghz. Wireless range is more important than having the latest security features.

Still don't get how Merlin can be so cozy with the FCC allowing this. Maybe he should change the firmware so it does not look like the Asus firmware yes another type of DD-WRT or Tomato then he can do whatever he wants and screw the FCC stupid power reduction rules.

None of this is Merlin's fault and if he did what you suggest then the FCC could ban third party firmware all together and force Asus to lock down the router so no third party firmware could be installed and no body wants that.

 

[Markmaster]

What information about my settings of router should I present for clever community that can help me with my god damn port forwarding?
Is any kind of tool that can test is specific port is open or not?


Sent from my iPhone using Tapatalk

 

[RMerlin]

I have several websites blocked via the firewall. with version 43 everything works, but with the 44 nothing is blocked.

I just tested it and it's working correctly for me.

Try disabling HW acceleration under LAN -> Switch Control.

 

[Builder71]

I agree as I rolled back to 374.43 as the new version had terrible WiFi range on 5Ghz. Wireless range is more important than having the latest security features.

Still don't get how Merlin can be so cozy with the FCC allowing this. Maybe he should change the firmware so it does not look like the Asus firmware yes another type of DD-WRT or Tomato then he can do whatever he wants and screw the FCC stupid power reduction rules.

None of this is Merlin's fault and if he did what you suggest then the FCC could ban third party firmware all together and force Asus to lock down the router so no third party firmware could be installed and no body wants that.

We all know this is not Merlin's fault, but both have a point.

What annoys me the most is that ASUS acts like the FCC has global jurisdiction.
That s*cks!