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

As I said in the title, I want to access via ssh my VM from the host OS and the other way around (both OSes are ubuntu; 10.10 on the host, 9.10 on the guest)

To do so, I've configured a bridged NIC on the guest, attached it to my physical eth0 NIC and then statically assigned to both interfaces addresses of the same sub-network ( and

All the interfaces are up, with the right entry in route -n:

$ ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:1d:ba:65:10:12  
          inet addr:  Bcast:  Mask:
$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface     U     0      0        0 eth0

(this is on the host os - same situation on guest os).

The problem is that both machines doesn't "see" one each other:

$ ping
PING ( 56(84) bytes of data.
--- ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5040ms

What's the problem? What I'm missing?

share|improve this question
up vote 6 down vote accepted

Rather than a "bridged" adaptor from what I can tell what you need to set up is a "host-only" adaptor.

The bridged adaptor will cut out your host entirely and forward all data via your physical network card, even bypassing the NAT mode that is used by default. I expect this is most useful if you want to host a network-wide service on a virtual machine.

The "host-only" adaptor on the other hand sets up a mini dhcp server (for your guest to get an IP) and passes data only between the host and guest.

You would set up the host-only connection in the same way as any other connection, using ifconfig and dhcpcd.

share|improve this answer
Thanks, this solved everything :) – akappa Jun 29 '11 at 14:41

Ref: https//

VM -> Settings -> Network

Set the first adaptor as Host-Only

  • The host OS gets and the guests get

Set the 2nd adaptor with e.g. NAT

  • This will allow the guest OS to talk to the outer world
  • Every guest OS gets
  • Each guest OS can set its own port forwarding
  • to Of course, the same host ports should not be used for different guests
share|improve this answer

protected by Community Feb 9 at 7:07

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

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