1820710 Members
2788 Online
109627 Solutions
New Discussion юеВ

traceroute command

 
SOLVED
Go to solution
jpcast_real
Regular Advisor

traceroute command

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:

-Can anyone recommend me any tool to trace the trafic over one NIC.
-It seems traceroute does not rely on the local routing table . Am I right?


Dartanan:/> netstat -rnv
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
174.1.51.55/255.255.255.255 174.1.51.55 UH 0 lan900:1 4136
15.15.15.11/255.255.255.255 15.15.15.11 UH 0 lan0 4136
15.15.15.55/255.255.255.255 15.15.15.55 UH 0 lan0:1 4136
174.1.51.11/255.255.255.255 174.1.51.11 UH 0 lan900 4136
15.15.15.0/255.255.255.0 15.15.15.11 U 3 lan0 1500
15.15.15.0/255.255.255.0 15.15.15.55 U 3 lan0:1 1500
174.1.51.0/255.255.255.0 174.1.51.11 U 3 lan900 1500
174.1.51.0/255.255.255.0 174.1.51.55 U 3 lan900:1 1500
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 0
default/0.0.0.0 174.1.51.254 UG 0 lan900 0
Dartanan:/> traceroute 174.1.51.44
traceroute: Warning: Multiple interfaces found; using 15.15.15.55 @ lan0:1
traceroute to 174.1.51.44 (174.1.51.44), 30 hops max, 40 byte packets
1 15.15.15.44 (15.15.15.44) 0.453 ms 0.141 ms 0.120 ms
Here rests one who was not what he wanted and didn't want what he was
2 REPLIES 2
Hoefnix
Honored Contributor
Solution

Re: traceroute command

Hi,

Try to use ping -o

See next thread, also problem with multible NIC's.
Other tips in this one aswell:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=529013

HTH,
Peter
Elmar P. Kolkman
Honored Contributor

Re: traceroute command

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'.
Every problem has at least one solution. Only some solutions are harder to find.