Aaron> snowy:~> ntping 209.112.190.5
Aaron> 1: 209.112.190.5 *
Aaron> 2: 209.112.190.5 *
Aaron> I poked a bit with ntping, and got this from 'ntping -D':
Aaron> ** sendloop 0
Aaron> ... recv got: rc 64
Aaron> ... got icmp type 209 code 112 id 2048 (0x800)
Aaron> * unknown icmp type discarded.
Aaron> ... recv got: rc 64
Aaron> ... got icmp type 209 code 112 id 0 (0x0)
Aaron> * unknown icmp type discarded.
Aaron> ** timediff: 1000 > 43
Well, I'd say ntping sends mangled packets or the 209.112.190.5 host
sends mangled responses. (i understand ntping runs on a linux box, but
the the target is a ???).
One diagnostic would be: are other targets ping'albe with ntping and
only this one target does not work (indicating the target is broken),
or is ntping generally unable to ping other hosts from this linux
platform (indicating ntping is broken) ?
Another good try would be a tcpdump to check what packets are actual
on the net. are 'echo requests' ok ? are the 'echo responses' ok ?
And can additionally check ntping with linux kernel greater than
~2.1.50 at home (hopefully before the weekend), because it's sure
possible something changed in the networking layer.
Erik
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.