20ms Ping to google...

[thedoc!]

Hello List,

I am in france now and I am loving the bandwidth, the latency and the no CAP!!

Here is a ping to google - I will be back in RSA this weekend and will miss this

C:\WINDOWS>ping www.google.com

Pinging www.l.google.com [216.239.59.147] with 32 bytes of data:

Reply from 216.239.59.147: bytes=32 time=12ms TTL=239
Reply from 216.239.59.147: bytes=32 time=30ms TTL=239
Reply from 216.239.59.147: bytes=32 time=19ms TTL=239
Reply from 216.239.59.147: bytes=32 time=19ms TTL=239

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

 

[thedoc!]

Ping Telkom...

C:\WINDOWS>ping www.telkomsa.net

Pinging www.telkomsa.net [196.25.211.40] with 32 bytes of data:

Reply from 196.25.211.40: bytes=32 time=288ms TTL=113
Reply from 196.25.211.40: bytes=32 time=369ms TTL=113
Reply from 196.25.211.40: bytes=32 time=167ms TTL=113
Reply from 196.25.211.40: bytes=32 time=167ms TTL=113

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

 

[stoke]

/me pukes allover TheDoc! .
Amazing what can be achieved.
167 ms from France to Teklom ... grrrrrrrrrrrr.

 

[thedoc!]

Amazing hey.....? So much for unshaped ADSL...

 

[bwana]

Yeah - but its france!

 

[thedoc!]

anyone want any traces or pings done from here??

 

[Piesang]

I'm happy with this.


Pinging www.telkomsa.net [196.25.211.40] with 32 bytes of data:

Reply from 196.25.211.40: bytes=32 time=70ms TTL=116
Reply from 196.25.211.40: bytes=32 time=44ms TTL=116
Reply from 196.25.211.40: bytes=32 time=61ms TTL=116
Reply from 196.25.211.40: bytes=32 time=69ms TTL=116

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

 

[stoke]

Trace mt to bzflag0.gamesunited.de [Germany] and then do www.saix.co.za [SAIX] then do ftp.trenstar.co.za [IS] - please please.

 

[Piesang]

This is a ping to my ISP.

Excellent man!!!

C:\Documents and Settings\Piesang>ping www.wo.co.za

Pinging www.wo.co.za [196.7.147.134] with 32 bytes of data:

Reply from 196.7.147.134: bytes=32 time=5ms TTL=248
Reply from 196.7.147.134: bytes=32 time=6ms TTL=248
Reply from 196.7.147.134: bytes=32 time=6ms TTL=248
Reply from 196.7.147.134: bytes=32 time=4ms TTL=248

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

 

[thedoc!]

Trace mt to bzflag0.gamesunited.de [Germany] and then do www.saix.co.za [SAIX] then do ftp.trenstar.co.za [IS] - please please.

Only this host responds the rest seem to be blocking international ICMP?

C:\WINDOWS>ping bzflag0.gamesunited.de

Pinging bzflag0.gamesunited.de [212.6.108.237] with 32 bytes of data:

Reply from 212.6.108.237: bytes=32 time=12ms TTL=54
Reply from 212.6.108.237: bytes=32 time=12ms TTL=54
Reply from 212.6.108.237: bytes=32 time=12ms TTL=54
Reply from 212.6.108.237: bytes=32 time=13ms TTL=54

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

 

[James]

Reply from 212.6.108.237: bytes=32 time=12ms TTL=54

Nice !!!!

C:\Documents and Settings\Administrator>ping bzflag0.gamesunited.de

Pinging bzflag0.gamesunited.de [212.6.108.237] with 32 bytes of data:

Reply from 212.6.108.237: bytes=32 time=471ms TTL=48
Reply from 212.6.108.237: bytes=32 time=471ms TTL=48
Reply from 212.6.108.237: bytes=32 time=470ms TTL=48
Reply from 212.6.108.237: bytes=32 time=471ms TTL=48

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

 

[stoke]

Thanks TheDoc! - yea - it's the opposite on this end - cannot get a response from bzflag0 but do from the rest. Dangit.

They're doing it so that we cannot see who the bandwidth is actually pruchased from, cos then we could work out the real cost.

Hey - you got a response from telkomsa.net - tracert it please.

 

[Piesang]

What does tracert do??

 

[stoke]

Tells you the ip addresses of the routers that your traffic goes through on it's way to the destination.
You can then work out who owns the routers and therefore where the bandwidth was purchased from.

Open a MS Dos box / command prompt.
Type in tracert someipaddressordomainname

 

[Piesang]

Did you say you can't tracert bzflag0? Because I get a response.

 

[Piesang]

C:\Documents and Settings\Piesang>tracert bzflag0.gamesunited.de

Tracing route to bzflag0.gamesunited.de [212.6.108.237]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms 192.168.0.100
3 3 ms 7 ms 6 ms 172.17.9.254
4 8 ms 5 ms 3 ms 192.168.99.85
5 5 ms 4 ms 5 ms 192.168.99.5
6 5 ms 7 ms 5 ms 192.168.99.46
7 12 ms 8 ms 11 ms 196.40.104.17
8 13 ms 10 ms 10 ms 172.16.8.50
9 22 ms 23 ms 23 ms dsl-146-192-01.telkomadsl.co.za
[165.146.192.1]

10 24 ms 45 ms 34 ms wblv-ip-er-1-fe-10-0-1-1.telkom-ipnet.co.za [196
.43.10.14]
11 349 ms * 343 ms ny-ip-dir-globalc-pos-7-0.telkom-ipnet.co.za [19
6.43.9.149]
12 337 ms 326 ms 327 ms g0-2.na01.b001105-24.jfk02.atlas.cogentco.com [3
8.112.18.41]
13 327 ms 329 ms 327 ms g10-2-104.core01.jfk02.atlas.cogentco.com [38.11
2.38.169]
14 329 ms 327 ms 328 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.1
3]
15 336 ms 427 ms 333 ms p5-0.core01.bos01.atlas.cogentco.com [66.28.4.11
7]
16 414 ms 411 ms 415 ms p10-0.core01.lon02.atlas.cogentco.com [130.117.0
.186]
17 420 ms 438 ms 423 ms p15-0.core01.ams03.atlas.cogentco.com [130.117.1
.226]
18 424 ms 465 ms 421 ms ewe-tel-gmbh-ams.demarc.cogentco.com [130.117.23
.126]
19 432 ms 437 ms 433 ms bbrt.ol-1-so-3-0-0.3.ewe-ip-backbone.de [80.228.
109.137]
20 430 ms 430 ms 454 ms 212.6.108.237

Trace complete.

 

[stoke]

Yea - my ISP is IS - yours is probably SAIX based.
Notice the HUUUUGE jump at step 11.
Now lets see that step in reverse from France ...

 

[Piesang]

Yes, a huge jump and a timeout at step 11.

 

[stoke]

Step 11 is the SAIX link to New York and through the SAIX shaping stuff.
Now - a TraceRt from France will show something completely different on the same 2 points.
TheDoc! - Where are you ?

 

[thedoc!]

was freezing my nutz off here....OK here is the tracert results:

C:\WINDOWS>tracert www.telkomsa.net

Tracing route to www.telkomsa.net [196.25.211.40]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 10.140.0.1
2 1 ms <1 ms <1 ms 192.168.32.1
3 <1 ms 1 ms 1 ms 213.174.115.30
4 1 ms 1 ms 1 ms 213.174.96.19
5 3 ms 2 ms 1 ms 217.69.16.33
6 1 ms 2 ms 2 ms t3-0-3-1.ar2.CDG2.gblx.net [64.211.83.9]
7 8 ms 7 ms 7 ms so7-0-0-2488M.ar2.AMS2.gblx.net [67.17.65.246]
8 11 ms 10 ms 10 ms Telkom-SA-Limited.so-0-2-0.ar2.AMS2.gblx.net [64.210.21.46]
9 46 ms 61 ms 49 ms ash-ip-dir-equinix-pos-7-0.telkom-ipnet.co.za [196.43.9.154]
10 40 ms 64 ms 46 ms ash-ip-dir-equinix-ge-1-0-2.telkom-ipnet.co.za [196.43.9.166]
11 46 ms 61 ms 46 ms ash-ip-dir-equinix.telkom-ipnet.co.za [196.43.9.245]
12 128 ms 150 ms 134 ms rrba-ip-lir-1-pos-6-1.telkom-ipnet.co.za [196.43.9.145]
13 157 ms 121 ms 145 ms rndf-ip-er-1-atm-4-1-0-209.telkom-ipnet.co.za [196.43.11.210]
14 141 ms 90 ms 151 ms intekom-34meg-gw.gt.saix.net [196.25.245.50]
15 140 ms 151 ms 133 ms 196.25.211.40

Trace complete.

C:\WINDOWS>