Aaron> It happens the same with all targets. The .5 host happens to be
Aaron> the one I'm running it from. So, I would presume it's ntping
Aaron> that is broken.
Aaron> tcpdump stuff, first for linux 2.0.27 target:
Aaron> 12:08:21.300784 209.112.190.5 > 209.112.190.3: icmp: echo request
Aaron> 12:08:21.301899 209.112.190.3 > 209.112.190.5: icmp: echo reply
Aaron> [...]
Well, at least always a good packet is sent and the reply packet looks
good to. So the packet breaks in the kernel or in the ntping decoder.
Unfortunately, i was unable to reproduce the bug:
root@chappell:unix 34 > uname -a
Linux chappell 2.1.57 #88 Thu Sep 25 14:42:32 MET DST 1997 i586 unknown
root@chappell:unix 34 > ./ntping -V
Version: ntping v0.9n Sep 1996
root@chappell:unix 35 > ./ntping 194.45.135.2
1: 194.45.135.2 27 ms
This ping-target is a 2.0.30 box, other targets are working too
(SunOS, Solaris) and to the loopback address too.
Aaron> It has actually not worked since at least 2.1.42 or something
Aaron> like that. Possibly 2.1.48. I don't exactly recall, but it has
Aaron> been a while since it hasn't worked.
The only suggestion, that comes to my mind, is be to recompile ntping
and try again.
Maybe there are others on the mailing-list, having fail/success
reports about ntping under newer linux v2.1.x kernels ?
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.