North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
RE: Routing through non-addressable space???
- From: Simon Higgs
- Date: Sat Jan 26 04:07:27 2002
At 09:35 PM 1/25/02 -0600, you wrote:
Mmmmmm... this trace is from an @Work/Excite circuit that is about to go
dark. The "cable modem" is (as far as I can tell) the Cisco 2600 at the
customer site. Either that or @Work's customer gateway address.
Cable modems actually "have" two IP's: one rfc1918 that they use for
provisioning purposes and in the actual IP of the cable modem device,
one real IP that they pass on to the end-user's device. Many of the
newer cable modems are now showing the private IP in traces where
previously they'd pass and not respond to ICMP. As for why, who knows?
My best guess is to ease tracking down offending IP's vs. users.
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of
Sent: Friday, January 25, 2002 8:43 PM
To: 'Simon Higgs'; 'firstname.lastname@example.org'
Subject: RE: Routing through non-addressable space???
Routing through a cable interface that has a 10.x address as its primary
address would be my first guess, esp. due to the 24.x address.
ip address 10.x.x.x. x.x.x.x.x
ip address public.for.cpe.equip mask.mask.mask.mask secondary
From: Simon Higgs [mailto:email@example.com]
Sent: Friday, January 25, 2002 8:47 PM
Subject: Routing through non-addressable space???
Can someone explain this trace to me. How on earth did the 10.0.0.0
get inserted into the last hop?
# IP address Host name Round
4 188.8.131.52 GSR1-SRP4-0.lsanhe4.we.mediaone.net 64 ms
5 184.108.40.206 GSR2-SRP4-0.lsanhe3.we.mediaone.net 71 ms
6 220.127.116.11 Unavailable 79 ms
7 18.104.22.168 gbr2-p100.la2ca.ip.att.net 94 ms
8 No response
9 22.214.171.124 ggr1-p340.la2ca.ip.att.net 110 ms
10 126.96.36.199 att-gw.la.home.net 112 ms
11 188.8.131.52 wbb1-pos2-0.pop1.ca.home.net 120 ms
12 10.252.25.118 Unavailable 134 ms
13 184.108.40.206 Unavailable 141 ms