Asuswrt-Merlin 3.0.0.4.372.30_2

[Etz]

Both issues already fixed in 372.30_2.

Did I mention that you are awesome...

 

[zenmota]

Based on the error message, it sounds like this function gets called while one of these lists is empty.

Thanks, this gives me a starting point to look into it.

The most common invalid names that I see are names that contain quotes, or non latin characters (i.e. people using cyrillic in device names). This also applies to the DHCP reservation page of the router. I doubt that's what is causing your issue in this case, but you can check that page too if you had manually entered device names there.

Thanks for looking into it. It's not a big deal, as the router seems to be working fine and wireless seems better. Just that the client list use to come up really quick, now it doesn't or I have click refresh several times.

The only DHCP reservation I have is the network printer and its name is HP Printer.

Thanks again...

 

[Etz]

Can confirm, OpenVPN works again with Static pre-shared key.

 

[MonkY]

Just updated to 3.0.0.4.372.30_2 and the first thing i've noticed is a really, really bad one. All my pings have gone from 1ms to 7-10ms (in LAN). Also, on wan, my testing websites have gone from 5ms to 20ms and above. And it's very erratic (before i got all the time 4-5-4-5-4ms, now it's like 15-25-18-20-30-12ms).

It's something that is forcing me to downgrade... or is there anything else i could try before getting back to an older version?

What router model?

Sorry i forgot to mention it: RT-AC66U
Tried a reboot... same high pings...

 

[RMerlin]

Sorry i forgot to mention it: RT-AC66U
Tried a reboot... same high pings...

Known issue in the 3xx code:

http://forums.smallnetbuilder.com/showthread.php?t=11514

 

[BMWDude49120]

Merlin, I have an RT-AC66U and have loaded your latest build 3.0.0.4.372.30_2. I've noticed that HW Acceleration is enabled even when I also have IPV6 enabled, which is new in this version. However, this causes my system log to constantly log the following:

Jul 7 19:56:34 kernel: printk: 145 messages suppressed.
Jul 7 19:56:34 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:56:41 kernel: printk: 5 messages suppressed.
Jul 7 19:56:41 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:56:45 kernel: printk: 24 messages suppressed.
Jul 7 19:56:45 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:56:50 kernel: printk: 19 messages suppressed.
Jul 7 19:56:50 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:56:54 kernel: printk: 38 messages suppressed.
Jul 7 19:56:54 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:57:00 kernel: printk: 629 messages suppressed.
Jul 7 19:57:00 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:57:04 kernel: printk: 7 messages suppressed.
Jul 7 19:57:04 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:57:10 kernel: printk: 332 messages suppressed.
Jul 7 19:57:10 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:57:14 kernel: printk: 178 messages suppressed.
Jul 7 19:57:14 kernel: protocol 0000 is buggy, dev eth0

If I manually disable HW Acceleration, these entries stop completely. For now, I have just left HW Acceleration disabled, since I want to leave IPV6 enabled. I just wanted to let you know about this in case anyone else runs into the same issue.

 

[RogerSC]

Merlin, I have an RT-AC66U and have loaded your latest build 3.0.0.4.372.30_2. I've noticed that HW Acceleration is enabled even when I also have IPV6 enabled, which is new in this version. However, this causes my system log to constantly log the following:

Jul 7 19:56:34 kernel: printk: 145 messages suppressed.
Jul 7 19:56:34 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:56:41 kernel: printk: 5 messages suppressed.
Jul 7 19:56:41 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:56:45 kernel: printk: 24 messages suppressed.
Jul 7 19:56:45 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:56:50 kernel: printk: 19 messages suppressed.
Jul 7 19:56:50 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:56:54 kernel: printk: 38 messages suppressed.
Jul 7 19:56:54 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:57:00 kernel: printk: 629 messages suppressed.
Jul 7 19:57:00 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:57:04 kernel: printk: 7 messages suppressed.
Jul 7 19:57:04 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:57:10 kernel: printk: 332 messages suppressed.
Jul 7 19:57:10 kernel: protocol 0000 is buggy, dev eth0
Jul 7 19:57:14 kernel: printk: 178 messages suppressed.
Jul 7 19:57:14 kernel: protocol 0000 is buggy, dev eth0

If I manually disable HW Acceleration, these entries stop completely. For now, I have just left HW Acceleration disabled, since I want to leave IPV6 enabled. I just wanted to let you know about this in case anyone else runs into the same issue.

Here's a post that might help you:

http://forums.smallnetbuilder.com/showpost.php?p=45870&postcount=610

 

[RMerlin]

Merlin, I have an RT-AC66U and have loaded your latest build 3.0.0.4.372.30_2. I've noticed that HW Acceleration is enabled even when I also have IPV6 enabled, which is new in this version.

Yes, they only disable CTF when IPv6 is running if you are on an RT-AC56U or RT-AC68U now.

 

[erwinquek]

My ISP ipv6 diections is Autoconfiguration (SLAC/DHCPv6)” for Dual-Stack setting. My way I can config this on RT-N66U?

 

[BMWDude49120]

Here's a post that might help you:

http://forums.smallnetbuilder.com/showpost.php?p=45870&postcount=610

Unfortunately that isn't the issue, as I have all of the VPN features disabled. I only get these errors in the log if I have both HW Acceleration (CTS) and IPV6 enabled. If I leave IPV6 enabled and disable CTS, the errors stop.

 

[MonkY]

Known issue in the 3xx code:

http://forums.smallnetbuilder.com/showthread.php?t=11514

Downgraded to RT-AC66U_3.0.0.4_270.26b and the ping issues are solved. So it's RT-AC66U_3.0.0.4_372.30_2 fault for sure.

Pings from LAN went from 10-15ms to <1 ms and external pings from 20-30ms to 2-3ms. So 372.30 is unusable. I wouldn't even release a router firmware with such issues. Even a $10 router works better... so i recommend everyone not to use it.

 

[cmillar6]

Downgraded to RT-AC66U_3.0.0.4_270.26b and the ping issues are solved. So it's RT-AC66U_3.0.0.4_372.30_2 fault for sure.

Pings from LAN went from 10-15ms to <1 ms and external pings from 20-30ms to 2-3ms. So 372.30 is unusable. I wouldn't even release a router firmware with such issues. Even a $10 router works better... so i recommend everyone not to use it.

I agree, I have not been able to use a wired connection on my AC66u for months.
However, remember the ping issue only affects wired clients, wireless seems ok.

 

[MonkY]

However, remember the ping issue only affects wired clients, wireless seems ok.

That's not entirely correct. Because your WAN must be wired... therefore any external ping will be affected. Any website will respond slower (even 10 times slower), and that's really bad.

 

[oshia86]

Well, I would love to give this a try, but my 4th AC66U died this weekend. Looks like i'll be switching to something else.

 

[SkyNet]

It's weird... in the clear build 372 from asus ping jumps only with jumbo frames in router switch like in other firmwares, but in Merlin build 372.30 ping jumps again like in 354. Anyway the issue with ping exists again.

 

[RMerlin]

As I said in that other thread, this is a known issue of all RT-AC66U builds from the 3.0.0.4.3xx series. Asus has already fixed it on their end, but they haven't made a new release with that fix yet, which is why 3.0.0.4.372.30 still has the issue.

Personally I don't think it's that big of a deal. I ran a firmware with that issue for months on my network, and even my VoIP was working fine despite it. I wouldn't run an older 270 build just because of this. 2-5 ms added to the average 30-50 ms ping you get from most sites won't make a noticeable difference.

 

[RMerlin]

That's not entirely correct. Because your WAN must be wired... therefore any external ping will be affected. Any website will respond slower (even 10 times slower), and that's really bad.

10x slower would imply that a 30 ms ping time would be increased to 300ms - this is nowhere THAT bad.

 

[netware5]

Downgraded to RT-AC66U_3.0.0.4_270.26b and the ping issues are solved. So it's RT-AC66U_3.0.0.4_372.30_2 fault for sure.

Pings from LAN went from 10-15ms to <1 ms and external pings from 20-30ms to 2-3ms. So 372.30 is unusable. I wouldn't even release a router firmware with such issues. Even a $10 router works better... so i recommend everyone not to use it.

I am running 270.26b on RT-N66U and looking forward upgrading to 370.30_2. So the question is: The "ping issue" is specific for RT-AC66U or happens on all Asus routers?

 

[RMerlin]

I am running 270.26b on RT-N66U and looking forward upgrading to 370.30_2. So the question is: The "ping issue" is specific for RT-AC66U or happens on all Asus routers?

Specific to RT-AC66U.

 

[damir]

RMerlin,

Thank you for great work.

My previous version on (RT-N66U) was: 3.0.0.4.270.26
I flashed successfully to 3.0.0.4_372.30_2.

Did i have to clear nvram?

After i flashed it, every setting was there, and i just rebooted the router.
Is this okay, or i have to clear to factory settings? (and re-configure everything?)

Also, i noticed while pinging goole.com or any other side using WinMTR, there is about 2-3% packet loss on first HOP. (Should i be concerned about this?)

Thank you!