Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I 'm trying to ping from my host PC (Windows 7) to Ubuntu 13.04 (VirtualBox). However, I get the error:

Pinging with 32 bytes of data:
Reply from TTL expired in transit.
Reply from TTL expired in transit.
Reply from TTL expired in transit.
Reply from TTL expired in transit.

Ping statistics for
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

tracert showed that there is a routing loop.

Tracing route to over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms
  2    42 ms    43 ms    42 ms []
  3     *       41 ms     * [178.59.10
  4    45 ms    42 ms    46 ms []
  5     *        *        *     Request timed out.
  6    46 ms    47 ms    44 ms []
  7     *       42 ms    42 ms [
  8    43 ms    44 ms    43 ms []
  9     *       43 ms    42 ms [
 10    46 ms    42 ms    44 ms []
 11     *        *        *     Request timed out.
 12    42 ms    43 ms    43 ms []
 13     *        *        *     Request timed out.
 14    45 ms    44 ms    42 ms []
 15     *        *       43 ms [
 16    46 ms    47 ms    47 ms []
 17     *        *        *     Request timed out.
 18    46 ms    45 ms    45 ms []
 19     *        *        *     Request timed out.
 20    44 ms    43 ms    43 ms []
 21     *        *       43 ms [
 22    44 ms    44 ms    46 ms []
 23    42 ms     *       43 ms [
 24    45 ms    43 ms    43 ms []
 25    43 ms     *       45 ms [
 26    54 ms    47 ms    44 ms []
 27    43 ms     *        * [
 28    43 ms    42 ms    46 ms []
 29     *        *       42 ms [
 30    43 ms    43 ms    44 ms []

Is there any way to resolve this problem?

VirtualBox Network Settings:

Host-Only Adapter

Promiscuous Mode: Deny

Cable connected

share|improve this question
Sorry for offtopic, but I can't find any other way to contact you. Why have you deleted your question about file history in google chrome? I have found an answer/ – Trolzen Oct 17 '13 at 2:37
Question is up. Thank's in advance. – dempap Oct 18 '13 at 22:46


You misconfigured the routing and you are leaking private IP addresses to the internet. Fix your routing. This might help.

Longer version:

IP numbers are unique. We only have 232 IPs and those are carefully allocated so that we know how to route IP packets from one location to another. If you connect to the Internet you must use one of these officially assigned IPs or IP ranges.

This is not always practical when you have more computers then IP addresses (and you typically only get a single IP as a home user). We work around that with RFC 1918. RFC 1918 describes a few IP ranges which should never be used publically on the Internet. This means that:

  • You can freely use them at home, but also
  • You should never leak these to the Internet. And
  • If you want to communicate from a host with an RFC1918 IP then you must use some special tricks (e.g. tunnels, a VPN, or NATting).

In your case you send packets directly from toward the internet. You can see the packet start at, then get routed to (which is probably your default gateway) and from there to should never see your packet. It should have been dropped at the edge of your home network.

However due to misconfiguration, does get the packet. For some reason it sends it to This can be either because they never expected to see this kind of wrong packet and this is's default gataway, or because also uses the range internally. also does not know what to do with it and sends it to, where the loop starts again.

Without careful consideration this would tie up the network between these two machines as they keep forwarding packets to each other. Eventually these last two machines will be so busy they they can not do anything else.

To prevent these kinds of problems IP datagrams have a field called TTL (time to live). Each time a packet/datagram passes a router this field gets decreased by one. If it reaches zero it gets dropped and a warning gets send back to the original sender. This causes the TTL expired in transit message to be displayed on your computer.

The fix is to properly configure your own border router (probably at It should not forward packets for any of the RFC1918 IPs (, or to the Internet.

Just what it should do with them depends on your home setup. There is not enough information in the post to answer that.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.