"Roach, Mark R." wrote: > > Don't quite understand this one, my system is running mon to monitor a few > servers/routers on my network, I have been getting excessive numbers of > alerts from this system when servers on my local subnet go down, this is > what I have discovered. > > If I ping a bad address outside my own subnet, I get nothing until I hit > ctrl+c, eg > > [mrroach@tncorpmrr001 mrroach]$ ping 208.128.168.26 > PING 208.128.168.26 (208.128.168.26) from 10.13.1.58 : 56(84) bytes of > data. > > --- 208.128.168.26 ping statistics --- > 16 packets transmitted, 0 packets received, 100% packet loss > > This, AFAIK, is correct. But if I ping a bad address in my own subnet I get > strange messages (after a few seconds) > > [mrroach@tncorpmrr001 mrroach]$ ping 10.13.1.6 > PING 10.13.1.6 (10.13.1.6) from 10.13.1.58 : 56(84) bytes of data. > From 10.13.1.58: Destination Host Unreachable <-- error #1 > From 10.13.1.58: Destination Host Unreachable <-- error #2 > From 10.13.1.58: Destination Host Unreachable <-- error #3 > > --- 10.13.1.6 ping statistics --- > 5 packets transmitted, 0 packets received, +3 errors, 100% packet loss > > And you can see, +3 errors listed at the end... why is this?
See above for errors. Your own box (10.13.1.58) is likely misconfigured. It should not be responding to an address which is not its own. To see all the gory packet details, try watching the net with tcpdump or ethereal. Pierre
