Oh. I'd thought the ingress/egress filtering was being done on the individual cable modems as well. I realize I should have said 'local' instead of 'non-routable', oops. What I'm still wondering is why my traceroute goes that far into RR's network, especially since it doesn't seem to confuse things for me to use 192.168.0.0/24 addresses on my local network. (I get the same traceroute, but with a third RR host, with 192.168.0.1 and so forth) Is this just an artifact of the way Windows is routing? What's confusing me is that the hosts my traceroute goes through are public, routable IP addresses. Am I missing something here? Thanks to all who've replied so far -- this has been quite informative.
-----Original Message----- From: Hani Mustafa [mailto:[EMAIL PROTECTED]] Sent: Monday, July 22, 2002 12:19 PM To: Ian Webb; [EMAIL PROTECTED] Subject: Re: Strange traceroute output on Road Runner for an RFC 1918 address More often than not, network admins would set the egress/ingress filters for these addresses where it leaves/enters the network to/from the internet (rather than to/from customers). Ian Webb <[EMAIL PROTECTED]> wrote : > I get the following output when I do a traceroute from my Windows XP > machine, which is directly connected to a Road Runner cable modem > (Motorola Surfboard), to 192.168.100.1: > > C:\>tracert 192.168.100.1 > > Tracing route to 192.168.100.1 over a maximum of 30 hops > > 1 * * * Request timed out. > 2 62 ms 125 ms 66 ms 24.93.66.37 > 3 87 ms 220 ms * 24.93.66.150 > 4 * 24.93.66.177 reports: Destination host unreachable. > > This seems weird to me, since 192.168.100.1 is an RFC 1918 local address > space. I can't think of any valid reason that a packet destined for it > would go *two* hops into Road Runner's network before getting a > destination host unreachable. Is there something I'm missing? > > Thanks, > Ian ~Hani Mustafa
