pinging local network some 100ms+ latency spikes

[ViviTheMage]

C:\Users\blabla>ping 10.10.5.1 -t

Pinging 10.10.5.1 with 32 bytes of data:
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
[B]Reply from 10.10.5.1: bytes=32 time=59ms TTL=64[/B]
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
[B]Reply from 10.10.5.1: bytes=32 time=52ms TTL=64[/B]
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
[B]Reply from 10.10.5.1: bytes=32 time=132ms TTL=64[/B]
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time=12ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
[B]Reply from 10.10.5.1: bytes=32 time=53ms TTL=64[/B]
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
[B]Reply from 10.10.5.1: bytes=32 time=26ms TTL=64[/B]
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time=7ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
[B]Reply from 10.10.5.1: bytes=32 time=234ms TTL=64[/B]
Reply from 10.10.5.1: bytes=32 time<1ms TTL=64
Reply from 10.10.5.1: bytes=32 time=1ms TTL=64

Ping statistics for 10.10.5.1:
    Packets: Sent = 29, Received = 29, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 234ms, Average = 19ms
Control-C
^C
C:\Users\blabla>

This is very weird, I am unsure why I get these random 50-200ms spikes!

I am running a linksys e4200v1 with tomato...both PC and server are connected to it.

I am pinging my router....10.10.5.1.

 

[spidey07]

A router's job is to route packets, not respond to your pings. Try between both machines.

 

[ViviTheMage]

That looks good...
I was thinking of changing my WAN link to come in to my router via powerline because my cable modem is so far away, do you think i'd run into latency issues by doing that?

 

[Emulex]

over wifi? that's normal. It's called interference and frequency hopping etc. First generation 5ghz/N was far simpler than current generation.

Laws require modems to implement "safe" channel use such as hopping to another channel. The Latency incurred to tell everyone to jump, find another channel. man. I think that's why folks like ASUS just NOOP'd those functions in ASUSWRT. too hard for them to get working for the masses.

 

[ViviTheMage]

no, this is over LAN, connected to the router.

I am now wondering if i'd be OK to have my internet run through my powerline adapters, because my SO hates this 100 foot cat5e I have run along the floor....or would I have some added latency/loss by doing so?

 

[spidey07]

A 100 foot cable is out of spec if it's stranded, but you would likely see errors and retransmissions if that was the cause and adds immeasurable latency due to length. As in you'd only be able to measure it in the nano seconds due to speed of light in the medium.

Ping between machines, you should never really see much more than 1 or 2 ms unless the host is busy. Routers are poor things to ping for latency as that hits the router processor.

 

[ViviTheMage]

100 feet is not out of spec, 300+ would be ...

My main question now is getting my WAN over powerline, would that be OK, or does powerline add some latency/packet loss?

 

[spidey07]

100 is out of spec for STRANDED cable, ie a patch cord. Solid terminated in keystone jacks it is within spec.

A proper cat 5e run is always going to offer less latency because of modulation and noise with powerline. You can try it though, that would point to your cable being the problem

 

[ViviTheMage]

I'll give it a shot.

 

[Emulex]

don't forget sometimes its just stupid stuff like the cable got pinched.

many intel nic's can do extensive diagnostics, or if you have a CNA you get some hardcore diagnostics.

Why not try the obvious? Use a different pc/nic/wire?

does this happen with a 14 foot cat6 cable?

does this happen on a different router port?

Why not use a $20 8-port gigabit (rosewill) switch in between? This offloads a router from switching. Routers that switch do not make great switches.

Check for cat/dog damage to wires or yank - ends coming loose. Never make your own cables, buy pre-made That's how the military works.