brian wrote:
>
> Thanks for the responses all. Everything is working correctly, this was a
> question of curiosity, not troubleshooting.
>
> The FW is not blocking any ping responses. And the x.x. represent public IP's
> of 128.252.77.1-255. My netmask is 255.255.255.0
>
> Here is the output from an netstat -nr:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt Iface
> 128.252.77.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo
> 0.0.0.0 128.252.77.254 0.0.0.0 UG 40 0 0 eth0
>
> I will ask some more questions for clarification in-line.
> -Brian
>
> On Tuesday 19 June 2001 16:51, you wrote:
> > brian wrote:
> > > Can someone explain something about the response I get from some ping
> > > test?
> > >
> > > At work I have the whole Class C subnet x.x.77.1-255. When I ping from an
> > > internal PC (x.x.77.216) to an IP that no PC's are using(x.x.77.201), I
> > > get a resonse of "Destination Host Unreachable".
> >
> > This means the destination is not in your routing table which is checked
> > before ever trying to send a ping into the local void.
> >
>
> Aren't all IP's 128.252.77.1-255 represented in my routing table?
Yes. In fact, *ALL* IPs are represented by default (0.0.0.0/0).
Oops... it's "connect: Network is unreachable" that you get when the route is
missing...
I'd have to double-check; but IIRC, "Destination Host Unreachable" should be the
result of getting an ICMP error response to your ping... the problem is that
this can't come from the destination host itself if it doesn't exist, so some
other possibly misconfigured machine is responding...?
Use tcpdump or ethereal to see what is happening on the wire...
NOTE: not all network problems are in the machine you are debugging from; some
problems can be caused by other, misconfigured hosts/routers responding
inappropriately...
Pierre
[snip]
> > > -Brian
> >
> > Pierre
>
> Thanks again!
