From: Digital Yemeni (digital.yemeni@gmail.com)
Date: Sun Jun 24 2007 - 09:56:35 ART
Can anyone explain to me how an ISP has the RFC1918 addresses be used to
route internet traffic?
Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.x.x <------- My Cable Modem inside
interface
2 9 ms 18 ms 9 ms 10.2x.x.x <-------------My Cable ISP next
hop, RFC1918 address!
3 23 ms 6 ms 8 ms 172.2x.2x.x <-------------My Cable ISP next
hop, RFC1918 address!
4 14 ms 11 ms 8 ms 172.2x.2x.x <-------------My Cable ISP next
hop, RFC1918 address!
5 9 ms 8 ms 12 ms 172.2x.x.x <-------------My Cable ISP next
hop, RFC1918 address!
6 11 ms 13 ms 8 ms 203.x.x.x <-------------some router in the
Internet {could be the ISP edge Internet router!}
7 29 ms 17 ms 19 ms 203.x.x.x
8 46 ms 44 ms 50 ms 134.x.x.x
9 39 ms 47 ms 40 ms 202.x.x.x
10 71 ms 66 ms 70 ms 209.x.x.x
11 110 ms 97 ms 124 ms 66.x.x.x
:
:
19 256 ms 253 ms 255 ms eh-in-f99.google.com [72.14.207.99]
I can't see my public IP in the trace-route!! I mean, the next hope after my
Cable Modem inside IP [192.168.x.x] "theoretically" must be my public IP
address, but it's not!!! However, if i try to ping it (my public IP) from
somewhere in the internet i can reach it!
I know there must be some NAT going on @ the ISP but why is the case when i
already have a public IP? :)
Any explanation??!
Thanks in advance!
-- Best Regards! Digital, CCIE# to be assigned by Cisco when it collects enough $$ out of me! :p
This archive was generated by hypermail 2.1.4 : Sun Jul 01 2007 - 17:24:51 ART