• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 685
  • Last Modified:

Networking, traceroute on linux

I get the following:

-bash-3.2# ping 10.14.10.10
PING 10.14.10.10 (10.14.10.10) 56(84) bytes of data.
64 bytes from 10.14.10.10: icmp_seq=1 ttl=64 time=0.209 ms
64 bytes from 10.14.10.10: icmp_seq=2 ttl=64 time=0.247 ms

--- 10.14.10.10 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.209/0.228/0.247/0.019 ms
-bash-3.2#
-bash-3.2#
-bash-3.2# traceroute 10.14.10.10
traceroute to 10.14.10.10 (10.14.10.10), 30 hops max, 40 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
-bash-3.2#

Open in new window


Is this telling me I can ping 10.14.10.10, but its actually more than 30 hops from me ???

Can be so, its my gateway.  Am I misunderstanding something ?
0
Los Angeles1
Asked:
Los Angeles1
  • 6
  • 5
  • 2
  • +2
10 Solutions
 
Los Angeles1Author Commented:
Just realized this came from a VM, probably confused matters
0
 
southpau1Commented:
It probably means taht your default gateway does not accept or use ICMP.  Being that it is on a VM, it isn't surprising.

The stars mean no response

Try the traceroute from the host machine see what happens
0
 
HermaniCommented:
try traceroute -l
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
XaelianCommented:
No doesn't mean it's more then 30hops away,iit just says it will display max 30 hops. So don't worry.

You can't get a result of the traceroute. Can you try it on the host OS? Probably there is an error with the configuration of you network in the VM. It's not so surprising that it can't connect to the hops inside the VM.
0
 
Seaton007Commented:
You can also try the PATHPING command.
0
 
HermaniCommented:
try traceroute -l
should be traceroute -I ( capital I)

this way it uses the same packets as a normal ping command does.

Also , since the response from your ping is ttl=64 , I assume it's on the same Lan , and it's a Linux box.
0
 
southpau1Commented:
what is your NIC setting for the VM?  If it is currently bridged, try to change it to either NAT or static
0
 
Los Angeles1Author Commented:
could someone please post an example of the traceroute -l or traceroute -I
0
 
XaelianCommented:
http://linux.about.com/library/cmd/blcmdl8_traceroute.htm here you find all the options + examples. Doing this via mobile phone so can't give a screenshot.
0
 
southpau1Commented:
Greensburo - Have you tried the other recommendations, or are you focusing on that single possible solution?

-Try traceroute from host machine
-Change NIC settings for VM
-Try the PATHPING command
0
 
HermaniCommented:
could someone please post an example of the traceroute -l or traceroute -I
traceroute -I 10.14.10.10

Open in new window


Since both ping and traceroute -I use icmp echo requests , I can't see why a ping would work , and a traceroute won't.
0
 
southpau1Commented:
Hermani - with a ping, only the destination node is replying to ICMP.  with Traceroute, each intermediate hop is replying to ICMP, so if any of those devices are blocking or not using ICMP, they will not reply, and hence that particular hop will not be identified.

That is what is happening here.  It seems that on Greensburo's VM, the next hop is not replying.  This could be either his host machine or his router.  The host machien could have a firewall or otherwise be configured to not reply.  The router may not recognize the request because of the network settings on the VM.
0
 
HermaniCommented:
I fully agree with the first part,

but for the second part : how do you explain the ttl of 64 ?
64 bytes from 10.14.10.10: icmp_seq=1 ttl=64 time=0.209 ms

Open in new window

0
 
southpau1Commented:
That is the OS default for all TCP traffic....

But for traceroute it is altered to equal 0 in the first iteration, then 1, then 2...so on and so forth...
0
 
HermaniCommented:
yes I know  , so suppose the target machine is linux.( which has default TTL 64) , and the ping reply has TTL=64 , then the target machine is only one hop away. no ?
0
 
southpau1Commented:
No it is zero hops away, meaning it doesnt pass throughn a router, only switches. He is pinging a machine within his home network
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
  • 5
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now