Varied Pings and gaming - What to do?

[leewsimpson]

Hello fellow iburst users.

I would really like to get Iburst working for games. I have read that some people get quite a steady ping rate around the 60ms mark. Here is my setup currently:

External IBurst modem connected to long (10m) ethernet cable. Modem is situated in the loft (have tried finding the "sweet" spot).

I live in the north part of Weltevreden park, so I'm probably connected to the Northcliff tower. I have tried the IConnect program to make sure but I get the Socket Error # 10060.

MTU is set to 1352, and TCP receive is set to 10496 as recommeded by the speedguide website. Timestamps also set to on.

My ping to IBurst is all over the place, as you can see here. My question is what more can I do to fix the ping so I can play Battlefield 2!

Reply from 196.30.31.120: bytes=32 time=42ms TTL=126
Reply from 196.30.31.120: bytes=32 time=1655ms TTL=126
Reply from 196.30.31.120: bytes=32 time=56ms TTL=126
Reply from 196.30.31.120: bytes=32 time=81ms TTL=126
Reply from 196.30.31.120: bytes=32 time=65ms TTL=126
Reply from 196.30.31.120: bytes=32 time=1521ms TTL=126
Reply from 196.30.31.120: bytes=32 time=431ms TTL=126
Reply from 196.30.31.120: bytes=32 time=55ms TTL=126
Request timed out.
Reply from 196.30.31.120: bytes=32 time=2906ms TTL=126
Reply from 196.30.31.120: bytes=32 time=183ms TTL=126
Reply from 196.30.31.120: bytes=32 time=157ms TTL=126
Reply from 196.30.31.120: bytes=32 time=1737ms TTL=126
Reply from 196.30.31.120: bytes=32 time=204ms TTL=126
Reply from 196.30.31.120: bytes=32 time=125ms TTL=126
Reply from 196.30.31.120: bytes=32 time=611ms TTL=126
Reply from 196.30.31.120: bytes=32 time=36ms TTL=126
Reply from 196.30.31.120: bytes=32 time=136ms TTL=126
Reply from 196.30.31.120: bytes=32 time=115ms TTL=126
Reply from 196.30.31.120: bytes=32 time=108ms TTL=126
Reply from 196.30.31.120: bytes=32 time=3284ms TTL=126
Reply from 196.30.31.120: bytes=32 time=672ms TTL=126
Reply from 196.30.31.120: bytes=32 time=472ms TTL=126
Reply from 196.30.31.120: bytes=32 time=107ms TTL=126
Reply from 196.30.31.120: bytes=32 time=174ms TTL=126
Reply from 196.30.31.120: bytes=32 time=84ms TTL=126
Reply from 196.30.31.120: bytes=32 time=108ms TTL=126
Reply from 196.30.31.120: bytes=32 time=65ms TTL=126
Reply from 196.30.31.120: bytes=32 time=581ms TTL=126
Reply from 196.30.31.120: bytes=32 time=795ms TTL=126
Reply from 196.30.31.120: bytes=32 time=246ms TTL=126
Reply from 196.30.31.120: bytes=32 time=78ms TTL=126
Reply from 196.30.31.120: bytes=32 time=131ms TTL=126
Reply from 196.30.31.120: bytes=32 time=2029ms TTL=126
Reply from 196.30.31.120: bytes=32 time=262ms TTL=126
Reply from 196.30.31.120: bytes=32 time=96ms TTL=126
Reply from 196.30.31.120: bytes=32 time=68ms TTL=126
Reply from 196.30.31.120: bytes=32 time=63ms TTL=126
Reply from 196.30.31.120: bytes=32 time=58ms TTL=126
Request timed out.

Ping statistics for 196.30.31.120:
    Packets: Sent = 2969, Received = 2938, Lost = 31 (1% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 4219ms, Average = 304ms

 

[GRES]

obtain directional antenna and have fun!