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?
> > If I ping the same IP (x.x.77.201) from home (totally different IP
> > subnet) I get no response at all. The pings just fall into the void.
>
> Expected.
>
Can you tell me why this was expected behavior? As opposed to "Destination
Host Unreachable"?
> > Why is there a difference in the response I receive internally and
> > externally?
>
> Double-check x.x.77.216's config, especially the netmask.
> Any chance it's 255.255.255.240 or thereabouts...?
>
Its 128.252.77.216 , netmask 255.255.255.0
> What's the output of "route -n"...?
>
See top of email.
> > -Brian
>
> Pierre
Thanks again!
