UUNT --> JINX Problem

J

JL1

Member
Joined
Jan 26, 2005
Messages
24
Reaction score
0
it looks like the problem is at JINX

Tracing route [165.146.7.3]
over a maximum of 30 hops:

1 45 ms 44 ms 61 ms 196.30.31.100
2 174 ms 49 ms 270 ms 196.30.31.193
3 304 ms 449 ms 42 ms fe6-1.gw10.jnb6.alter.net [196.30.31.254]
4 625 ms 124 ms 54 ms ge0-0.br1.jnb6.alter.net [196.30.156.41]
5 103 ms 106 ms 4149 ms other-side.atm6-0sub1.br1.jnb6.alter.net [196.31
.39.53]
6 55 ms 53 ms 86 ms rndf-ip-er-2-ge-2-0-0.telkom-ipnet.co.za [196.43
.11.158]
7 87 ms 56 ms 112 ms rndf-ip-esr-1-fe-1-0-4.telkom-ipnet.co.za [196.4
3.10.6]
8 114 ms 3428 ms 110 ms rndf-146-7-03.telkomadsl.co.za [165.146.7.3]

Trace complete.


a second tracert from iburst to a ADSL node
Tracing route to [165.146.7.3]
over a maximum of 30 hops:

1 281 ms 54 ms 66 ms 196.30.31.100
2 494 ms * 127 ms 196.30.31.193
3 * 1030 ms * fe6-1.gw10.jnb6.alter.net [196.30.31.254]
4 358 ms 42 ms 52 ms ge0-0.br1.jnb6.alter.net [196.30.156.41]
5 340 ms 65 ms 70 ms other-side.atm6-0sub1.br1.jnb6.alter.net [196.31
.39.53]
6 * * 2021 ms rndf-ip-er-2-ge-2-0-0.telkom-ipnet.co.za [196.43
.11.158]
7 51 ms 53 ms 49 ms rndf-ip-esr-1-fe-1-0-4.telkom-ipnet.co.za [196.4
3.10.6]
8 1493 ms 196 ms 1006 ms rndf-146-7-03.telkomadsl.co.za [165.146.7.3]

Trace complete.
 
Very deceiving.

1 1 ms 1 ms 1 ms Router.yfd.ath.cx [192.168.0.254]
2 83 ms 95 ms 123 ms 196.30.31.100
3 68 ms 98 ms 111 ms 196.30.31.193
4 206 ms 290 ms 179 ms fe6-1.gw10.jnb6.alter.net [196.30.31.254]
5 70 ms 97 ms 124 ms ge0-0.br1.jnb6.alter.net [196.30.156.41]
6 69 ms 150 ms 68 ms other-side.atm6-0sub1.br1.jnb6.alter.net [196.31.39.53]
7 81 ms 49 ms 141 ms rndf-ip-er-2-ge-2-0-0.telkom-ipnet.co.za [196.43.11.158]
8 92 ms 54 ms 124 ms rndf-ip-esr-1-fe-1-0-1-1.telkom-ipnet.co.za [196.43.10.182]
9 79 ms 109 ms 119 ms rndf-146-7-03.telkomadsl.co.za [165.146.7.3]
 
Last edited:
JL1 said:
it looks like the problem is at JINX

Tracing route [165.146.7.3]
over a maximum of 30 hops:

1 45 ms 44 ms 61 ms 196.30.31.100
2 174 ms 49 ms 270 ms 196.30.31.193
3 304 ms 449 ms 42 ms fe6-1.gw10.jnb6.alter.net [196.30.31.254]
4 625 ms 124 ms 54 ms ge0-0.br1.jnb6.alter.net [196.30.156.41]
5 103 ms 106 ms 4149 ms other-side.atm6-0sub1.br1.jnb6.alter.net [196.31.39.53]
6 55 ms 53 ms 86 ms rndf-ip-er-2-ge-2-0-0.telkom-ipnet.co.za [196.43.11.158]
7 87 ms 56 ms 112 ms rndf-ip-esr-1-fe-1-0-4.telkom-ipnet.co.za [196.43.10.6]
8 114 ms 3428 ms 110 ms rndf-146-7-03.telkomadsl.co.za [165.146.7.3]

Trace complete.
Click to expand...

Im resurecting this because something had fundamentally changed.

No matter what URL I try this on (and i've tried many), the first hop gives a timeout. Where is 196.30.31.100??? It was always there before?

I can ping 196.30.31.100 no problem. But it is no loger on the route. As PAN says in another thread, maybe some kind of proxy has been installed.

Code: 
>tracert www.mweb.co.za

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    77 ms   234 ms    77 ms  196.30.31.193
  3    93 ms    93 ms    93 ms  fe6-1.gw10.jnb6.alter.net [196.30.31.254]
  4     *       93 ms     *     fe1-0.br1.jnb7.alter.net [196.31.17.162]
  5     *       77 ms    93 ms  as3741.rba.is.co.za [196.30.228.242]
  6   296 ms   107 ms     *     core2a-rba-gi4-0-0.rtr.isnet.net [196.26.0.8]
  7   170 ms     *        *     168.209.100.78
  8     *       93 ms     *     168.209.0.194
  9   107 ms   124 ms   124 ms  196.23.49.102
 10    93 ms   187 ms   171 ms  www.mweb.co.za [196.2.63.110]

Trace complete.
 
Tracing route to is.co.za [196.4.160.2]
over a maximum of 30 hops:

1 84 ms 179 ms 119 ms 196.30.31.100
2 109 ms 290 ms 49 ms 196.30.31.193
3 158 ms * 169 ms fe6-1.gw10.jnb6.alter.net [196.30.31.254]
4 * 79 ms 100 ms fe1-0.br1.jnb7.alter.net [196.31.17.162]
5 142 ms 221 ms * as3741.rba.is.co.za [196.30.228.242]
6 108 ms 89 ms 89 ms crsm2a-rba-vl1.rtr.isnet.net [196.26.0.12]
7 180 ms 59 ms 59 ms apollo.is.co.za [196.4.160.2]

Trace complete.

...and gatecrasher... im right, a proxy has been setup
 
Compare these two traces to Google: The first is one is using Iburst. The second one is using 64k Mweb ISDN.

Code: 
>tracert www.google.com

Tracing route to www.google.akadns.net [64.233.187.99]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    77 ms    62 ms   140 ms  196.30.31.193
  3    77 ms    62 ms   156 ms  fe6-1.gw10.jnb6.alter.net [196.30.31.254]
  4   171 ms    93 ms   187 ms  fe4-1-0.cr1.jnb6.alter.net [196.30.156.33]
  5   312 ms   405 ms   312 ms  atm1-1-0sub902.ir2.mia16.alter.net [196.30.229.2
09]
  6   312 ms   374 ms   327 ms  POS0-1-0.IH4.MIA4.ALTER.NET [152.63.86.145]
  7   310 ms   312 ms   421 ms  302.at-5-1-0.XR2.MIA4.ALTER.NET [152.63.7.182]
  8   312 ms   343 ms   327 ms  0.so-4-2-0.XL2.MIA4.ALTER.NET [152.63.101.46]
  9   343 ms     *      343 ms  0.so-4-2-0.XL2.ATL5.ALTER.NET [152.63.81.81]
 10     *      327 ms   374 ms  0.so-7-0-0.BR3.ATL5.ALTER.NET [152.63.87.93]
 11   406 ms     *      327 ms  so-1-1-0.gar2.Atlanta1.Level3.net [4.68.127.177]

 12   452 ms   359 ms     *     so-3-3-0.bbr1.Atlanta1.Level3.net [4.68.96.13]
 13   436 ms     *      312 ms  ge-11-0.hsa1.Atlanta1.Level3.net [64.159.3.6]
 14   390 ms   577 ms     *     unknown.Level3.net [63.211.121.30]
 15     *      359 ms   421 ms  216.239.46.170
 16   562 ms   421 ms     *     216.239.46.61
 17     *        *      390 ms  216.239.49.82
 18   374 ms     *      374 ms  64.233.187.99

Trace complete.

Code: 
>tracert www.google.com

Tracing route to www.google.akadns.net [216.239.63.104]
over a maximum of 30 hops:

  1    38 ms    40 ms    40 ms  vic-58-3.mweb.co.za [196.2.45.81]
  2    32 ms    40 ms    40 ms  ndf-36-1.mweb.co.za [196.2.45.66]
  3    32 ms    40 ms    40 ms  core1-mweb-jhb-fa0-0.rtr.isnet.net [196.36.218.1
37]
  4    35 ms    40 ms    40 ms  168.209.0.133
  5    35 ms    40 ms    49 ms  core2b-rba-gi8-0-0.rtr.isnet.net [196.26.0.9]
  6   291 ms   293 ms   293 ms  168.209.0.142
  7   413 ms   302 ms   490 ms  core1b-ny.nmszone.is.co.za [168.209.244.3]
  8   285 ms   293 ms   293 ms  POS1-2.IG2.NYC4.ALTER.NET [208.192.177.205]
  9   291 ms   293 ms   293 ms  589.at-5-0-0.XR3.NYC4.ALTER.NET [152.63.22.14]
 10   285 ms   293 ms   312 ms  0.so-2-0-0.XL1.NYC4.ALTER.NET [152.63.17.29]
 11   288 ms   296 ms   293 ms  0.so-6-0-0.BR1.NYC4.ALTER.NET [152.63.21.77]
 12   288 ms   293 ms   359 ms  so-8-1.car1.NewYork1.Level3.net [209.244.160.181
]
 13   288 ms   293 ms   293 ms  ae-1-52.bbr2.NewYork1.Level3.net [4.68.97.33]
 14   363 ms   359 ms   359 ms  as-0-0.bbr1.SanJose1.Level3.net [64.159.1.133]
 15   363 ms   368 ms   368 ms  ge-10-1.ipcolo2.SanJose1.Level3.net [4.68.123.74
]
 16   354 ms   362 ms   368 ms  unknown.Level3.net [209.247.202.218]
 17   366 ms   359 ms   359 ms  66.249.94.27
 18   363 ms   359 ms   368 ms  216.239.49.66
 19   363 ms   368 ms   368 ms  216.239.63.104

Trace complete.

Chalk and cheese.
 
196.30.31.100 is the primary PDSN in JHB. 101 is the secondary.
 
To enlighten the less tech savie; is a PDSN a Packet Data Serving Node or what?

If it is what relevance would that have on these speed and proxy issues?
 
zepher said:
To enlighten the less tech savie; is a PDSN a Packet Data Serving Node or what?

If it is what relevance would that have on these speed and proxy issues?
Click to expand...

It was in answer to my question. The only relevance was that it used to appear on the first hop in the tracert report. For me, it no longer appears, or gives a timeout. For PAN, it's still there.
 
Yes it is a PDSN a Packet Data Serving Node.


And no it shouldn't have much influence over the latency.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X