104

In setting up virtual machines with VirtualBox, I often want the following characteristics

  • VM has a static IP
  • host can access VM without port forwarding
  • VM can access the internet
  • I can move my laptop from network to network (e.g. from home to office to coffee shop) without worrying about securing or reconfiguring the VM

None of the VirtualBox network connection methods satisfies these requirements on their own.

  • NAT
    Requires port forwarding if you want to connect to the VM from the host.

  • Host-only
    The VM can not access the internet unless the host is a router.

  • Bridged
    Exposes the VM to the network; not portable.

7 Answers 7

117

I can get the setup I want by setting up two adapters on the vm.

VirtualBox 4.2.12
Ubuntu 12.04 guest

In VirtualBox > Preferences > Network, set up a host-only network.

Mine is called vboxnet0, it is manually configured:
ip 192.168.56.1
netmask 255.255.255.0
no dhcp

VirtualBox network configuration VirtualBox network configuration

Then, in the network settings for the virtual machine, set up two adapters:

Adapter 1
host only, vboxnet0

Adapter2
NAT

Boot the virtual machine and log in through the console VirtualBox provides.

Run this to see your adapters:

ls /sys/class/net

In my case the adapters were named eth1 and eth2 (and lo, the loopback interface).

Then, edit your network configuration.

sudoedit /etc/network/interfaces


# The loopback network interface
auto lo
iface lo inet loopback

# Host-only interface
auto eth1
iface eth1 inet static
        address         192.168.56.20
        netmask         255.255.255.0
        network         192.168.56.0
        broadcast       192.168.56.255

# NAT interface
auto eth2
iface eth2 inet dhcp

Note that eth1 has no default gateway specified. eth2 will get a default gateway from dhcp.


Update March 2018

See this answer from @Hugo14453 for an updated version that works with Ubuntu 17.10 and newer.

12
  • 1
    Update: VirtualBox 4.3 introduced a NAT service that looks like it might obviate the need for two interfaces. 6.4. Network Address Translation Service Jan 26, 2014 at 17:36
  • 4
    This helped me a lot, I use Virtualbox for development, and when I'm in my house, everything works correctly since I have the network setup to my likings, the nightmare starts when I move to another network (family, companies...), I have to change websites URLs, delete some systems files, reboot I don't know how many times and the list goes on. This solution doesn't care about your current network which is why I like it...Just plug your PC to any network and focus on your work. Jun 14, 2014 at 11:22
  • 1
    Thanks. Not defining a gateway address for the host-only interface solved my issues.
    – Florian
    Jul 21, 2016 at 10:20
  • 2
    Perfect. /etc/network/interfaces config was key THANKS!!!! Nov 1, 2016 at 20:35
  • 1
    "Note that eth1 has no default gateway specified. eth2 will get a default gateway from dhcp." <-- THIS COMMENT IS THE KEY.
    – Pere Pages
    Apr 11, 2017 at 11:18
19

Network configuration has changed in Ubuntu 17.10.1. You now use the netplan config.

I followed this guide here

As a migration of Christian's answer, do the following:

Create a new config file inside of /etc/netplan to hold your host-only adapter config.

e.g sudo nano /etc/netplan/02-netcfg.yaml

Enter the following to configure a static IP of 192.168.56.12 where enp0s3 is the name of your host-only adapter.

network:
    version: 2
    renderer: networkd
    ethernets:
        enp0s3:
            addresses:
                - 192.168.56.12/24
            dhcp4: no

Then run the following two commands:

sudo netplan generate
sudo netplan apply

NAT should work without configuration, run ifconfig to see the result:

enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.56.12  netmask 255.255.255.0  broadcast 192.168.56.255
        inet6 fe80::a00:27ff:fe06:6cdd  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:06:6c:dd  txqueuelen 1000  (Ethernet)
        RX packets 252  bytes 23076 (23.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 208  bytes 30015 (30.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp0s8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.3.15  netmask 255.255.255.0  broadcast 10.0.3.255
        inet6 fe80::a00:27ff:fe4d:a6b8  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:4d:a6:b8  txqueuelen 1000  (Ethernet)
        RX packets 95  bytes 94894 (94.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 85  bytes 7436 (7.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
2
  • 1
    Thanks! I added an update section to my old answer and linked to this new info. Mar 9, 2018 at 22:57
  • 1
    I have followed you solution, but miss nat support for enp0s8. I have manually added enable dhcp4 for enp0s8 in netplan and finally get both enp0s3 and enp0s8 up. Hope this will help somebody. Nov 13, 2018 at 13:50
17

I could solve my problem with a mix of Christian Long solution. I added 2 adapters:

Adapter 1 - NAT

Adapter 2 - host only, vboxnet0

The only diference was in VM's interfaces file:

sudoedit /etc/network/interfaces

# The loopback network interface
auto lo
iface lo inet loopback
# NAT
auto eth0
iface eth0 inet dhcp
# Host only
auto eth1
iface eth1 inet dhcp

In VirtualBox Network config I left DHCP checked.

After a VM reboot everything worked fine.

2
  • This works for me, but I want the VMs to have static IP addresses. The minute I do that, Internet stops working. If I set up both with DHCP, it works fine. How do I make the host-only interface get a static IP? Apr 7, 2014 at 23:27
  • Only one that worked. Thanks. +1 Aug 29, 2016 at 14:43
16

There is another simple way that we don't need to create a new NAT adapter

  1. On the host machine, please add the following iptables rules. This will forward packets through the host and on to the Internet:

    sudo iptables -A FORWARD -o eth0 -i vboxnet0 -s 192.168.56.0/24 -m conntrack --ctstate NEW -j ACCEPT 
    
    sudo iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
    
    sudo iptables -A POSTROUTING -t nat -j MASQUERADE
    
  2. You will also need to enable IP forwarding on the host by issuing the following command:

    sudo sysctl -w net.ipv4.ip_forward=1
    
5
  • 1
    This works only on a Linux host. Oct 18, 2016 at 20:57
  • We need the "dnsmasq" service running. In the link unix.stackexchange.com/a/384187/61742 we have complete information about what was suggested by @Danatela . Thanks! Aug 5, 2017 at 20:06
  • 1
    @EduardoLucio please give credits to Long Bui. I just edited this post to make it more readable.
    – Danatela
    Aug 7, 2017 at 10:38
  • @Long Bui Thank you for your contribution! Up! Up! Up! Up! Up! Up! =D Aug 7, 2017 at 13:36
  • @DerekMahar similarly, on Windows it's supposed to be ok to use the built-in Internet Connection Sharing (ICS), and maybe, even ip forwarding: serverfault.com/questions/929081/….
    – YumeYao
    Aug 23, 2022 at 13:48
4

I Just added 2 adapters:

Adapter 1 host only, vboxnet0

Adapter2 NAT

And it works perfect, I can access the virtual machine from the host, and I have internet on the vm.

1
  • I tried this solution with Android x86 but it will use only one adapter, I thought the first only but it is random. It is using either NAT or Host-only adapter, not both, any idea why? Compared to bridged adapter, NAT has the advantage that it will use my VPN connection configured on my host OS.
    – baptx
    Jun 18, 2021 at 16:01
2

Yeah I had this problem it was a total pain! But I solved it by simply installing Squid Cache Proxy server on my physical PC, and that way - my host-only internet virtualbox PCs could connect to the internet !

I did a quick 3 minute guide for anyone who wants to know how it works.

1
  • I used this solution also. Unfortunately it will only work for apps using HTTP protocol. For apps like WhatsApp on Android x86, we would need a SOCKS proxy like Dante but I can't get this solution working anymore, using redsocks: android.stackexchange.com/questions/221389/…
    – baptx
    Jun 18, 2021 at 15:05
0

In my case, I could not see the IP 192.168.250.1 on vboxnet0 (e.g. with "ip addr"), despite setting this in the host-only network settings in VirtualBox, until I created the file /etc/netplan/02-vbox.yaml containing

network:
    version: 2
    renderer: networkd
    ethernets:
        vboxnet0:
            addresses:
                - 192.168.250.1/24
            dhcp4: no

and ran "netplan generate && netplan apply"

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .