Etz
Regular Contributor
Both issues already fixed in 372.30_2.
Did I mention that you are awesome...
Both issues already fixed in 372.30_2.
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.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.
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?
Sorry i forgot to mention it: RT-AC66UWhat router model?
Sorry i forgot to mention it: RT-AC66U
Tried a reboot... same high pings...
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.
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.
Here's a post that might help you:
http://forums.smallnetbuilder.com/showpost.php?p=45870&postcount=610
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.
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.
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.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.
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?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!