First impressions on ure mywireless

pings to :

kalahari.mweb.co.za
karoo.mweb.co.za

and any saix gaming servers would really help me make my decision, i've got the contract sitting on my desk waiting to be faxed off :)

Also, what area are you in if you don't mind me asking ?
 
hey all - yup its the basic 128 package-

first for ANDRE - who wanted SAIX FREELANCE SERVER pinged (196.25.69.221 ) - did a basic ping plotter (and remember Im yanking off one ftp, and upping to another at same time, using up b/w) hopefully this is what you're after
first:
1, -------------- ,66.18.65.105
2,gige-0-0-102.rtr-core4-stp.infosat.net,66.18.65.110
3,gige-0-0-23.rtr-bdr1-rbn.infosat.net,66.18.65.201
4, -------------- ,168.209.18.61
5, -------------- ,196.26.0.251
6,ndf-access2-s-3-1-0.gt.saix.net,196.25.110.245
7,rndf-ip-er-1-fe-8-1-0.telkom-ipnet.co.za,196.43.11.210
8,intekom-34meg-gw.gt.saix.net,196.25.245.50
9,mayhem.telkomsa.net,196.25.69.221
-----------------------
then did a 1 sec ping rate to same addy, and it seemed to disappear totally, giving:
Target Name: mayhem.telkomsa.net
IP: 196.25.69.221
Date/Time: 1/29/04 8:07:46 PM to 1/29/04 8:08:04 PM

1 * * * * * * * * * * [66.18.65.105]
2 * * * * * * * * * * gige-0-0-102.rtr-core4-stp.infosat.net [66.18.65.110]
3 * * * * * * * * * * gige-0-0-23.rtr-bdr1-rbn.infosat.net [66.18.65.201]
4 * * * * * * * * * * [168.209.18.61]
5 * * * * * * * * * * [196.26.0.251]
6 * * * * * * * * * * ndf-access2-s-3-1-0.gt.saix.net [196.25.110.245]
7 * * * * * * * * * * rndf-ip-er-1-fe-8-1-0.telkom-ipnet.co.za [196.43.11.210]
8 * * * * * * * * * * intekom-34meg-gw.gt.saix.net [196.25.245.50]
9 * * * * * * * * * * mayhem.telkomsa.net [196.25.69.221]

Ping statistics for mayhem.telkomsa.net
Packets: Sent = 10, Received = 0, Lost = 10 (100.0%)
Round Trip Times: Minimum = 0ms, Maximum = 0ms, Average = 0ms
-----------

next for CHOPSKY re the gaming servers, took a look at saix, and there's a whole blerry bunch of em! :P - dont want to hog the whole page with info, but the first two I tried off SAIX page, (196.4.79.9 and 196.4.79.8) were in the 80's in terms of ping (using pingplotter) - and the one CT one I tried (from here in Jhb),(196.43.3.36) gave around 120 - 150 ping with some packet loss midway in the hops.

then for Mweb, again too darn many servers - Phobos 8777 - around 93 ping average, Kalahari 7677, around 119, karoo.mweb.co.za 9777 - around 90 (lots of packet loss)
Remember though Im majorly abusing my b/w at the same time, with a number of appz going - never a good thing to do when pinging anything.. but if there are specific servers you want info on, or forms of pinging/testing you'd like, let me know :)

hope the above helps..
 
ps- for SLIVER, Im in Melville, Jhb (the much sneered at 'sewende laan' :)

If anyone wants actual lengthy traceroutes and ping times - rather than clog up the page here, feel free to mail me and I'll do whatever tests I can to help folks work out whether or not to make the leap..
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by LoneGunman</i>
first for ANDRE - who wanted SAIX FREELANCE SERVER pinged <hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

Thanks, but unfortunately any downloads going on in the background tend to skew your pings somewhat. When gaming you're not going to be running downloads usually since it can make the game jerky.

If you have some time, can you ping any one of the game servers people have asked for while not downloading anything so we can get an idea what it's like.

For comparison sake, this is what I get from mayhem:
C:\&gt;ping mayhem.telkomsa.net

Pinging mayhem.telkomsa.net [196.25.69.221] with 32 bytes of data:

Reply from 196.25.69.221: bytes=32 time=59ms TTL=123
Reply from 196.25.69.221: bytes=32 time=40ms TTL=123
Reply from 196.25.69.221: bytes=32 time=41ms TTL=123
Reply from 196.25.69.221: bytes=32 time=40ms TTL=123

Ping statistics for 196.25.69.221:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 59ms, Average = 45ms
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">If anyone wants actual lengthy traceroutes and ping times - rather than clog up the page here<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">Being the first one up and running I dont think anyone would mind if you glogged up 1000 pages. [:)]
ProAsm ponders at the teeth marks on his keyboard [:D]
 
sorry folks, didnt mean to cause frustration :) I stopped downloading of everything, and did a proper ping and here's what follows - time is 11.20pm

(for ANDRE - re downloading while doing pings, yeah ok, Im dumb (and wayy too eager to shovel in the entire internet :)

I stopped everything and pinged mayhem to start with:

C:\&gt;ping mayhem.telkomsa.net

Pinging mayhem.telkomsa.net [196.25.69.221] with 32 bytes of data:

Reply from 196.25.69.221: bytes=32 time=106ms TTL=120
Reply from 196.25.69.221: bytes=32 time=97ms TTL=120
Reply from 196.25.69.221: bytes=32 time=91ms TTL=120
Reply from 196.25.69.221: bytes=32 time=101ms TTL=120

Ping statistics for 196.25.69.221:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 106ms, Average = 98ms
---------------------------------------


something wrong with SAIX at time of pinging, perhaps - here's what I got:

196.4.79.9 : saix game server-

C:\&gt;ping 196.4.79.9

Pinging 196.4.79.9 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 196.4.79.9:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

total time out - maybe the server was down...ditto for the other saix one I'd tried earlier
- however, the CT one was responsive:
C:\&gt;ping 196.43.3.36

Pinging 196.43.3.36 with 32 bytes of data:

Reply from 196.43.3.36: bytes=32 time=113ms TTL=120
Reply from 196.43.3.36: bytes=32 time=106ms TTL=120
Reply from 196.43.3.36: bytes=32 time=134ms TTL=120
Reply from 196.43.3.36: bytes=32 time=106ms TTL=120

Ping statistics for 196.43.3.36:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 134ms, Average = 114ms
---
berzerk.saix.net 196.4.79.6 also timed out :
C:\&gt;ping 196.4.79.6

Pinging 196.4.79.6 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 196.4.79.6:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

took a look at Pta saix server: reboot.saix.net 196.25.219.132 Pretoria - also total time out. ditto the CS server
C:\&gt;ping elyzium.saix.net

Pinging elyzium.saix.net [196.4.79.9] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 196.4.79.9:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

(having not done any gaming in a long time, there may have just been a major fubar at time of me trying SAIX, so dont take the zero responses from saix as gospel..
reboot.saix.net [196.25.219.132] also 100% time out

C:\&gt;ping q3.saix.net
Unknown host q3.saix.net.

however, got a response from osp.saix.net - first time 25% PL, second time, following:
C:\&gt;ping osp.saix.net

Pinging osp.saix.net [196.25.69.222] with 32 bytes of data:

Reply from 196.25.69.222: bytes=32 time=105ms TTL=120
Reply from 196.25.69.222: bytes=32 time=99ms TTL=120
Reply from 196.25.69.222: bytes=32 time=94ms TTL=120
Reply from 196.25.69.222: bytes=32 time=88ms TTL=120

Ping statistics for 196.25.69.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 105ms, Average = 96ms



---------NOW MWEB

C:\&gt;ping kalahari.mweb.co.za

Pinging kalahari.mweb.co.za [196.2.33.21] with 32 bytes of data:

Reply from 196.2.33.21: bytes=32 time=97ms TTL=119
Reply from 196.2.33.21: bytes=32 time=87ms TTL=119
Reply from 196.2.33.21: bytes=32 time=100ms TTL=119
Reply from 196.2.33.21: bytes=32 time=97ms TTL=119

Ping statistics for 196.2.33.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 100ms, Average = 95ms

and karoo.mweb (1st test ping got a 25% packet loss, redid it and got the results below:
C:\&gt;ping karoo.mweb.co.za

Pinging karoo.mweb.co.za [196.2.128.100] with 32 bytes of data:

Reply from 196.2.128.100: bytes=32 time=117ms TTL=116
Reply from 196.2.128.100: bytes=32 time=110ms TTL=116
Reply from 196.2.128.100: bytes=32 time=118ms TTL=116
Reply from 196.2.128.100: bytes=32 time=111ms TTL=116

Ping statistics for 196.2.128.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 110ms, Maximum = 118ms, Average = 114ms

hope this genuine data helps folks.. yell if its incomplete or you need other spots pinged (maybe the saix ones'll be up and responding tomorrow - will check it)
 
Also bear in mind that the Internet is still recovering from the MyDoom Worm. But the pings look acceptable.

Can't wait for CPT to come up.
-------------------------------[:)]

When I walk through the valley of the shadow of death, I shall fear no evil, for I am the meanist mother****** in the valley - Patton
 
Dear Mr Gunman,

Could you give us an indication of the distance you are from your tower? Does the modem give you a signal-strenght of any sort?

And lastly, can you ping:

1. is.co.za
2. ns.uu.net

Please?

--deckert
 
So far, I can't say Im too impressed with the pings LoneGunman has shown us. They're all pretty much about 90 which isn't in my opinion, acceptable for a broadband service. Im interested to know though, as Deckert is, how far you are from the tower?
Cheers.
 
Hi all - ok - rather than do thumbsuck of distance, if you have a street map, I stay in Seventh Avenue in Melville, and my tower is Brixton Tower (South of Melville) and for maths fans it takes me around 25 -35 minutes at a brisk walking pace, to get to the SABC, which is about 4 to 5 blocks below the tower itself, which is set higher up on the hill. Guestimates are dangerous but I'd say a minimum of 1.5 km, the guy who dropped off my module said it was about 4km, but I dont think its that far.

And Deckert, I'll post those two pings you're after a little later, once I've rebooted - (bear in mind I've yanked at least 600+ megs of goodies since yesterday afternoon and no reboot, so my pc is currently a tad tired)

As for signal strength, it seemed to show the data when I initially connected, but now doesnt - at time of connection all the 'bands' on the signal strength diagram were green (ole Megawan users will recall that kind of imagery) but I think when mousing over the signal strength indicator at connect time, it gave around 46%..

Given the I-Pod size of the thing, (with a dinky little ariel thats smaller than a pack of cigarettes) and comparing it to the aforementioned Megawan antennae size and fiddling in order to calibrate the MW signal, I was impressed by the plug n play ability.. also given that its amidst a lot of electronics and a thick wall between it and the tower itself - it didnt need open windows or 'aiming', so the signal must be real serious and widespread. Having got it up and running, Im loath to move it at all, least of all out onto balcony into direct line of sight, but regardless, the thing works. The only 'disconnect' happened last night after a while when I was doing the ping experiments - but that could have been due to a range of causes, from the massive downloading splurge onwards - you can set the thing to auto-reconnect, so any glitches dont cause too much trouble..
 
Hi All

If LoneGunman is getting 16k and he's maybe 1 of about 6 or 7 other users on the system...then at this stage I'm not impressed. What happened to the bursting that we heard so much about. I was thinking that the first people on te system would certainly get at least close to a 1meg/sec. The pings is also not what I expected.

LoneGunman...here's something for you to do - dgo to www.speedguide.net and do a speed test...they'l proberbly tell you that what you have is anything but broadband. :D

I'll stick to what I have for now.

Cheers
Guz
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by chopsky</i>
<br />So far, I can't say Im too impressed with the pings LoneGunman has shown us. They're all pretty much about 90 which isn't in my opinion, acceptable for a broadband service. Im interested to know though, as Deckert is, how far you are from the tower?
Cheers.
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

Chopsky Broadband has nothing to do with latency and more to do with amount of data that you can stream down i.e "A transmission facility having a bandwidth sufficient to carry multiple voice, video or data channels simultaneously." Latency isn't part of broadband at all as Satellite is also classified as broadband,yes I agree with you the pings are low but then :) I don't mind if I get 100 ping on CS or DoD for a 24/7 connection :)

Regards
Cerberus
 
I genereally find usb modems very slow compared to the equivilant ethernet/pci products. My parents usb isdn modem would average 80-100ms to kalahari while my pci isdn modem in a linux box would average 40-60. When using usb it also depends a lot on your PC, if you are using high cpu at the time your pings will be low, thats why i would favour using the ethernet option into a linux box seperate from the box you play games on.
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by guztro</i>
<br />
Hi All

If LoneGunman is getting 16k and he's maybe 1 of about 6 or 7 other users on the system...then at this stage I'm not impressed. What happened to the bursting that we heard so much about. I was thinking that the first people on te system would certainly get at least close to a 1meg/sec. The pings is also not what I expected.

<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

Hi,

Bursting was never advertised. In fact, when I phoned Sentech this was one of the few things they could confirm. Please remember that the statements that ProAsm make on this forum are not official Sentech statements.

Regards
Celery
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by celeborn</i>

Bursting was never advertised. In fact, when I phoned Sentech this was one of the few things they could confirm.
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

Ja, but then why does it still say <i>Up to 3Mbps of broadband at your fingertips.</i>

It's right there in a large font size on http://www.sentech.co.za.
 
He's on a 128k package.. .getting 16k/s .. .with bout a 100ping to most local gaming servers... i say weldone sentech. Especially since the net is being hammered by the current wormz.

For the price being paid... i dont think anyone in ZA can complain about getting 16k/s 24/7. The only question is will it remain that way once his contention gets filled up.

Lone please keep us informed if u notice any decrease in speeds over the next month or 2.
 
well that is what the modem can do 3mbps. I remember reading either on the site or in the forums each package is sort of capped to 128kbs or 256. 16k is good for a 128kbs. Its what he suppose to get. His ping is about 100 locally, it could be because he is about 4km away from the tower


how about getting those reason.za.net pings

..- dot dot dash ;)
 
Its not the distance to the tower. All radiowaves travel at the speed of light, 300 000 000 meters per second or 300 000 km/sec.
So the delay (or extra ping time) due to the 4km distance to the tower is then (4x2)/300 000 sec or 0.026 millisec.
Even at 15km from the tower it will be (15x2)/300 000 or 0.1 millisec.

Ajax
 
Not really - the problem is not the speed of the wave, it is the quality of the wave. The better the quality of the wave, the higher the dataspeed (and less lost packets etc)



<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by ajax</i>
<br />Its not the distance to the tower. All radiowaves travel at the speed of light, 300 000 000 meters per second or 300 000 km/sec.
So the delay (or extra ping time) due to the 4km distance to the tower is then (4x2)/300 000 sec or 0.026 millisec.
Even at 15km from the tower it will be (15x2)/300 000 or 0.1 millisec.

Ajax


<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

South Africa needs World Class Broadband at World Competitive Prices.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X