Hi, I am having insane lag spike(100ms to over 1500ms) between RBS50 and the main router RBR50. I have 2 satellites, both show this behavior. I tried a bunch of stuff I read about in these forums(factory reset, settings, etc) but it didn't help.
Devices connected directly to the RBR50 do not suffer from this lag, it's really when connected through one of the 2 satellites only, I could confirm this with my laptop by connecting it to all of them in sequence and testing the pings while directly connected throuh ethernet. RBR50 was perfect, while pinging through the RBS50 sohws the lag spike you can see below.
House is about 1200sq ft on 2 level. The signal is strong all over the house, backhaul shows Good. Daisy chain is activated, but I can see both RBS50 connect directly to the main router and do not use the daisy chain. So I take it their signal to RBR50 is strong. (one RBS is right below the RBR, so about 8 feet from it with one ceiling btw, the other is about 25 feet from the RBR50, also on the floor below.)
Here is a small ping sample:
eply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=762ms TTL=64
Reply from 192.168.0.1: bytes=32 time=101ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=79ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=66ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=56ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=18ms TTL=64
Reply from 192.168.0.1: bytes=32 time=15ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=123ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=572ms TTL=64
That kind of lag spike completly screw up online meeting as video and voice will lag and cut, then come back.
The problem wasn't there before the holidays, and I "think" I updated the firmware during that time to 2.7.3.22 during the holidays when I added a second satellite for the living room, so that might be it?
Does anyone has a rock solid firmware version they would recommend so that I can at least try that and see if it's the firmware that is the problem?
