Re: Strange traceroute output on Road Runner for an RFC 1918 address
From: root (sta@woh.rr.com)Date: 07/22/02
- Previous message: Panth3r: "RE: List Lurker Would Like To Learn More About Security Basics"
- In reply to: Ian Webb: "Strange traceroute output on Road Runner for an RFC 1918 address"
- Next in thread: Hani Mustafa: "Re: Strange traceroute output on Road Runner for an RFC 1918 address"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "root" <sta@woh.rr.com> To: "Ian Webb" <iwebb@carolina.rr.com>, <security-basics@securityfocus.com> Date: Mon, 22 Jul 2002 07:13:22 -0400
I remember re-doing my network and attempting to ping a lan ip and seeing
the request go out to the net. That was misconfiguration on my part as it
turned out.
When I ping 192.168.100.1 from my rr conencted pc,it goes to the rr internal
server,10.42.192.1. Then off to a 24.*.*.* ip,then lost. This all seems
normal to me. I notice on your tarcert it couldnt conenct to the first ip.
This may be whats making you wonder?
Now what I wonder...
Can I tracert to a legit rr internal ip? Awhile ago when I attempted to
sniff my network(without knowing I couldnt) I did manage to see the rr
internal ip'ed machine send out arp requests. Well,I'm off to check...
----- Original Message -----
From: "Ian Webb" <iwebb@carolina.rr.com>
To: <security-basics@securityfocus.com>
Sent: Sunday, July 21, 2002 5:26 PM
Subject: Strange traceroute output on Road Runner for an RFC 1918 address
> 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
>
>
- Previous message: Panth3r: "RE: List Lurker Would Like To Learn More About Security Basics"
- In reply to: Ian Webb: "Strange traceroute output on Road Runner for an RFC 1918 address"
- Next in thread: Hani Mustafa: "Re: Strange traceroute output on Road Runner for an RFC 1918 address"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
