The IP addresses showed up in the traceroutes are the "source IP addresses"
in the returning packets. Normally, routers route packets using the
destination IP addresses in the packets. The destination IP address in the
returning packets is your machine's IP address, that how you were able to
receive the traceroute info, but the info displayed is the IP addresses of
the hosts who sent the returned packets, so you can still receive traffic
sourced from machines with private IP addresses.
HTH,
Rog
> -----Original Message-----
> From: Leigh Anne Chisholm [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, February 25, 2001 5:01 PM
> To: Cisco@Groupstudy. Com
> Subject: Private Internet Addressing
>
>
> I did a traceroute to one of US West's customers... got some
> interesting results:
>
> 13 206 ms 179 ms 123 ms
> gig0-0-0.phnx-sust1.phnx.uswest.net [206.80.192.253]
> 14 1016 ms 151 ms 975 ms 207.224.191.2
> 15 233 ms 124 ms 123 ms 192.168.8.1
> 16 151 ms 179 ms 123 ms 192.168.100.147
> 17 247 ms 192 ms 151 ms
> vdsl-130-13-102-120.phnx.uswest.net [130.13.102.120]
>
> RFC 1918 - "Address Allocation for Private Internets"
> indicates 192.168.0.0 through 192.168.255.255 (192.168/16
> prefix) is reserved
> for private internets. Hops 15 and 16 in my traceroute show
> that addresses within this range are being used publically.
>
> Did I miss something? Have the "for private use only" IP
> addresses now been given the green light to be used within
> the internet?
>
>
> -- Leigh Anne
>
>
>
>
> _________________________________
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
