Routing through non-addressable space???
simon at higgs.com
Sat Jan 26 09:04:39 UTC 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: owner-nanog at merit.edu [mailto:owner-nanog at merit.edu] On Behalf Of
>Sent: Friday, January 25, 2002 8:43 PM
>To: 'Simon Higgs'; 'nanog at merit.edu'
>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
>mturpin at chartercom.com
>From: Simon Higgs [mailto:simon at higgs.com]
>Sent: Friday, January 25, 2002 8:47 PM
>To: nanog at merit.edu
>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 184.108.40.206 GSR1-SRP4-0.lsanhe4.we.mediaone.net 64 ms
>5 220.127.116.11 GSR2-SRP4-0.lsanhe3.we.mediaone.net 71 ms
>6 18.104.22.168 Unavailable 79 ms
>7 22.214.171.124 gbr2-p100.la2ca.ip.att.net 94 ms
>8 No response
>9 126.96.36.199 ggr1-p340.la2ca.ip.att.net 110 ms
>10 188.8.131.52 att-gw.la.home.net 112 ms
>11 184.108.40.206 wbb1-pos2-0.pop1.ca.home.net 120 ms
>12 10.252.25.118 Unavailable 134 ms
>13 220.127.116.11 Unavailable 141 ms
More information about the NANOG