Open remilapeyre opened 1 year ago
Running into the same issue, it sets the private IP address on a new interface eth1
leaving eth0
.
For any passers-by:
As of Vagrant 2.4.3, this is still an issue but it's specific to Fedora 36 and newer boxes. Upstream issue hashicorp/vagrant#12762 covers the issue in detail, but TL;DR Fedora no longer supports how Vagrant tries to configure static interface via ifcfg-rh files, instead it should be using NetworkManager keyfiles. Appropriate workaround pending a fix in the upstream would be to manually configure the additional interface it creates with the desired address with nmcli
.
You probably don't want to fiddle with the eth0
interface since that's attached to the shared network and is what Vagrant/Parallels is using to provide SSH access and general WAN access.
Configuring static IP addresses for the
private_network
using the configuration given at https://parallels.github.io/vagrant-parallels/docs/networking/private_network.html does not work.Vagrant version:
Vagrant parallels plugin version:
Parallels Desktop version:
Vagrantfile:
Running
vagrant up
:But the IP address is wrong:
The IP address
10.37.132.10
differs from10.37.130.6
. I think the private network is still using DHCP.