ntping's trace and ttl function hopefully fixed for HP-UX

Erik Schoenfelder (schoenfr@data)
Fri, 24 Jun 94 17:18:21 +0200

Hi!

With a deep look into a traceroute sources for HP-UX, we have changed
ntping accordingly.
ntpings -trace and -ttl functions seemed to be broken.

This should provide better results from the IP-Discoverer's
Discover-Net and Discover-Route function and correct results from
IP-Troubleshooter's Trace-Route function.

HP-UX uses a normal udp datagram socket with a special setsockopt call
to set the ttl time for an outgoing packet.
The other un*x's are using a raw socket with raw-protocol allowing any
ip-datagram to be sent.

Anyway, now this should be fixed, but it's untested, because we have
no root access to HP Workstations.

A tcpdump showed, that the trace and ttl packets a correcly sent, but
if the received time-limit-exceeded and port-unrechable icmp packets
are correctly received and decoded is not tested.

Anyone who is interested may fetch

ftp.ibr.cs.tu-bs.de:/pub/local/ntping-0.8.tar.gz

It extracs in an ntping directory and has a standalone configure
script.

You may run:

./configure [ --prefix=<your prefix> ]
make

and test with:
echo '-ttl 1 134.169.34.1' | ./ntping -b

expect a result like:

{134.169.34.12 5}
^^^^^^^^^^^^^
and this address should be the next hop to our site; ie. your gateway.
and:
echo '-ttl 24 134.169.34.1' | ./ntping -b

should return the destination host; expect a result like:

{134.169.34.1 891}

Additionally you may test it with a

make check
and
make lcheck

and examine the output.

If it works, install with

make install

If it's still broken, please send us a hint, some output, error
messages, tcpdumps or at least a handkerchief :)

Thanks a lot, Erik