Author Topic: Skuzzy re pings and traceroutes (Read 466 times)

214thCavalier · « **on:** January 08, 2005, 11:53:48 AM »

Noticed today while doing some plotting for your other thread that I am getting different ip's listed enroute when i run a ping and compare the results with a traceroute.

Normal ?

If this is not normal then who should i be blaming

fuzeman · « **Reply #1 on:** January 08, 2005, 12:26:54 PM »

Nope not normal. The router IPs from you to HTC should remain constant. Mine change at both Savis and Level3 on my pingplots.

Skuzzy · « **Reply #2 on:** January 08, 2005, 01:56:57 PM »

I would like to see some comparison traces showing this phenomenon. I would also need the precise time each was run.

EDIT: Nevermind. I saw what you are talking about. It all depends on if the IP address is just another IP address to the same interface or not. Routers are fun that way.

214thCavalier · « **Reply #3 on:** January 08, 2005, 03:22:22 PM »

Just to be clear.

If i run pings and tracert to the same ip (MA).

All the ips listed seem to be different until the target.

IE ping -r 9 to 216.91.187.39

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Paul>ping -r 9 216.91.187.39

Pinging 216.91.187.39 with 32 bytes of data:

Reply from 216.91.187.39: bytes=32 time=204ms TTL=240
Route: 213.208.116.216 ->
213.208.106.202 ->
195.149.20.141 ->
213.248.100.70 ->
213.248.74.213 ->
206.24.168.28 ->
208.172.2.99 ->
208.172.2.62 ->
216.91.187.35
Reply from 216.91.187.39: bytes=32 time=181ms TTL=240
Route: 213.208.116.216 ->
213.208.106.202 ->
195.149.20.141 ->
213.248.100.70 ->
213.248.74.213 ->
206.24.168.28 ->
208.172.2.99 ->
208.172.2.62 ->
216.91.187.35
Reply from 216.91.187.39: bytes=32 time=184ms TTL=240
Route: 213.208.116.216 ->
213.208.106.202 ->
195.149.20.141 ->
213.248.100.70 ->
213.248.74.213 ->
206.24.168.28 ->
208.172.2.99 ->
208.172.2.62 ->
216.91.187.35
Reply from 216.91.187.39: bytes=32 time=182ms TTL=240
Route: 213.208.116.216 ->
213.208.106.202 ->
195.149.20.141 ->
213.248.100.70 ->
213.248.74.213 ->
206.24.168.28 ->
208.172.2.100 ->
208.172.2.62 ->
216.91.187.35

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

And tracert to same gives.

C:\Documents and Settings\Paul>tracert 216.91.187.39

Tracing route to 216.91.187.39 over a maximum of 30 hops

1 1 ms 1 ms 1 ms SpeedTouch.lan [10.0.0.138]
2 19 ms 25 ms 21 ms lon1-adsl6.nildram.net [213.208.106.124]
3 20 ms 20 ms 22 ms lon1-10.nildram.net [213.208.106.195]
4 21 ms 22 ms 19 ms lon1-6.nildram.net [195.149.20.132]
5 19 ms 20 ms 19 ms ldn-b1-geth14-3.telia.net [213.248.100.69]
6 21 ms 23 ms 20 ms cw-01448-ldn-b1.telia.net [213.248.74.214]
7 132 ms 133 ms 128 ms dcr1-loopback.Chicago.savvis.net [208.172.2.99]
8 130 ms 129 ms 134 ms acr2-so-1-0-0.Chicago.savvis.net [208.172.3.86]
9 169 ms 167 ms 168 ms 208.172.1.202
10 172 ms 173 ms 173 ms 216.91.187.39

Trace complete.

Tests ran approx a minute apart.

Just to clear it up a bit.

Ping.-r 9 gives.

1: 213.208.116.216 ->
2: 213.208.106.202 ->
3: 195.149.20.141 ->
4: 213.248.100.70 ->
5: 213.248.74.213 ->
6: 206.24.168.28 ->
7: 208.172.2.99 ->
8: 208.172.2.62 ->
9: 216.91.187.35
10: 216.91.187.39

And tracert gives.

1: 213.208.106.124
2: 213.208.106.195
3: 195.149.20.132
4: 213.248.100.69
5: 213.248.74.214
6: 208.172.2.99
7: 208.172.3.86 (this hop varies between 208.172.3.86 and .82)
8: 208.172.1.202
9: 216.91.187.39

fuzeman · « **Reply #4 on:** January 24, 2005, 09:46:34 PM »

Another related question. How do we know if its the same router with a different port/interface?
Example: an IP address is A.B.C.D if the D varies I'd assume its the same router. Is it still ok if both C and D change?
Does the DNSName have to change for it to be considered 'wacked'?
{ passes the aspirin to Skuzzy }

Swoop · « **Reply #5 on:** January 25, 2005, 06:22:28 PM »

I'm looking forward to this one.....