Trace Route last hop timeouts

[regardtv]

Hello Everyone,

Just a quick question concerning running trace routes back to your MyWireless connections.

I seem to not be able to actually reach my assigned IP. I reach a point somewhere before the modem - is it the tower ?

3 1022 ms 531 ms 540 ms s1-0-0chan9.gw2.jnb6.alter.net[196.7.77.217]
4 511 ms 981 ms 992 ms fe1-0.br1.jnb7.alter.net[196.31.17.162]
5 981 ms 391 ms 771 ms as3741.rba.is.co.za [196.30.228.242]
6 541 ms 981 ms 601 ms isl.nmszone.is.co.za [196.26.0.3]
7 912 ms 1021 ms 571 ms 168.209.18.62
8 441 ms 781 ms 841 ms gige-0-0-21.rtr-core4-stp.infosat.net [66.18.65.222]
9 561 ms 591 ms 580 ms 66.18.65.105
10 * * * Request timed out.

ie Where is 66.18.65.105 in the scheme of things ?

R

 

[Karnaugh]

I have a feeling Sentech are blocking certain ICMP towards the clients - This can account for the Path MTU discovery breakages.

- Colin Alston
colin at alston dot za dot org

"Warning: Use with extreme caution."

 

[flashvc]

The IP that's not responding to the traceroute is the PPP peer address.
It's the UDP traceroute that doesn't work. Try ICMP traceroute and it'll complete, but the last hop will be your IP instead of the PPP peer IP.

66.18.65.105 seems to be the Hub...

--