problem with traceroute

[Mathias Zubek_1]

hello,

i have a little problem with traceroute, the destination is wrong:

traceroute to d0029670.prod.bfa (210.13.16.50), 30 hops max, 20 byte packets
1 Z1310126.prod.bfa (212.13.10.126)
2 220.50.77.105 (220.50.77.105)
3 220.20.45.106 (220.20.45.106)
4 220.80.77.106 (220.80.77.106)
5 B0029670.prod.bfa (210.13.16.49)

There is no errormessage.
The IP- Config from destination host is:

HP-UX11# netstat -i
Name Mtu Network Address
lan1:1 1500 210.13.16.48 D0029670
lan1 1500 210.13.16.48 B0029670
lo0 4136 127.0.0.0 localhost

HP-UX11# netstat -in
Name Mtu Network Address
lan1:1 1500 210.13.16.48 210.13.16.50
lan1 1500 210.13.16.48 210.13.16.49
lo0 4136 127.0.0.0 127.0.0.1


Any ideas ?

[Rainer von Bongartz]

looks like a DNS problem..

check with
nslookup 210.13.16.50
nslookup d0029670.prod.bfa
nslookup B0029670.prod.bfa
nslookup 210.13.16.49
results might be different

[Herve BRANGIER]

I think it's not an error : when you have 2 IP
(lan1 : @IP1 and lan1:1 : @IP2)on the same
network, traceroute send ICMP packets to the
@IP2, and the reply is sent to your host with
the IP of your lan1 (probably first in your
route). You receive a reply from your system
which says host is find but the reply come
from @IP1.

I think it's already the same problem when you
use more than on IP on a same network.

Herv?

[Jose Fdo. Garcia Alvare]

It's not a problem. You can have several virtual interfaces over one phisical interface (phys.: lan0, vir.: lan0:x). If you do a traceroute to lan0:x the final step of the command is lan0 which is the real one (physical). All the way out packets from virtual ones (lan0:x) goes trough physical one (lan0).