Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Weird traceroute

I was doing a trace route from my machine to a particular website through windows xp, and I noticed some private IP addresses showing up in the trace, so I am just wondering why would 10.*.*.* ip address show up on the internet, I have never seen that before.

5 REPLIES

Re: Weird traceroute

Probably you didnt exit your own network. Can u post the trace report.

Hall of Fame Super Silver

Re: Weird traceroute

It is also possible that he went through some providers network where router interfaces as you transit the AS are configured with 10.*.*.* addresses.

HTH

Rick

New Member

Re: Weird traceroute

but why would you choose a private ip address for a router interface?

New Member

Re: Weird traceroute

1 <1 ms <1 ms <1 ms 192.168.30.1

2 <1 ms <1 ms <1 ms 192.168.30.1

3 57 ms 55 ms 56 ms 83.121.129.1 (Modified for protection)

4 60 ms 61 ms 60 ms 10.100.0.133

5 56 ms * * 10.16.150.1

6 74 ms 75 ms 76 ms pal6-eepad-1-dz.pal.seabone.net [195.22.197.25]

7 114 ms 114 ms 111 ms pal8-pal6-racc1.pal.seabone.net [195.22.218.210]

8 * * 124 ms mil50-pal8-racc3.mil.seabone.net [195.22.196.108]

9 136 ms 135 ms 134 ms fra50-mil50-racc1.fra.seabone.net [195.22.211.98]

10 133 ms 133 ms 133 ms fra7-fra50-racc1.fra.seabone.net [195.22.211.219]

11 127 ms 129 ms 131 ms teleglobe-1-ca-fra7.fra.seabone.net [89.221.34.30]

12 131 ms 130 ms 130 ms if-11-0-0.core1.PV1-Paris.teleglobe.net [80.231.65.66]

13 127 ms 129 ms 131 ms if-14-0-0.core3.PG1-Paris.teleglobe.net [80.231.73.5]

14 139 ms 142 ms 141 ms if-9-2.har1.PG1-Paris.teleglobe.net [80.231.72.46]

15 291 ms 203 ms 209 ms ix-10-5.har1.PG1-Paris.teleglobe.net [195.219.198.30]

16 150 ms 146 ms 147 ms te2-1-91-nb-voltaire-2.nerim.net [194.79.131.142]

17 147 ms 147 ms 142 ms vl2-swr301-mix-voltaire.nerim.net [62.4.16.17]

18 134 ms 129 ms 128 ms gi50-lgw101-hst-voltaire.nerim.net [194.79.130.66]

19 123 ms 126 ms 130 ms network.ippi.fr [195.5.254.146]

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

these two private addresses 10.100.0.133, 10.16.150.1 are showing up after the public ip address.

Thanks

New Member

Re: Weird traceroute

It looks like the 10.x.x.x addresses are from your ISP. Many ISP's use the 10.0.0.0 /8 range internally and for management purposes, and as long as it isn't advertised outside their own network there's no problem. If you do a trace towards yourself from a looking glaas those hops should show up with time-outs.

It's not neat to do it this way, as customers cannot use the private IP space those routers are in, but if it is a consumer ISP rather than a business ISP it rearely causes problems as most consumers use the 192.168.x.x private ranges.

226
Views
0
Helpful
5
Replies