my traceroute not responce but ping reply on same ip.

[aamir4u]

Hello,

my traceroute not responce but

ping reply on same ip.

1  *uatdata1 /#ping 10.10.34.70
PING 10.10.34.70: 64 byte packets
64 bytes from 10.10.34.70: icmp_seq=0. time=15. ms
64 bytes from 10.10.34.70: icmp_seq=1. time=14. ms
64 bytes from 10.10.34.70: icmp_seq=2. time=17. ms
64 bytes from 10.10.34.70: icmp_seq=3. time=16. ms
64 bytes from 10.10.34.70: icmp_seq=4. time=15. ms

----10.10.34.70 PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 14/15/17
uatdata1 /#traceroute 10.10.34.70
traceroute to 10.10.34.70 (10.10.34.70), 30 hops max, 40 byte packets
 1  * * *
 2  *uatdata1 /#

hot can solve the problem

tell me how traceroute works on same ip

Thanks

[Matti_Kurkela]

Ping and traceroute (may) use different protocols.

Ping uses the ICMP protocol (specifically, ICMP echo-request and echo-reply packets). Traceroute may use UDP, ICMP or even TCP.

All these protocols (ICMP, TCP and UDP) run on top of the IP protocol.

Network firewalls can be configured to accept ICMP but reject UDP, or vice versa.

The ICMP protocol has some other important functions too (path MTU discovery, connection error reporting), so ICMP is not usually completely blocked, although firewalls may limit the amount of accepted ICMP packets or restrict allowed ICMP message types if required.

On the other hand, typical traceroute probes look like UDP connection attempts to random ports, so if a firewall is configured to allow traffic to only a strictly limited number of UDP ports, traceroute is likely to fail.

Some versions of traceroute have the option of using ICMP instead of UDP: run "man traceroute" and read the man page to find out if your HP-UX traceroute has such an option available. If ping works, traceroute using ICMP might work too.

Traceroute using TCP protocol is usually a separate command (tcptraceroute), which is not a normal part of HP-UX. If you want one, you may find an old version in the Porting Archive:

http://hpux.connect.org.uk/hppd/hpux/Networking/Admin/tcptracerout-1.2/

[akio_kabutogi]

As HP-UX version and the patch level are not know, I may be wrong here. But if you are running some

olde patch level, then, you have to specify the interface explicitly like :

 # traceroute -i lan1 10.xx.xx.xx

when the system is multihomed. If my memory is correct, traceroute from old patch levels did not choose

proper interface automatically from the IP address specified.