Homeplug ping spike problem

Yorkshirelion

Yorkshirelion

Well-known Member
Hi all,

Just got a Netgear HDXB101 200Mbps starter kit, plugged it in and installed the software which was a piece of cake, however the reason i bought these was to cure a flaky and packet lossy (made up word) problem.

One is connected to my router downstairs, one is connected to my PC upstairs, when i ping my router downstairs i can ping spikes as follows;

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Stu>ping 192.168.0.200 -t

Pinging 192.168.0.200 with 32 bytes of data:
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=9ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=2ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=15ms TTL=255
Reply from 192.168.0.200: bytes=32 time=5ms TTL=255
Reply from 192.168.0.200: bytes=32 time=5ms TTL=255
Reply from 192.168.0.200: bytes=32 time=5ms TTL=255
Reply from 192.168.0.200: bytes=32 time=7ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=11ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=5ms TTL=255
Reply from 192.168.0.200: bytes=32 time=11ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=13ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=10ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=8ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=13ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=2ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=8ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=6ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=5ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=15ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=13ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=8ms TTL=255
Reply from 192.168.0.200: bytes=32 time=12ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms TTL=255

Ping statistics for 192.168.0.200:
Packets: Sent = 85, Received = 85, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 15ms, Average = 4ms
Control-C
^C
C:\Users\Stu>

Is that just interference on the wiring that is causing this ?

If anyone else that has some could test there's i would appreciate it :lease:
 
G

graystreet

Well-known Member
I got these using 85Mbps Zyxel HPs. The spikes, coincidentally or otherwise, were when our daughter phoned us on our DECT phone.

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=50ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=25ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=24ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=25ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 62, Received = 62, Lost = 0 (0
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 50ms, Average = 5ms

HIH :)
 
Yorkshirelion

Yorkshirelion

Well-known Member
Damn,

It would seem that these are not the solution to my network problem then :mad:

I'm out of options, can't run Cat 5, wireless is lossy and these have big spikes, i wouldn't mind if it was just the old 10-20ms but i have seen 300-500ms and that is gonna cause a lag issue for sure.
 
T

t72bogie

Novice Member
Im afraid theres just as much noise on the powerlines in your home as there is in the airwaves :(

powerline uses a lot of algorithms (just as 802.11 wi-fi does) to overcome this and can be a lot better in some circumstances, just not all.

Some things are very noisy on the wire - switched power supplies (like those that come with mobile phones) and transformers (some low voltage light fitting ones) are the worst offenders, so try not to plug these in anywhere near the homeplugs
 
You must log in or register to reply here.

The latest video from AVForums

Podcast: Q Acoustics Q3030i, Humax Aura, Roku Streambar & WandaVision Reviews and more...
Subscribe to our YouTube channel.
Join the AVForums team live on Wednesdays at 7pm UK time.
Top Bottom