https://community.hpe.com/t5/operating-system-hp-ux/traceroute-command/m-p/3237879#M173156 Hi,<BR /><BR />Try to use ping -o<BR /><BR />See next thread, also problem with multible NIC's.<BR />Other tips in this one aswell:<BR /><A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=529013" target="_blank">http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=529013</A><BR /><BR />HTH,<BR />Peter Fri, 02 Apr 2004 05:06:44 GMT Hoefnix 2004-04-02T05:06:44Z https://community.hpe.com/t5/operating-system-hp-ux/traceroute-command/m-p/3237878#M173155 I have two network cards on my server and I want to test if the trafic between two systems is performed by one network card or the other one. I have splitted the connecction and it seems to work but when I execute traceroute to other server with the same characteristics it seems to use another network card that it was supposed ... Two questions:<BR /><BR />-Can anyone recommend me any tool to trace the trafic over one NIC.<BR />-It seems traceroute does not rely on the local routing table . Am I right?<BR /><BR /><BR />Dartanan:/&gt; netstat -rnv<BR />Routing tables<BR />Dest/Netmask Gateway Flags Refs Interface Pmtu<BR />127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136<BR />174.1.51.55/255.255.255.255 174.1.51.55 UH 0 lan900:1 4136<BR />15.15.15.11/255.255.255.255 15.15.15.11 UH 0 lan0 4136<BR />15.15.15.55/255.255.255.255 15.15.15.55 UH 0 lan0:1 4136<BR />174.1.51.11/255.255.255.255 174.1.51.11 UH 0 lan900 4136<BR />15.15.15.0/255.255.255.0 15.15.15.11 U 3 lan0 1500<BR />15.15.15.0/255.255.255.0 15.15.15.55 U 3 lan0:1 1500<BR />174.1.51.0/255.255.255.0 174.1.51.11 U 3 lan900 1500<BR />174.1.51.0/255.255.255.0 174.1.51.55 U 3 lan900:1 1500<BR />127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 0<BR />default/0.0.0.0 174.1.51.254 UG 0 lan900 0<BR />Dartanan:/&gt; traceroute 174.1.51.44<BR />traceroute: Warning: Multiple interfaces found; using 15.15.15.55 @ lan0:1<BR />traceroute to 174.1.51.44 (174.1.51.44), 30 hops max, 40 byte packets<BR /> 1 15.15.15.44 (15.15.15.44) 0.453 ms 0.141 ms 0.120 ms Fri, 02 Apr 2004 04:57:14 GMT https://community.hpe.com/t5/operating-system-hp-ux/traceroute-command/m-p/3237878#M173155 jpcast_real 2004-04-02T04:57:14Z https://community.hpe.com/t5/operating-system-hp-ux/traceroute-command/m-p/3237879#M173156 Hi,<BR /><BR />Try to use ping -o<BR /><BR />See next thread, also problem with multible NIC's.<BR />Other tips in this one aswell:<BR /><A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=529013" target="_blank">http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=529013</A><BR /><BR />HTH,<BR />Peter Fri, 02 Apr 2004 05:06:44 GMT https://community.hpe.com/t5/operating-system-hp-ux/traceroute-command/m-p/3237879#M173156 Hoefnix 2004-04-02T05:06:44Z https://community.hpe.com/t5/operating-system-hp-ux/traceroute-command/m-p/3237880#M173157 Traceroute uses the first interface it finds, independent of routes. That's why you have this problem. As Peter mentions, ping -o is a way to know the real 'route'. Fri, 02 Apr 2004 05:09:52 GMT https://community.hpe.com/t5/operating-system-hp-ux/traceroute-command/m-p/3237880#M173157 Elmar P. Kolkman 2004-04-02T05:09:52Z