Upgrade to .29: huge jitter

[AxelV]

Hi there!

I'm new here, so let me introduce myself first: I'm Axel and I'm from the Netherlands. I have been reading these forums for a while now.
I recently updated my AC66U from Merlin's 260 build to the new 354.29 build. 260 was working like a charm (90+ days uptime), but with .29 I am experiencing a very weird problem.
A ping to my favourite Dutch techsite used to look like this:

Pinging tweakers.net [213.239.154.20] with 32 bytes of data:
Reply from 213.239.154.20: bytes=32 time=3ms TTL=57
Reply from 213.239.154.20: bytes=32 time=3ms TTL=57
Reply from 213.239.154.20: bytes=32 time=3ms TTL=57
Reply from 213.239.154.20: bytes=32 time=3ms TTL=57

Ping statistics for 213.239.154.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 3ms, Average = 3ms

But with the new firmware, it looks like this:

Pinging tweakers.net [213.239.154.20] with 32 bytes of data:
Reply from 213.239.154.20: bytes=32 time=14ms TTL=57
Reply from 213.239.154.20: bytes=32 time=13ms TTL=57
Reply from 213.239.154.20: bytes=32 time=15ms TTL=57
Reply from 213.239.154.20: bytes=32 time=11ms TTL=57

Ping statistics for 213.239.154.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 15ms, Average = 13ms

HW acceleration was disabled in both cases due to IPv6 (6rd).
I did a factory reset, but the problem persists. I do still get the full 100/100 speeds I used to get with the 260 build.
It's not a problem with my ISP, my neighbour still has these 3ms response times. IPv6 pings seem to have the same problem.

What can it be? All help is very much appreciated!

Axel

 

[RMerlin]

Know issue. Asus has since fixed it in the (not released yet) 3.0.0.4.372.

 

[AxelV]

Thanks! Do you know of a workaround or ETA?

 

[RMerlin]

Thanks! Do you know of a workaround or ETA?

No ETA yet.

They have given me permission to share the test build with people needing it, however it's an original Asus FW, so you will lose all the functionality of Asuswrt-Merlin if you use it.

If you still want to use it anyway let me know, and I'll reupload it to Mediafire.

 

[AxelV]

No ETA yet.

They have given me permission to share the test build with people needing it, however it's an original Asus FW, so you will lose all the functionality of Asuswrt-Merlin if you use it.

If you still want to use it anyway let me know, and I'll reupload it to Mediafire.

I would really like that, the Asus FW will do for the time being I suppose.

 

[doubleroll]

No ETA yet.

They have given me permission to share the test build with people needing it, however it's an original Asus FW, so you will lose all the functionality of Asuswrt-Merlin if you use it.

If you still want to use it anyway let me know, and I'll reupload it to Mediafire.

Please share if at all possible. Thx!

 

[jlsenter1]

Jitter on 354.29

I have been a Merlin user for virtually all releases. I have notice what appears to be the same problem. What version of Merlin can I roll back to eliminate?

Regards,

 

[supe]

Is the rt-n66u affected and is there a fix too? please share if it is.

Thanks.

 

[RMerlin]

I have been a Merlin user for virtually all releases. I have notice what appears to be the same problem. What version of Merlin can I roll back to eliminate?

Regards,

3.0.0.4.270.26b is fine. The issue was introduced in 354.27.

 

[RMerlin]

Is the rt-n66u affected and is there a fix too? please share if it is.

Thanks.

No, the issue is specific to the RT-AC66U. If you ping your router's IP on an RT-N66U it should give you a ping time equal or lower than 1ms.

 

[RMerlin]

See this post for the link to the Asus beta firmware that resolves the issue on the RT-AC66U.

Remember: this is a BETA firmware. Other stuff might be broken/unfinished yet. I recommend people stick to 354 if the issue isn't causing them any problem.

 

[bodean]

When will we see a Merlin FW update to fix this issue?

 

[Magnus33]

There is new firmware up now on the asus site as of two days ago.

asus rt-n66u 3.0.0.4.370

 

[lilstone87]

When will we see a Merlin FW update to fix this issue?

Probably when there is a official release from asus, unless he ask for the source code, and asus agree's to give it to him.

 

[lilstone87]

There is new firmware up now on the asus site as of two days ago.

asus rt-n66u 3.0.0.4.370

They are talking about the AC66U, as this isn't an issue on the N66U. Also Merlin mention this issue was fixed in a .372 beta for the AC66U. As of right now there isn't a .370 release for the AC66U, and if there was one probably wouldn't help. As stated the issue was addressed in a newer beta firmware of .372.

 

[Magnus33]

No caffeine and posted in wrong thread..whoops!!

 

[dombera]

Can't wait for Merlin's 3.0.0.4.370 or 3.0.0.4.372 for RT-N66U

 

[bluepoint]

Can't wait for Merlin's 3.0.0.4.370 or 3.0.0.4.372 for RT-N66U

That would be 3.0.0.4.370.30 or 3.0.0.4.372.31 versions for RMerlin's.

 

[m00ster]

I am running the latest merlin firmware for the AC66R and do not have the jitter issue:

Pinging 172.20.0.1 with 32 bytes of data:
Reply from 172.20.0.1: bytes=32 time=1ms TTL=64
Reply from 172.20.0.1: bytes=32 time=1ms TTL=64
Reply from 172.20.0.1: bytes=32 time=1ms TTL=64
Reply from 172.20.0.1: bytes=32 time=1ms TTL=64

I am using the PCE-AC66 Wireless Adapter that links anywhere from 1.1Ghz to 1.3Ghz.

 

[seth_space]

I am running the latest merlin firmware for the AC66R and do not have the jitter issue:

Pinging 172.20.0.1 with 32 bytes of data:
Reply from 172.20.0.1: bytes=32 time=1ms TTL=64
Reply from 172.20.0.1: bytes=32 time=1ms TTL=64
Reply from 172.20.0.1: bytes=32 time=1ms TTL=64
Reply from 172.20.0.1: bytes=32 time=1ms TTL=64

I am using the PCE-AC66 Wireless Adapter that links anywhere from 1.1Ghz to 1.3Ghz.

Your pinging your local host.. ie your own machine.
Try other site like google.com