What's new

Latency Spikes With wireless Media bridge

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

compsmithit

New Around Here
RT-AC68U - Both
Firmware Version:384.4_2

Im having a bit of an issue with media bridge using the latest stable builds. I have 2x - 68U's about 25ft appart, one in Media bridge mode, one in AP mode connected on the 5GHz band. Im getting high ping spikes every 7-10 seconds.

Code:
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time<1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time<1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=326ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time<1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time<1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=522ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=696ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=2ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time<1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=994ms TTL=64

The 5GHz network is on channel 157 with the 20/40/80 Mhz width. I had also played with AI mesh on Asus Official firmware but latency on that was allover the place so I went back to Merlin.

The 2nd location is not able to have a wired backhaul. This is a recently reconfigured setup. Previously I had just one 68U in Media Bridge mode running legacy 380.69_2 connected to a TP Link Archer C9 running DD-WRT that I did not have these spikes. The C9 had to be removed after reboot issues crept up with DD-WRT. Before the reboot issues latency was stable on legacy firmware. I tried 384.4_2 but I remember all sorts of drop out issues. I figured purchasing another 68U and putting both on the latest stable would have a stable media bridge. Is there any recommendations on what I can try to stabilize the connection latency? I will try reverting both to a legacy firmware version if I cant get this worked out. Any help would be greatly appreciated.
 
Last edited:
RT-AC68U - Both
Firmware Version:384.4_2

Im having a bit of an issue with media bridge using the latest stable builds. I have 2x - 68U's about 25ft appart, one in Media bridge mode, one in AP mode connected on the 5GHz band. Im getting high ping spikes every 7-10 seconds.

Code:
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time<1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time<1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=326ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time<1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time<1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=522ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=696ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=2ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time<1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=1ms TTL=64
Reply from 192.168.0.252: bytes=32 time=994ms TTL=64

The 5GHz network is on channel 157 with the 20/40/80 Mhz width. I had also played with AI mesh on Asus Official firmware but latency on that was allover the place so I went back to Merlin.

The 2nd location is not able to have a wired backhaul. This is a recently reconfigured setup. Previously I had just one 68U in Media Bridge mode running legacy 380.69_2 connected to a TP Link Archer C9 running DD-WRT that I did not have these spikes. The C9 had to be removed after reboot issues crept up with DD-WRT. Before the reboot issues latency was stable on legacy firmware. I tried 384.4_2 but I remember all sorts of drop out issues. I figured purchasing another 68U and putting both on the latest stable would have a stable media bridge. Is there any recommendations on what I can try to stabilize the connection latency? I will try reverting both to a legacy firmware version if I cant get this worked out. Any help would be greatly appreciated.
Why didn't you buy a bridge , like the RP 68U , it works really well as a bridge , also as repeater or AP . Getting 450MBPS ON 2.4 and over 670MBPS on 5 , this at 40 ft distance with 3 walls between .
Just wish there was a Merlin FW for it .
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top