Why is ping acting wonky?

[c567591]

On a client's box that we are trying to get setup to talk to the internet so we can ssh into the box, ping is acting wonky.

# ping 192.9.206.201
PING 192.9.206.201 (192.9.206.201): 56 data bytes
64 bytes from a3684 (192.9.206.9): icmp_seq=0 ttl=64 time=0 ms

The response is not from the router that I'm trying to ping, but the server itself.
# netstat -r
Routing tables
Destination Gateway Flags Refs Use Interface
default 192.9.206.201 UGS 0 0 net0
localhost localhost UH 4 53513 lo0
a3684 localhost UGHS 0 7 lo0
224 a3684 UCS 0 0 net0

(Sorry for the munged table)

Its running SCO Openserver 5.0.5

I have servers like this working just fine elsewhere. Never seen this behavior before.
Internally they telnet into it to use it and it works fine.

Anyone know what's up?

 

[PHV]

Usually a router doesn't reply to ICMP (ping) requests ...

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[c567591]

Also attempting to ping outside the network yeids no response.

 

[c567591]

It does from the windows workstations.
Even still, why is the wrong machine responding or appearing to respond?

 

[PHV]

The following is suspect:
default 192.9.206.201 UGS 0 [!]0[/!] net0
What is the ouput of ifcong -a ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[c567591]

Here it is:

net0: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.9.206.9 netmask ffffff00 broadcast 192.9.206.201
perf. params: recv size: 24576; send size: 24576; full-size frames: 1
ether 00:08:c7:9f:ad:6f
Though I think it may be that the broadcast address is the same as the router.
I am changing it and rebooting it now to see what happens. No clue why that would be set that way.

 

[PHV]

I agree, the brodcast should be 192.9.206.255

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[c567591]

Yep that was it.
The goofy broadcast address was messing things up.
Thanks for pointing me in the right direction.