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
I'm currently experimenting with Windows Server 2012 R2 automation and attempted to configure winrm with SSL enabled as my provisioner. As pointed out by the issue 9187 I'm forced to explicitly define a host parameter to circumvent an error.
My goal is to set a static IP for the guest VM to 192.168.111.10, but the combination of config.winrm.host = "192.168.111.10" and windows_server.vm.network "public_network", ip: "192.168.111.10", bridge: ENV['VAGRANT_BRIDGE'] doesn't correctly assign a static IP to my guest when running vagrant up. The environment variable VAGRANT_BRIDGE is set to wlp2s0 (since vagrant doesn't seem to recognize my virtual adapter wlp2s0:0 before vagrant up is called).
Vagrant should've set the static IP (192.168.111.10) on the Windows Server guest.
Actual behavior
Vagrant picked an IP from the wrong subnet, instead of the correct subnet 192.168.111.1/24 it requested an arbitrary IP (most likely via DHCP) from 192.168.0.1/24.
I'm unsure if this is even an issue with vagrant on it's own or if my network configuration is just terrible.
Can somebody confirm this is a common issue?
I have been having vaguely similar problems with Vagrant since 2.1.0 with CentOS guest not paying attention to ip settings (in fact I keep getting duplicate IPs assigned with External Switches) But you are doing enough differently than me that our issues could be entirely separate. Sorry.
What am I trying to do here...?
I'm currently experimenting with Windows Server 2012 R2 automation and attempted to configure
winrm
withSSL
enabled as my provisioner. As pointed out by the issue 9187 I'm forced to explicitly define a host parameter to circumvent an error.Thus I changed my network adapters:
My goal is to set a static IP for the guest VM to
192.168.111.10
, but the combination ofconfig.winrm.host = "192.168.111.10"
andwindows_server.vm.network "public_network", ip: "192.168.111.10", bridge: ENV['VAGRANT_BRIDGE']
doesn't correctly assign a static IP to my guest when runningvagrant up
. The environment variableVAGRANT_BRIDGE
is set towlp2s0
(since vagrant doesn't seem to recognize my virtual adapterwlp2s0:0
before vagrant up is called).Vagrant version
Vagrant version:
2.1.1
Host operating system
Fedora 27
Guest operating system
Windows Server 2012 R2 (x64)
Vagrantfile
Debug output
See the gist
Expected behavior
Vagrant should've set the static IP (
192.168.111.10
) on the Windows Server guest.Actual behavior
Vagrant picked an IP from the wrong subnet, instead of the correct subnet
192.168.111.1/24
it requested an arbitrary IP (most likely via DHCP) from192.168.0.1/24
.References
The text was updated successfully, but these errors were encountered: