failed to bring up eth1 ubuntu virtualbox

Preston Hagar prestonh at
Tue Apr 16 17:55:37 UTC 2013

On Sat, Apr 13, 2013 at 3:04 PM, jiten jha <jitenjha11 at>wrote:

> Dear Friends,
> I am try to configure openstack in ubuntu virtual box when I finished
> ubuntu 12.04.2 or 12.04.1 64 bit server .
> After that go to virtual box - system preferences - network and enable 2
> lan card vboxnet0 and vboxnet1 with ip address and
> after that vim /etc/network/interfaces
> # The Loopback network interface
> auto lo
> iface lo inet loopback
> # The Primary network interface
> auto eth0
> iface eth0 inet dhcp
> # Public interface
> auto eth1
> iface eth1 inet static
> address
> netmask
> network
> broadcast
> gateway
> # Private Interface
> auto eth2
> iface eth2 inet manual
> up ifconfig eth2 up
> I have search on google but same problem in 12.04.1 and 12.04.2 server .
> Please help me to solve the problem.
> --
> Thanks & Regards
> Jitendra Jha
> +91-7498370550
I'm not exactly clear on what is going on, but a couple of things I noticed
to point out:

1.  When you setup a new NAT network (which is what you are doing if you
are going to the main system preferences and creating vboxnet devices),
then the IPs for those devices become the gateway for your client machines.
 The client machines will need to have a different IP within that subnet.
 By default, when you create a vboxnet gateway, it will run a dhcp server
for client machines.  If you don't want that and want your client machine
to be static, then you need to turn off the dhcp server, or at least modify
the address pool range so that the static IP you assign your client isn't
in the address pool range.

2.  I'm not sure if you are giving us the /etc/network/interfaces of the
host machine or the client, but my guess is that it is the client.  It
won't be able to route since your IP is and your netmask is, then it will only see 10.112.*.* addresses.  Your have your
gateway at a address, so you will have trouble there.

My best advice is to not use NAT at all and set each client to use bridged
networking.  It will make the network device of each client show up on your
"normal" network (the same one your host is on) and you can give it an ip
within that same range (or let your DHCP server take over, if you have one).

If bridging doesn't work for some reason, you might start with using dhcp
on your client first (and making sure it is on in the vboxnet setup),
seeing if that works out okay, then trying to change
/etc/network/interfaces to static after you know that you have NAT setup
correctly in general.

If you do a

netstat -rn

in the guest when it is working (say via dhcp) it should give you the
default route to put on the gateway line.  An ifconfig should give you
acceptable values for the rest, although like I said before, when you
assign it static, be sure to either turn off the VirtualBox DHCP server, or
assign outside of the address pool range.

Hope this helps,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ubuntu-users mailing list