dhcp private_network fails on virtualbox #3083

Closed
phinze opened this Issue Mar 8, 2014 · 70 comments

Comments

Projects
None yet
@phinze
Member

phinze commented Mar 8, 2014

Problem

With a fresh VirtualBox install, adding a private network with type: :dhcp fails with the following error:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["dhcpserver", "add", "--ifname", "vboxnet0", "--ip", "172.28.128.2", "--netmask", "255.255.255.0", "--lowerip", "172.28.128.3", "--upperip", "172.28.128.254", "--enable"]

Stderr: VBoxManage: error: DHCP server already exists

Subsequent boots fail with a different message:

A host only network interface you're attempting to configure via DHCP
already has a conflicting host only adapter with DHCP enabled. The
DHCP on this adapter is incompatible with the DHCP settings. Two
host only network interfaces are not allowed to overlap, and each
host only network interface can have only one DHCP server. Please
reconfigure your host only network or remove the virtual machine
using the other host only network.

Steps to repro

Fresh install of Vagrant 1.4.3 and VirtualBox 4.3.6.

Minimal Vagrantfile:

# force virtualbox provider
ENV['VAGRANT_DEFAULT_PROVIDER'] = 'virtualbox'

Vagrant.configure('2') do |config|
  config.vm.box     = 'precise64'
  config.vm.box_url = 'http://files.vagrantup.com/precise64.box'
  config.vm.network 'private_network', type: :dhcp
end

Error message will appear on first vagrant up. My test host is OS X but I bet you this occurs on all hosts.

Explanation

VirtualBox ships with an initial dhcpserver seeded in its config [1].

$ VBoxManage list dhcpservers
NetworkName:    HostInterfaceNetworking-vboxnet0
IP:             192.168.56.100
NetworkMask:    255.255.255.0
lowerIPAddress: 192.168.56.101
upperIPAddress: 192.168.56.254
Enabled:        Yes

The hostonlyifs settings ship empty.

When encountering a private network with type: :dhcp, Vagrant sees this HostInterfaceNetworking-vboxnet0 dhcpserver and assumes that it is valid and ready to be attached to vboxnet0. But vboxnet0 was just created and has an IP address of 172.28.128.1.

So the error message comes from VirtualBox yelling that you can't assign a dhcpserver with an IP address outside the network of an adapter.

But the error occurs after the hostonlyif has been created, so it's leaked to subsequent boots, which is why the error message changes.

What now?

We have a couple of options to solve this:

  1. Petition VirtualBox to ship with an empty dhcpservers config
  2. Add code to Vagrant to clean up this default dhcpserver
  3. Add code to Vagrant to get smarter about dhcpservers with inconsistent IP addresses, possibly suggesting action to the user to fix

Workaround

Removing the default dhcpserver from VirtualBox solves all these collision problems.

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0

[1] Here's the code that seeds the dhcpserver: https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/xml/Settings.cpp#L1506

@bchavet

This comment has been minimized.

Show comment
Hide comment
@bchavet

bchavet Mar 19, 2014

The workaround that I am using is to run the following before the first vagrant up

VBoxManage hostonlyif create

If this is a fresh VirtualBox installation, this creates a new vboxnet0 interface that gets the default dhcp server linked, and Vagrant can proceed with creating its own at vboxnet1. If this is an already-primed VirtualBox installation, this will just result in an extra, unused interface. This is a pretty minor side effect until a more graceful solution can be worked out.

bchavet commented Mar 19, 2014

The workaround that I am using is to run the following before the first vagrant up

VBoxManage hostonlyif create

If this is a fresh VirtualBox installation, this creates a new vboxnet0 interface that gets the default dhcp server linked, and Vagrant can proceed with creating its own at vboxnet1. If this is an already-primed VirtualBox installation, this will just result in an extra, unused interface. This is a pretty minor side effect until a more graceful solution can be worked out.

@AdamKalnas

This comment has been minimized.

Show comment
Hide comment
@AdamKalnas

AdamKalnas Apr 23, 2014

Thanks for posting this, it helped me get what I needed to get vagrant setup on Ubuntu 14.04.

FWIW.. this did not work for me

VBoxManage hostonlyif create

While this did work 👍

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0

Thanks for posting this, it helped me get what I needed to get vagrant setup on Ubuntu 14.04.

FWIW.. this did not work for me

VBoxManage hostonlyif create

While this did work 👍

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0
@mitchellh

This comment has been minimized.

Show comment
Hide comment
@mitchellh

mitchellh May 5, 2014

Member

Closing due to inactivity. Still a bug but its one I never hear about (I think only if DHCP is used?) and seems pretty low priority.

Member

mitchellh commented May 5, 2014

Closing due to inactivity. Still a bug but its one I never hear about (I think only if DHCP is used?) and seems pretty low priority.

@mitchellh mitchellh closed this May 5, 2014

@tmm1

This comment has been minimized.

Show comment
Hide comment
@tmm1

tmm1 Jun 3, 2014

Ran into this as well and the VBoxManage dhcpserver remove trick worked. If a proper fix is not planned, perhaps the command (or a link to this issue) could be added to the lengthy message vagrant spits up when the error is encountered.

tmm1 commented Jun 3, 2014

Ran into this as well and the VBoxManage dhcpserver remove trick worked. If a proper fix is not planned, perhaps the command (or a link to this issue) could be added to the lengthy message vagrant spits up when the error is encountered.

@YmerejRedienhcs

This comment has been minimized.

Show comment
Hide comment
@YmerejRedienhcs

YmerejRedienhcs Jun 10, 2014

I experienced this too. I didn't explicitly choose DHCP, I just did a default install of virtualbox on my OSX machine. I agree: if you're not going to fix it, it would be nice for you to document the workaround in the error message. As for priority, it stopped my vagrant deployment from working. To me, who is affected by it, that's higher than "pretty low priority".

I experienced this too. I didn't explicitly choose DHCP, I just did a default install of virtualbox on my OSX machine. I agree: if you're not going to fix it, it would be nice for you to document the workaround in the error message. As for priority, it stopped my vagrant deployment from working. To me, who is affected by it, that's higher than "pretty low priority".

@jwieringa

This comment has been minimized.

Show comment
Hide comment
@jwieringa

jwieringa Jun 13, 2014

A default installation of Vagrant 1.6.3 and VirtualBox 4.3.12 resulted in this error for me too. A link to this issue would work for me.

The following command resolved the issue for me:

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0

👍 for all for the help.

A default installation of Vagrant 1.6.3 and VirtualBox 4.3.12 resulted in this error for me too. A link to this issue would work for me.

The following command resolved the issue for me:

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0

👍 for all for the help.

@ThomWright

This comment has been minimized.

Show comment
Hide comment
@ThomWright

ThomWright Jun 27, 2014

I had this issue today, I agree with @YmerejRedienhcs - what would it take for this to become higher priority than "pretty low"?

I had this issue today, I agree with @YmerejRedienhcs - what would it take for this to become higher priority than "pretty low"?

@rjmunro

This comment has been minimized.

Show comment
Hide comment
@rjmunro

rjmunro Jun 27, 2014

Please increase priority of this. It happens on a basic new installation, it's going to break for all new developers / designers etc. on my projects.

I found the suggested workaround fixed it for me:

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0

rjmunro commented Jun 27, 2014

Please increase priority of this. It happens on a basic new installation, it's going to break for all new developers / designers etc. on my projects.

I found the suggested workaround fixed it for me:

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0
@al3x-edge

This comment has been minimized.

Show comment
Hide comment
@al3x-edge

al3x-edge Jul 9, 2014

The VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 command worked for me as well. +1.

The VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 command worked for me as well. +1.

@Magrath

This comment has been minimized.

Show comment
Hide comment

Magrath commented Jul 11, 2014

+1

@jwhitcraft

This comment has been minimized.

Show comment
Hide comment

+1

@jmvrbanac

This comment has been minimized.

Show comment
Hide comment

+1

@ms-tg

This comment has been minimized.

Show comment
Hide comment

ms-tg commented Jul 30, 2014

👍

@kensykora

This comment has been minimized.

Show comment
Hide comment

+1

@tclift

This comment has been minimized.

Show comment
Hide comment
@tclift

tclift Aug 4, 2014

+1 - bit me, found this issue, command fixed

tclift commented Aug 4, 2014

+1 - bit me, found this issue, command fixed

@pagojo

This comment has been minimized.

Show comment
Hide comment
@pagojo

pagojo Aug 18, 2014

This seems pretty basic functionality which needs to be in the command line and at least in the documentation I think. Thanks for the good work btw :-)

pagojo commented Aug 18, 2014

This seems pretty basic functionality which needs to be in the command line and at least in the documentation I think. Thanks for the good work btw :-)

@chetzof

This comment has been minimized.

Show comment
Hide comment
@chetzof

chetzof Aug 20, 2014

also encountered this bug
the command fixed it

chetzof commented Aug 20, 2014

also encountered this bug
the command fixed it

@minonne

This comment has been minimized.

Show comment
Hide comment

minonne commented Aug 26, 2014

+1

@phinze

This comment has been minimized.

Show comment
Hide comment
@phinze

phinze Aug 26, 2014

Member

Hey folks! Filed https://www.virtualbox.org/ticket/13323 upstream, we'll see what uncle VBox has to say! 👴

Member

phinze commented Aug 26, 2014

Hey folks! Filed https://www.virtualbox.org/ticket/13323 upstream, we'll see what uncle VBox has to say! 👴

@dchesterman

This comment has been minimized.

Show comment
Hide comment
@dchesterman

dchesterman Sep 10, 2014

This happened with me with the default Vagrantfile create from Berkshelf.

This happened with me with the default Vagrantfile create from Berkshelf.

@jolankester

This comment has been minimized.

Show comment
Hide comment
@rsrchboy

This comment has been minimized.

Show comment
Hide comment
@rsrchboy

rsrchboy Sep 23, 2014

+1 -- frustrating couple days spent hunting down what was actually going on.

+1 -- frustrating couple days spent hunting down what was actually going on.

@swashcap

This comment has been minimized.

Show comment
Hide comment

swashcap commented Oct 5, 2014

+1

@liammcdermott

This comment has been minimized.

Show comment
Hide comment
@liammcdermott

liammcdermott Oct 5, 2014

Vagrant should not be in a broken state when you first try to use it (if the Vagrantfile uses :private_network, type: dhcp).

This is just my opinion, but Vagrant should either support the feature or disable it, having to use esoteric workarounds to get going makes Vagrant look bad.

Vagrant should not be in a broken state when you first try to use it (if the Vagrantfile uses :private_network, type: dhcp).

This is just my opinion, but Vagrant should either support the feature or disable it, having to use esoteric workarounds to get going makes Vagrant look bad.

@senz

This comment has been minimized.

Show comment
Hide comment

senz commented Nov 6, 2014

+1

@JeanMertz

This comment has been minimized.

Show comment
Hide comment
@JeanMertz

JeanMertz Nov 7, 2014

👍 We just ran into this at the office. Unsure how it started (I've never seen it happen), but my colleague just had this issue. Using VBoxManage ... remove ... solved the issue.

👍 We just ran into this at the office. Unsure how it started (I've never seen it happen), but my colleague just had this issue. Using VBoxManage ... remove ... solved the issue.

@andreychernih

This comment has been minimized.

Show comment
Hide comment
@harmon

This comment has been minimized.

Show comment
Hide comment

harmon commented Nov 14, 2014

+1

@etrepum

This comment has been minimized.

Show comment
Hide comment

etrepum commented Nov 20, 2014

+1

@jasonm-makerbot

This comment has been minimized.

Show comment
Hide comment
@jasonm-makerbot

jasonm-makerbot Jan 9, 2015

Yes I am on the latest version of Vagrant:
jason.meredith@JasonMeredithMBP:[Preferences] $ vagrant --version
Vagrant 1.7.1

On Jan 5, 2015, at 6:09 PM, Paul Hinze notifications@github.com wrote:

@jasonm-makerbot the fix for this was merged - are you still hitting this on latest vagrant?


Reply to this email directly or view it on GitHub.

NOTICE: This email may contain information that is confidential or
attorney-client privileged and may constitute inside information or trade
secrets. The contents of this email are intended only for the recipient(s)
listed above. If you are not the intended recipient, you are directed not
to read, disclose, distribute or otherwise use this transmission. If you
have received this email in error, please notify the sender immediately and
delete the transmission. Delivery of this message is not intended to waive
any applicable privileges.

Yes I am on the latest version of Vagrant:
jason.meredith@JasonMeredithMBP:[Preferences] $ vagrant --version
Vagrant 1.7.1

On Jan 5, 2015, at 6:09 PM, Paul Hinze notifications@github.com wrote:

@jasonm-makerbot the fix for this was merged - are you still hitting this on latest vagrant?


Reply to this email directly or view it on GitHub.

NOTICE: This email may contain information that is confidential or
attorney-client privileged and may constitute inside information or trade
secrets. The contents of this email are intended only for the recipient(s)
listed above. If you are not the intended recipient, you are directed not
to read, disclose, distribute or otherwise use this transmission. If you
have received this email in error, please notify the sender immediately and
delete the transmission. Delivery of this message is not intended to waive
any applicable privileges.

phinze added a commit that referenced this issue Jan 21, 2015

providers/virtualbox: read netmask from dhcpservers
This should fix the cleaning up of the default VirtualBox dhcpserver,
which we've been fighting with for ages over in #3083. We were checking
for a structure _including_ a netmask, but the driver was not populating
netmask.
@phinze

This comment has been minimized.

Show comment
Hide comment
@phinze

phinze Jan 22, 2015

Member

Alright I think this is finally ready to be made a thing of the past! #5233 fixed the lingering bug in the cleanup code and will come out in vagrant 1.7.3

Member

phinze commented Jan 22, 2015

Alright I think this is finally ready to be made a thing of the past! #5233 fixed the lingering bug in the cleanup code and will come out in vagrant 1.7.3

@phinze phinze closed this Jan 22, 2015

@harmon

This comment has been minimized.

Show comment
Hide comment
@harmon

harmon Jan 22, 2015

Yay! Thanks bud! 👍

harmon commented Jan 22, 2015

Yay! Thanks bud! 👍

@justinsteele

This comment has been minimized.

Show comment
Hide comment
@justinsteele

justinsteele Jan 22, 2015

Interesting that today is the first time I tried dhcp, immediately ran into this, and 15 minutes prior it was fixed. Thanks!! 👍

Interesting that today is the first time I tried dhcp, immediately ran into this, and 15 minutes prior it was fixed. Thanks!! 👍

@berinle

This comment has been minimized.

Show comment
Hide comment
@berinle

berinle Jan 23, 2015

Just got bitten by this. Thanks for the workaround (since Vagrant 1.7.3 is not out yet) and the fix in 1.7.3 when it is out.

berinle commented Jan 23, 2015

Just got bitten by this. Thanks for the workaround (since Vagrant 1.7.3 is not out yet) and the fix in 1.7.3 when it is out.

@davidrapin

This comment has been minimized.

Show comment
Hide comment
@davidrapin

davidrapin Feb 3, 2015

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 worked for me.

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 worked for me.

@aztlan2k

This comment has been minimized.

Show comment
Hide comment
@aztlan2k

aztlan2k Feb 26, 2015

+1
VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0
worked for me too.

+1
VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0
worked for me too.

@rons77

This comment has been minimized.

Show comment
Hide comment
@rons77

rons77 Mar 2, 2015

worked like a charm!

rons77 commented Mar 2, 2015

worked like a charm!

@sandstrom

This comment has been minimized.

Show comment
Hide comment
@sandstrom

sandstrom Mar 22, 2015

Thanks @phinze! ⛵️

Thanks @phinze! ⛵️

@mmcfarland mmcfarland referenced this issue in WikiWatershed/model-my-watershed Mar 26, 2015

Merged

Create skeleton Django application #2

@DennisTerrell

This comment has been minimized.

Show comment
Hide comment
@DennisTerrell

DennisTerrell Apr 1, 2015

Also got this error with Vagrant 1.7.2.

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 worked like a champ.

Also got this error with Vagrant 1.7.2.

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 worked like a champ.

@ymkim92

This comment has been minimized.

Show comment
Hide comment

ymkim92 commented Apr 8, 2015

+1

@cookrn

This comment has been minimized.

Show comment
Hide comment
@cookrn

cookrn Apr 8, 2015

Just encountered this error with:

Vagrant@1.7.2
VirtualBox@4.3.26r98988

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 fixed the issue.

cookrn commented Apr 8, 2015

Just encountered this error with:

Vagrant@1.7.2
VirtualBox@4.3.26r98988

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 fixed the issue.

@r4d1n r4d1n referenced this issue in EFForg/OpenWireless Apr 13, 2015

Closed

Vagrant DHCP conflict #295

@mohrt

This comment has been minimized.

Show comment
Hide comment

mohrt commented Apr 26, 2015

+1

@juanbrujo

This comment has been minimized.

Show comment
Hide comment
@juanbrujo

juanbrujo May 4, 2015

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 👍 👍 👍

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 👍 👍 👍

@bramswenson

This comment has been minimized.

Show comment
Hide comment
@bramswenson

bramswenson May 11, 2015

I'm surprised that this is still an issue. However, on the latest ubuntu vivid with virtualbox installed from the oracle repo, it is. The VBoxManage command above removing the interface settings worked.

I'm surprised that this is still an issue. However, on the latest ubuntu vivid with virtualbox installed from the oracle repo, it is. The VBoxManage command above removing the interface settings worked.

@thoughtarray

This comment has been minimized.

Show comment
Hide comment

+1

@Gschiavon Gschiavon referenced this issue in Stratio/sparta May 18, 2015

Closed

Failure vagrant up #152

@jbradley428

This comment has been minimized.

Show comment
Hide comment

+1

@f1337

This comment has been minimized.

Show comment
Hide comment
@f1337

f1337 May 27, 2015

+1 just happened to me using Vagrant on a Yosemite host (10.10.3) w/ an Ubuntu (14.04) guest. I have been using Vagrant for over a year with RHEL, CentOS, Oracle Linux and Ubuntu 13.x guest OSes, and no issues with any of those.

UPDATE: I used the box-cutter/ubuntu1404-desktop base box when I got the error. Have not tested if a custom Ubuntu 14.04 base box fixes the issue.

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 "worked" to unblock me.

f1337 commented May 27, 2015

+1 just happened to me using Vagrant on a Yosemite host (10.10.3) w/ an Ubuntu (14.04) guest. I have been using Vagrant for over a year with RHEL, CentOS, Oracle Linux and Ubuntu 13.x guest OSes, and no issues with any of those.

UPDATE: I used the box-cutter/ubuntu1404-desktop base box when I got the error. Have not tested if a custom Ubuntu 14.04 base box fixes the issue.

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 "worked" to unblock me.

@okor

This comment has been minimized.

Show comment
Hide comment
@okor

okor Jun 2, 2015

Vagrant noob here, definitely still an issue. VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 worked for me on OSx Yosemite

okor commented Jun 2, 2015

Vagrant noob here, definitely still an issue. VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0 worked for me on OSx Yosemite

@hanmd82

This comment has been minimized.

Show comment
Hide comment
@hanmd82

hanmd82 Jun 16, 2015

+1 to this solution: VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0

Based off a fresh install of Vagrant 1.7.2 and VirtualBox 4.3.28

hanmd82 commented Jun 16, 2015

+1 to this solution: VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0

Based off a fresh install of Vagrant 1.7.2 and VirtualBox 4.3.28

@mpermar

This comment has been minimized.

Show comment
Hide comment
@mpermar

mpermar Jun 19, 2015

+1 fresh vagrant fresh VB

mpermar commented Jun 19, 2015

+1 fresh vagrant fresh VB

@ibawolf

This comment has been minimized.

Show comment
Hide comment
@ibawolf

ibawolf Sep 16, 2015

+1
Thanks for this solution VBoxManage dhcpserver remove
fresh install of Vagrant 1.7.4 and VirtualBox 5.0.4 on Ubuntu 14.04.

ibawolf commented Sep 16, 2015

+1
Thanks for this solution VBoxManage dhcpserver remove
fresh install of Vagrant 1.7.4 and VirtualBox 5.0.4 on Ubuntu 14.04.

@mightydok

This comment has been minimized.

Show comment
Hide comment
@mightydok

mightydok Nov 2, 2015

Same error, fresh install of Vagrant 1.7.4 and VirtualBox 4.3

Same error, fresh install of Vagrant 1.7.4 and VirtualBox 4.3

@dmitry-php

This comment has been minimized.

Show comment
Hide comment
@dmitry-php

dmitry-php Dec 1, 2015

+1 for vbox 5.0.10 and vagrant 1.7.4 on Ubuntu 14.04

+1 for vbox 5.0.10 and vagrant 1.7.4 on Ubuntu 14.04

@abacaj

This comment has been minimized.

Show comment
Hide comment
@abacaj

abacaj Dec 8, 2015

+1 vagrant 1.7.4 - on windows I had to manually remove it from virtualbox under file -> Preferences -> Network -> Host-only Networks highlight the available network and click the minus sign to remove it.

abacaj commented Dec 8, 2015

+1 vagrant 1.7.4 - on windows I had to manually remove it from virtualbox under file -> Preferences -> Network -> Host-only Networks highlight the available network and click the minus sign to remove it.

@joemaller joemaller referenced this issue in ideasonpurpose/basic-wordpress-vagrant Jun 17, 2016

Closed

Windows support (mostly Ansible) #4

@shatil

This comment has been minimized.

Show comment
Hide comment
@shatil

shatil Oct 10, 2016

+1

Still a problem for me. Now that I know about it I won't lose another half hour setting up a VirtualMachine using https://github.com/chef/bento and http://berkshelf.com.

shatil commented Oct 10, 2016

+1

Still a problem for me. Now that I know about it I won't lose another half hour setting up a VirtualMachine using https://github.com/chef/bento and http://berkshelf.com.

@harmittaa

This comment has been minimized.

Show comment
Hide comment
@harmittaa

harmittaa Feb 22, 2017

Same error, Windows 10, Vagrant 1.9.1, VirtualBox 5.1.14. Fixed by deleting the Host-only Networks from the VirtualBox GUI. Just to note, I happened to have two of them for some reason.

Same error, Windows 10, Vagrant 1.9.1, VirtualBox 5.1.14. Fixed by deleting the Host-only Networks from the VirtualBox GUI. Just to note, I happened to have two of them for some reason.

@PortWhisperer

This comment has been minimized.

Show comment
Hide comment
@PortWhisperer

PortWhisperer Jun 11, 2017

Just got this error on Vagrant 1.9.1 vbox 5.1.22

PortWhisperer commented Jun 11, 2017

Just got this error on Vagrant 1.9.1 vbox 5.1.22

@ggeldenhuis

This comment has been minimized.

Show comment
Hide comment
@ggeldenhuis

ggeldenhuis Aug 11, 2017

This issue still appears to be very much broken unfortunately.

This issue still appears to be very much broken unfortunately.

@rnwolfe

This comment has been minimized.

Show comment
Hide comment
@rnwolfe

rnwolfe Jul 1, 2018

Issue definitely still exists. Vagrant 2.1.2 and VirtualBox 5.2.12.

Agree with people above that this should not be an out-of-the-box error that is likely to occur for any host-only network using DHCP (which is default for VirtualBox).

rnwolfe commented Jul 1, 2018

Issue definitely still exists. Vagrant 2.1.2 and VirtualBox 5.2.12.

Agree with people above that this should not be an out-of-the-box error that is likely to occur for any host-only network using DHCP (which is default for VirtualBox).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment