Carnagerover
Senior Member
Hi all,
I bought a Netgear HDB101 starterkit as i have recently moved my HTPC from the loungue into the now computer room.
I had previously tried the D-link DIR-855 and this went back within a day as it wasnt up to the task of delivering wireless into my computer room without dropping packets and tbh wireless just doesn't seem to cut it for gaming full stop.
I can't re-wire the house to include Cat 5 cable, live in the UK and its just not practical to do that in my house.
So i thought i had found the answer in homeplugs put it seems that something in my wiring is causing a problem for the old Powerline adapters.
I get zero packet loss with these put i get spikes in my ping, therefore it is better than wireless and slightly faster but for gaming it is still causing me problems.
Here is an example of me pinging the router from my PC upstairs to the router downstairs through the Powerline adapters;
Pinging 192.168.0.200 with 32 bytes of data:
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=3ms 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=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=16ms 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=89ms 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=12ms 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=7ms 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=11ms 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=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=8ms TTL=255
Reply from 192.168.0.200: bytes=32 time=66ms 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=221ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms 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=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=81ms 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=9ms TTL=255
As you can see there is a whopper 221ms spike in there, just one of them when i'm playing an overseas game which in Halo 3 is a distinct possibility then its lag time and i'm buying. Even the 82ms would probably throw a stutter.
So this is a better solution that wireless for me as i dont drop packets but i will still get the odd stutter.

I bought a Netgear HDB101 starterkit as i have recently moved my HTPC from the loungue into the now computer room.
I had previously tried the D-link DIR-855 and this went back within a day as it wasnt up to the task of delivering wireless into my computer room without dropping packets and tbh wireless just doesn't seem to cut it for gaming full stop.
I can't re-wire the house to include Cat 5 cable, live in the UK and its just not practical to do that in my house.
So i thought i had found the answer in homeplugs put it seems that something in my wiring is causing a problem for the old Powerline adapters.
I get zero packet loss with these put i get spikes in my ping, therefore it is better than wireless and slightly faster but for gaming it is still causing me problems.
Here is an example of me pinging the router from my PC upstairs to the router downstairs through the Powerline adapters;
Pinging 192.168.0.200 with 32 bytes of data:
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=3ms 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=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=16ms 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=89ms 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=12ms 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=7ms 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=11ms 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=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=8ms TTL=255
Reply from 192.168.0.200: bytes=32 time=66ms 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=221ms TTL=255
Reply from 192.168.0.200: bytes=32 time=3ms 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=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=4ms TTL=255
Reply from 192.168.0.200: bytes=32 time=81ms 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=9ms TTL=255
As you can see there is a whopper 221ms spike in there, just one of them when i'm playing an overseas game which in Halo 3 is a distinct possibility then its lag time and i'm buying. Even the 82ms would probably throw a stutter.
So this is a better solution that wireless for me as i dont drop packets but i will still get the odd stutter.
