Very Computer

by **shannonwhi..** » Wed, 10 Aug 2005 13:17:39

I'm trying to traceroute from a machine on our network to another
machine on an attached network.

Whenever I perform the traceroute I get the following output which is
quite useless. Is the a switch somewhere that I can turn on/off to
produce a logical output to trace the actual hops that I go over?

# traceroute h10109
traceroute to h10109 (10.116.XX.XX), 30 hops max, 38 byte packets
1 h10109 (10.116.XX.XX) 1.982 ms 2.177 ms 1.786 ms
2 h10109 (10.116.XX.XX) 3.217 ms 2.629 ms 6.268 ms
3 h10109 (10.116.XX.XX) 27.657 ms 27.100 ms 39.746 ms
4 h10109 (10.116.XX.XX) 82.549 ms 39.026 ms 35.047 ms
5 * * *

This just repeats the destination IP address instead of displaying the
hops...

THanks

by **dnoy** » Wed, 10 Aug 2005 23:36:21

> I'm trying to traceroute from a machine on our network to another
> machine on an attached network.

> Whenever I perform the traceroute I get the following output which is
> quite useless. Is the a switch somewhere that I can turn on/off to
> produce a logical output to trace the actual hops that I go over?

> # traceroute h10109
> traceroute to h10109 (10.116.XX.XX), 30 hops max, 38 byte packets
> 1 h10109 (10.116.XX.XX) 1.982 ms 2.177 ms 1.786 ms
> 2 h10109 (10.116.XX.XX) 3.217 ms 2.629 ms 6.268 ms
> 3 h10109 (10.116.XX.XX) 27.657 ms 27.100 ms 39.746 ms
> 4 h10109 (10.116.XX.XX) 82.549 ms 39.026 ms 35.047 ms
> 5 * * *

> This just repeats the destination IP address instead of displaying the
> hops...

> THanks

-n might work. those are probably DNS names you see.

--
Respectfully,

CL Gilbert

by **Moe Tr** » Thu, 11 Aug 2005 09:25:28

In the Usenet newsgroup comp.os.linux.networking, in article

>Whenever I perform the traceroute I get the following output which is
>quite useless. Is the a switch somewhere that I can turn on/off to
>produce a logical output to trace the actual hops that I go over?

># traceroute h10109
>traceroute to h10109 (10.116.XX.XX), 30 hops max, 38 byte packets
> 1 h10109 (10.116.XX.XX) 1.982 ms 2.177 ms 1.786 ms
> 2 h10109 (10.116.XX.XX) 3.217 ms 2.629 ms 6.268 ms
> 3 h10109 (10.116.XX.XX) 27.657 ms 27.100 ms 39.746 ms
> 4 h10109 (10.116.XX.XX) 82.549 ms 39.026 ms 35.047 ms
> 5 * * *

1. Why are you munging an RFC1918 address. It's a meaningless address
that no one can reach. All you are doing is making it harder to figure
out what your problem is.

2. IF THE IP ADDRESSES ARE DIFFERENT AT EACH HOP, there is something
b0rked in the DNS server reverse zone file.

3. IF THE IP ADDRESSES ARE THE SAME AT EACH HOP, this is probably a
firewall misconfiguration on h10109.

Quote:>This just repeats the destination IP address instead of displaying the
>hops...

Fire up 'tcpdump' with the -vv option to see more in the headers. You
may want to use -n (no DNS lookups) and -s to increase the size of the
packet capture. If you decide to post that output (no more than the
four hops should be needed) DO NOT MUNGE THE MAC ADDRESSES. They are of
no use in hacking - they get dropped at each router, you know - but there
could be clues there.

Old guy

Very Computer

Traceroute not displaying getway IP address within Hops

Traceroute not displaying getway IP address within Hops

Traceroute not displaying getway IP address within Hops

Traceroute not displaying getway IP address within Hops