Arch Linux

Jeroen)Mathon

Member

From: Netherlands

Registered: 2013-08-29

Posts: 82

[Solved]VirtualBox 5.1.26-1 does not lease ipv4 adresses on HostOnly

Hey Everyone,

Currently i am running `VirtualBox 5.1.26-1` on my up to date Arch Linux installation,
I have a few VM's on my virtualbox running ArchLinux, untill recently i had no problem with HostOnly adaptors on virtualbox.

Currently i am facing the problem that the host-only adaptor is not leasing any ipv4 adresses, instead it leases a ipv6 adreses which is highly unpractical.

There also is a static IP being given to the clients that goes like 10.0.2.15, All vm's now have this ip, which they should not have.

These are my network interfaces, that are up at the moment:

4: virbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:86:24:3a brd ff:ff:ff:ff:ff:ff
    inet 10.1.0.1/24 brd 10.1.0.255 scope global virbr1
       valid_lft forever preferred_lft forever
5: virbr1-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr1 state DOWN group default qlen 1000
    link/ether 52:54:00:86:24:3a brd ff:ff:ff:ff:ff:ff
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
    link/none 
    inet 10.8.0.38 peer 10.8.0.1/32 brd 10.8.0.38 scope global tun0
       valid_lft forever preferred_lft forever
    inet6 fe80::86b4:9fe0:1d40:d4a2/64 scope link flags 800 
       valid_lft forever preferred_lft forever
7: vboxnet0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 192.168.56.1/24 brd 192.168.56.255 scope global vboxnet0
       valid_lft forever preferred_lft forever
    inet6 fe80::800:27ff:fe00:0/64 scope link 
       valid_lft forever preferred_lft forever

Does anyone have an idea on how to fix this problem and if it might be an issue with the virtualbox package.

I am also running a VPN on the host machine and have the following routes setted up:

default         gateway         0.0.0.0         UG    50     0        0 tun0
default         gateway         0.0.0.0         UG    20600  0        0 wlp1s0
10.1.0.0        0.0.0.0         255.255.255.0   U     0      0        0 virbr1
gateway         0.0.0.0         255.255.255.255 UH    50     0        0 tun0
helios          gateway         255.255.255.255 UGH   600    0        0 wlp1s0
192.168.0.0     0.0.0.0         255.255.255.0   U     600    0        0 wlp1s0
192.168.2.0     gateway         255.255.255.0   UG    600    0        0 wlp1s0
192.168.56.0    0.0.0.0         255.255.255.0   U     0      0        0 vboxnet0
home            gateway         255.255.255.255 UGH   600    0        0 wlp1s0

Update:
I tried to disable all the routes that i custom set on connect, but that did not work, it had no influence on the problem.

Update:
My other two VM's that are very old seem to have their own ip on the second interface(a host only) they do share the same ip on the NAT interface, i will continue to research what my fault on the new VM's was. and will post my solution if i find it.

Update Solution:
I found out that Host Only adaptors do not support DHCP, instead you need to manualy specify its ip.

Last edited by Jeroen)Mathon (2017-08-23 13:27:08)

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,456

Re: [Solved]VirtualBox 5.1.26-1 does not lease ipv4 adresses on HostOnly

Update Solution:
I found out that Host Only adaptors do not support DHCP, instead you need to manualy specify its ip.

Since when? See https://www.virtualbox.org/manual/ch06. … k_hostonly

In the VirtualBox graphical user interface, you can configure all these items in the global settings via "File" → "Preferences" → "Network", which lists all host-only networks which are presently in use. Click on the network name and then on the "Edit" button to the right, and you can modify the adapter and DHCP settings.

Jeroen)Mathon

Member

From: Netherlands

Registered: 2013-08-29

Posts: 82

Re: [Solved]VirtualBox 5.1.26-1 does not lease ipv4 adresses on HostOnly

Update Solution:
I found out that Host Only adaptors do not support DHCP, instead you need to manualy specify its ip.

Since when? See https://www.virtualbox.org/manual/ch06. … k_hostonly

In the VirtualBox graphical user interface, you can configure all these items in the global settings via "File" → "Preferences" → "Network", which lists all host-only networks which are presently in use. Click on the network name and then on the "Edit" button to the right, and you can modify the adapter and DHCP settings.

I figured that out, but on the newest version virtualbox just freezes crashes when trying to enable it.