I made a post a few weeks back and still have issues..
Running it in both 2.4 and 5 mode, before I was using a dlink adapter (so only 2.4). Got a 5ghz board and performance is still bad, so probably not interference (link score 100 at inssider).
I think this exemplifies the issue:
Reply from 192.168.1.1: bytes=32 time=432ms TTL=64
Reply from 192.168.1.1: bytes=32 time=462ms TTL=64
Reply from 192.168.1.1: bytes=32 time=469ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=453ms TTL=64
Reply from 192.168.1.1: bytes=32 time=361ms TTL=64
Reply from 192.168.1.1: bytes=32 time=365ms TTL=64
Reply from 192.168.1.1: bytes=32 time=398ms TTL=64
This is also not constant - now for example my ping -t is returning 1s with some 40-50 mixed in.
Has anyone seen something like this? Is there anything I can do config/firmware-wise?
I'm currently running the latest merlin. The issue also happened on stock. It started happening after I left it turned off for a couple weeks (never noticed it before then).
Hopefully my router isn't starting to die on me, but this behavior does not look like that..
Willing to try other firmwares/configs or simple tests as needed
EDIT: Ah, usually have ~10 devices connected, including a couple new chromecasts. The chromecasts were also added to the network after I turned the router back on, so I guess they could have something to do with it... maybe?
Running it in both 2.4 and 5 mode, before I was using a dlink adapter (so only 2.4). Got a 5ghz board and performance is still bad, so probably not interference (link score 100 at inssider).
I think this exemplifies the issue:
Reply from 192.168.1.1: bytes=32 time=432ms TTL=64
Reply from 192.168.1.1: bytes=32 time=462ms TTL=64
Reply from 192.168.1.1: bytes=32 time=469ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=453ms TTL=64
Reply from 192.168.1.1: bytes=32 time=361ms TTL=64
Reply from 192.168.1.1: bytes=32 time=365ms TTL=64
Reply from 192.168.1.1: bytes=32 time=398ms TTL=64
This is also not constant - now for example my ping -t is returning 1s with some 40-50 mixed in.
Has anyone seen something like this? Is there anything I can do config/firmware-wise?
I'm currently running the latest merlin. The issue also happened on stock. It started happening after I left it turned off for a couple weeks (never noticed it before then).
Hopefully my router isn't starting to die on me, but this behavior does not look like that..
Willing to try other firmwares/configs or simple tests as needed
EDIT: Ah, usually have ~10 devices connected, including a couple new chromecasts. The chromecasts were also added to the network after I turned the router back on, so I guess they could have something to do with it... maybe?
Last edited: