You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WSL doesn't support IPv6 so a Vagrant VM provisioned in Hyper-V from WSL will be unreachable by an IPv6 address. It often happens that guest IPv6 addresses are reported instantly but IPv4 addresses will be dependant on DHCP and are reported at a later date. Vagrant will pick up the IPv6 address and then not be able to communicate (SSH) with the guest VM.
Describe the solution you'd like
This would allow a user to specify that only IPv4 guest addresses should be used and wait for one to be reported by the guest.
Describe alternatives you've considered
It would be possible to disable IPv6 in the guest VMs but this would provide a more generic solution
The text was updated successfully, but these errors were encountered:
WSL doesn't support IPv6 so a Vagrant VM provisioned in Hyper-V from WSL will be unreachable by an IPv6 address. It often happens that guest IPv6 addresses are reported instantly but IPv4 addresses will be dependant on DHCP and are reported at a later date. Vagrant will pick up the IPv6 address and then not be able to communicate (SSH) with the guest VM.
Describe the solution you'd like
This would allow a user to specify that only IPv4 guest addresses should be used and wait for one to be reported by the guest.
Describe alternatives you've considered
It would be possible to disable IPv6 in the guest VMs but this would provide a more generic solution
The text was updated successfully, but these errors were encountered: