hashicorp
Assigning IPv6 addresses with VirtualBox provider on Windows host fails
I tried to use an IPv6 address with Vagrant, but starting the box fails.
Vagrant version
Vagrant 2.1.2 VirtualBox 5.2.18
Host operating system
Windows 7 64-bit, Windows 10 64-bit
Guest operating system
Ubuntu Bionic 64-bit
Vagrantfile
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/bionic64"
config.vm.network "private_network", ip: "fd12:3456:789a:1::2"
end
Debug output
==> default: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "ipconfig", "VirtualBox Host-Only Ethernet Adapter #3", "--ipv6", "fd12:3456:789a:1::1", "--netmasklengthv6", "64"]
Stderr: VBoxManage.exe: error: IPv6 setting is not supported for this adapter
Expected behavior
The IPv6 address should be assigned to the Host-Only adapter in VirtualBox, and as well inside the host operating system, and the startup process should continue.
Actual behavior
The startup process fails
Steps to reproduce
- vagrant up.
VirtualBox seems to not be able to configure IPv6 addresses properly on Windows, the input boxes are greyed out in the configuration dialog (see https://imgur.com/htJOTqr). I can configure the address manually using Windows network adapter settings.
Seeing the same issues with the same environment. Is there any known workaround?
Hi there, Looks like this issue is blocked on VirtualBox not supporting IPv6. 💻 🌎
@soapy1 VirtualBox supports ipv6, as you can see here: https://www.virtualbox.org/manual/ch08.html The issue is on Vagrant side not being able to enable IPv6 on vbox instances. Suggestion: reopen this please :-)
Yes agree. The issue is not fixed, as Vbox clearly supports IPv6, and I am even using it on Windows, with manual configuration of the network adapter in windows network settings; but the settings in virtualbox are grayed-out, and the CLI API returns an error, so somehow there is something missing here...
Looking into this issue a bit further I've found some VirtualBox forum posts about similar issues. In particular https://forums.virtualbox.org/viewtopic.php?f=6&t=89219 and https://forums.virtualbox.org/viewtopic.php?f=6&t=83228. The Windows7/ipv6 network adapter support seems to be an issue with VirtualBox. However, while the behavior in Vagrant seems generally correct (other platforms successfully set the ipv6 of the network), this failure can probably be handled more gracefully by Vagrant.
2022 wow incredible job maintaining your product...…. (emoji through up and eating it again only to through it up again)
