[50mb] Regular Ping Spikes / Packet Loss

[ajaxsm]

Hey Guys,

I can't seem to get a response from anywhere else - including customer support. Yesterday morning I was upgraded to the 50mb package, but I am having a few issues.

I am an avid gamer, and ping / packet loss really affects gameplay. Since the upgrade I get 100% packet loss for around a second every 30 - 40 seconds... which is not then end of the world - but frustrating.

I saw its a good idea to post screen shots from the modem overview etc, so here are some:

http://uploadpicz.com/images/PUHEIQZ.jpg

http://uploadpicz.com/images/YK655ZX.jpg

Could the transmit power on the upstream be an issue? I'm clueless at the moment but if it continues I will have to find a way to go back to the 20mb package - as it was seriously stable and brilliant.

Thanks,
Matt

[Joxer]

Upstream power level looks high and amy be the problem but I don't know much about 50mb connections. The fact that you are locking onto 4 downstreams is also odd, are you on a virginmedia connection?

You could try pinging the default gateway ( if you are connected directrly to the modem) and see if you get packet loss there.

[ajaxsm]

I am defiantly on a Virgin Media connection.

Thanks for the suggestion about pinging the default gateway. I will try it tomorrow when I have access to move things around!

Anyone have any ideas about the power level on the upstream? I'll post a link to this thread tomorrow in reply to the virgin media twitter account - see if they can shed any light.

edit: new info

I decided to do a ping to the router IP itself, and I believe its the router where the trouble lies.


Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=908ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=8ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=722ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63


Notice the periodic high pings. I have tried this with 2 routers, 2 different computers - haven't been able to test wired yet. But I believe the problem lies on the modem.

[Zhadnost]

Upstream power level looks high and amy be the problem but I don't know much about 50mb connections. The fact that you are locking onto 4 downstreams is also odd, are you on a virginmedia connection?


Not odd, a lot of areas (this one included) has 4 DS channels. It may be that areas with BSRs have them.

Just to satisfy a curiousity can you run the following:

If linux/unix
=========
ifconfig eth0:0 192.168.100.10 netmask 255.255.255.0 up (assuming that the internet interface is eth0)
route add -host 192.168.100.10 dev eth0:0

If windows (less sure of this)
========
route add 192.168.100.0 mask 255.255.255.0 <internet ip>

And then ping the modem, (just to make sure that the problem is the connection and not the modem/network card)

[ajaxsm]

Rather oddly, now with a wired connection I don't get any of these packet drops at all - god knows why I did yesterday afternoon.

It seems the bit of hardware that was causing the issue was the free dongle they provided with the router. I'll keep you posted if it starts happening again (through wired).

Looks like the best solution would be me to actually fit Ethernet in the house.

Thanks for your help though guys - appreciated.

[Joxer]

I am defiantly on a Virgin Media connection.:D

Made me laugh!

Anyway... try pinging the router on wireless and see if you still get spikes (you said router then pinged the modem then called it the modem, confused me for a bit). If so then try changing the channel(s) on the router.

Zhadnost, I knew that about the BSRs but I don't like BSR and try to pretend they don't exist (it doesn't work).:nutter: