Powerline and high latency

Bakedgoods · 22 Oct 2010 at 17:46

Evening all,

I've had a Powerline setup for a while and started gaming again recently and my ping is 60+ constantly, and pretty inconsistent.

Brother using wireless is consistently lower than me.

Do you think it's my roughly 2 years old powerline kit being poor, or is that the nature of the technology? (It's NETGEAR HD something, will dig out the model number)

It was the same in my old house and i've recently moved.

s-p · 22 Oct 2010 at 18:58

I don't see how powerline/homeplug technology should be slower than wireless.

My setup:
PC --> Router 1 --> Homeplug --> Router 2

These are the results of me pinging Router 2 from my PC.

Code:

C:\Users\Blah>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=4ms TTL=63
Reply from 192.168.1.254: bytes=32 time=4ms TTL=63
Reply from 192.168.1.254: bytes=32 time=6ms TTL=63
Reply from 192.168.1.254: bytes=32 time=5ms TTL=63

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

Bakedgoods · 22 Oct 2010 at 19:32

Brothers using wireless and getting a 40-50 ping in games, mines going from 50-90, with an average about 65ms

I've got PC > HDXB101 > HDXB01 > Router

tntcoder · 22 Oct 2010 at 19:40

Wardie said:
Brothers using wireless and getting a 40-50 ping in games, mines going from 50-90, with an average about 65ms

I've got PC > HDXB101 > HDXB01 > Router

Ping your router from cmd and see what the timings are.

Bakedgoods · 22 Oct 2010 at 19:41

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=37ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=82ms TTL=64

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=6ms TTL=64
Reply from 192.168.1.254: bytes=32 time=25ms TTL=64

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=100ms TTL=64
Reply from 192.168.1.254: bytes=32 time=31ms TTL=64
Reply from 192.168.1.254: bytes=32 time=580ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64

Tried changing ethernet cables, changing the plug socket used, changing ethernet port on my PC.

Bakedgoods · 22 Oct 2010 at 19:58

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=22ms TTL=64
Reply from 192.168.1.254: bytes=32 time=19ms TTL=64
Reply from 192.168.1.254: bytes=32 time=20ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=15ms TTL=64
Reply from 192.168.1.254: bytes=32 time=99ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=71ms TTL=64
Reply from 192.168.1.254: bytes=32 time=90ms TTL=64
Reply from 192.168.1.254: bytes=32 time=6ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=6ms TTL=64
Reply from 192.168.1.254: bytes=32 time=25ms TTL=64
Reply from 192.168.1.254: bytes=32 time=23ms TTL=64
Reply from 192.168.1.254: bytes=32 time=30ms TTL=64
Reply from 192.168.1.254: bytes=32 time=74ms TTL=64

John24 · 22 Oct 2010 at 20:01

Have you tried a direct connection into the PC? If you still get high pings it's the router if not it's the powerline's.

Bakedgoods · 27 Oct 2010 at 09:01

Tried the powerline equipment with my new PC and it's still spiking like crazy when just pinging even my local router.

Can't run cat5, but would rather not buy a wireless adapter.

However I am a bit concerned about spending again on new Powerline stuff and having the same problem.

Any last ideas?

morfmedia · 27 Oct 2010 at 12:55

Never seen mine spike beyond 2-5ms to the router. Something sounds strange to be honest, any other possible interference?

Bakedgoods · 27 Oct 2010 at 13:26

Not that I can think of.

Tried using different sockets on the opposite side of the room, swapping the ethernet cables etc. Tried downloading the configuration utility and changing the settings of that but it made no difference whatsoever.

Bakedgoods · 27 Oct 2010 at 18:40

Any final thoughts guys?

Might just order a new Powerline kit and hope it works, if it's still high then I guess i'll just have to sell it

manbearpig · 27 Oct 2010 at 18:44

I cant give any advice, but my generic powerline plugs from the rainforest are fine, I get about a 40ms ping all the time and It did at my old house. It may be your powerline plugs.

Bakedgoods · 27 Oct 2010 at 18:55

I've quite far away from the router and after reading comments I suspect the signal will be going through a circuit breaker before reaching where I am. People have mentioned lots of loss/signal degradation as a result of this.

Hmmmm :F

morfmedia · 27 Oct 2010 at 21:00

Might be worth getting some gigabit ones as they are likely to have better tolerances? As you say the circuit breaker degrades the circuit a lot I believe.

John24 · 28 Oct 2010 at 00:03

An openreach engineer told me the newer powerline adaptors don't have any issues with the circuit breaker because they use the earth wire instead of the live. Whether that is true or not I don't know but my XAVB2501's work fine over two floors.

Code:

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64

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

Bakedgoods · 28 Oct 2010 at 08:14

That looks great, i've just gone for it an ordered two of those. Pretty expensive!

Hopefully they will give the same performance as you've had otherwise I guess i'll just have to try sell them.

John24 · 29 Oct 2010 at 00:19

They are a bit pricey but I could only find good things about them, thankfully they worked out OK.

Got my fingers crossed for you

Bakedgoods · 29 Oct 2010 at 07:44

Cheers, i'll post the results this afternoon.

A quick ping to the local router once I get home will be all that's needed

Matt_Hirst · 29 Oct 2010 at 10:03

Just been reading this with interest.

I have D-Link homepluge DHP-301's, my office pc's are connected to a router, Belkin N1 view, then to dhp-301, then downstairs I have 3 other DHP-301's, one for the WD Live, one for a laptop the otherh connects to the broadband router.

At the moment the one in the office is plugged in and on and also the one downstairs to the router, my ping is as follows:

Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time=4ms TTL=63
Reply from 192.168.2.1: bytes=32 time=81ms TTL=63
Reply from 192.168.2.1: bytes=32 time=3ms TTL=63
Reply from 192.168.2.1: bytes=32 time=4ms TTL=63

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

Am wondering what could cause the ping to be so high for one of them? If I repeat the exercise usually three of the four are 3 or 4 ms but one is very large.

regards,

Matt

Bakedgoods · 29 Oct 2010 at 16:12

New ones wok a treat, results below!

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64

Thanks for the recommendation

Powerline and high latency

Capodecina

Capodecina

Capodecina

Capodecina

Capodecina

Capodecina

Capodecina

Capodecina

Capodecina

Capodecina

Capodecina