46% Signal

Not that great, I expected better with such a good signal.


C:\>ping 196.43.3.38 -t

Pinging 196.43.3.38 with 32 bytes of data:

Reply from 196.43.3.38: bytes=32 time=275ms TTL=120
Reply from 196.43.3.38: bytes=32 time=261ms TTL=120
Reply from 196.43.3.38: bytes=32 time=300ms TTL=120
Reply from 196.43.3.38: bytes=32 time=301ms TTL=120
Reply from 196.43.3.38: bytes=32 time=201ms TTL=120
Reply from 196.43.3.38: bytes=32 time=399ms TTL=120
Reply from 196.43.3.38: bytes=32 time=220ms TTL=120
<b>Request timed out.</b> (WHY?)
Reply from 196.43.3.38: bytes=32 time=270ms TTL=120
Reply from 196.43.3.38: bytes=32 time=148ms TTL=120
Reply from 196.43.3.38: bytes=32 time=246ms TTL=120
Reply from 196.43.3.38: bytes=32 time=187ms TTL=120
Reply from 196.43.3.38: bytes=32 time=135ms TTL=120
Reply from 196.43.3.38: bytes=32 time=191ms TTL=120
Reply from 196.43.3.38: bytes=32 time=212ms TTL=120
Reply from 196.43.3.38: bytes=32 time=274ms TTL=120

Ping statistics for 196.43.3.38:
Packets: Sent = 16, Received = 15, Lost = 1 (6% l
Approximate round trip times in milli-seconds:
Minimum = 135ms, Maximum = 399ms, Average = 241ms
 
how come you ping so crap?

I never get a loss, always 0% and sub 120ms

did you do TheRodent's tweaks?

Why do you have to "put your two cents in"... but it's only a "penny for your thoughts"? Where's that extra penny going to?
 
I have the USB so basically it's just the Registry tweak I can do, is this right? Will restart quickly and retry the ping.
 
Thats a high signal strength. Remember though that ping times are probably also a factor of the overhead traffic (read, multiplexing load) of your particular tower. Maybe you are on a busy tower with a high TCR (modems-per-tower) [:)]

Have you confirmed that that is in fact the Sentech tower or is it just an educated guess. The wont necessarily just stick the panels on the nearest high tower. The could be on a lower building somewhere nearby. Just make sure what you say is LOS really is true LOS. Not that it matters anyways..
 
Cool, my ping has improved, but the packet loss increased. Prob just a busy tower then.
C:\&gt;ping 196.43.3.38 -t

Pinging 196.43.3.38 with 32 bytes of data:

Reply from 196.43.3.38: bytes=32 time=109ms TTL=120
Reply from 196.43.3.38: bytes=32 time=108ms TTL=120
Reply from 196.43.3.38: bytes=32 time=127ms TTL=120
Request timed out.
Request timed out.
Reply from 196.43.3.38: bytes=32 time=160ms TTL=120
Reply from 196.43.3.38: bytes=32 time=160ms TTL=120
Reply from 196.43.3.38: bytes=32 time=159ms TTL=120
Reply from 196.43.3.38: bytes=32 time=142ms TTL=120
Reply from 196.43.3.38: bytes=32 time=143ms TTL=120
Request timed out.
Reply from 196.43.3.38: bytes=32 time=161ms TTL=120
Reply from 196.43.3.38: bytes=32 time=181ms TTL=120
Reply from 196.43.3.38: bytes=32 time=142ms TTL=120
Reply from 196.43.3.38: bytes=32 time=120ms TTL=120
Reply from 196.43.3.38: bytes=32 time=142ms TTL=120
Reply from 196.43.3.38: bytes=32 time=141ms TTL=120
Reply from 196.43.3.38: bytes=32 time=142ms TTL=120

Ping statistics for 196.43.3.38:
Packets: Sent = 18, Received = 15, Lost = 3 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 181ms, Average = 142ms
 
Wow, so the debugging info in the drivers has quite a high overhead then. I never could quite figure out if it makes a lot of difference, due to my signal being way lower when I tested this back in the old days on an XP machine.

I moved my setup to Linux completely, and got an average ping of 100-120ms so I didn't care that much.

I do however get the same amount of packet loss though.


<center><h5><font color="red">Oo. MyWireless <s>Hacks</s> Tweaks & Tech Info.oO </font id="red"></h5><h6>Have you checked the fawking FAQ?</h6></center>
 
noone, thats shocking. I'm getting average ping times of under 80ms - constantly
 
I get 3 lights, 12% signal, and pings of average 120ms... is that good or bad?
 
aftermath, were your pings to the above UT2004 server or to some other address. I say this because there is a sizable 10ms-20ms difference between say UT2004 and sentech.co.za (for my pings at least)

sentech: avg = 109 (20 packets)
UT2004: avg = 123 (20 packets)

I just love that those pings are under near full load [:D]

4 lights - 20% - tower 36 - 11PM
 
Just kidding. I wish, but I think I get some of the worst ping times.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X