Forum Discussion
Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
Take a look at your Default Switch in Virtual Switch Manager, is it set to "External Network" with a defined controller or is it set to "Internal Network"?
I am bit confused about the last post about checking in the VSM for External/Internal network that is association. We are talking about Default Switch supplied by MS for NATing from Configuration version >7.0. MS easy way of old fashioned internet connection sharing. It is always EXTERNAL. I am sorry not able to make any sense. We are not taking about a custom Switch that is associated with any network type (External/Internal/Private)
Bala Sundaram is correct in that the Connection type cannot be changed for the Default Switch (all of the options are grayed-out), H3ALY , even with all VMs powered-off.
In any case, I have the same problem/question as Remon li . All I'm trying to do is assign a static IP address to a guest VM so that it doesn't change on me unexpectedly. I'd really like to satisfy the following requirements:
- Be able to specify the IP address to be used in the guest VM, e.g., 192.168.10.10.
- Be able to accomplish the above programatically, so that it can be done as part of an automated provisioning process (e.g., via Vagrant).
- Give Internet access to the guest VM via NAT (exactly as is done with the Default Switch). To be clear, I am amenable to using the Default Switch (instead of creating a new one), as long as its IP address does not change on me.
It sounds as though this is a two-part problem, and the first part is fixed in Build 17763.134, so at least the subnet will no longer change at random.
Bala Sundaram , when you say, "Erratic IP address assignment issue is fixed in Build 17763. 134", how many of the four octets are now "fixed"? The first three? In other words, do you now find that the address is predictably set to 192.168.XX, where XX never changes unexpectedly (nor the 192.168 part)?
Thanks for any clarification that you're able to provide!
Hello cbj4074,
I do not know why I said something very wrong. Sorry for misleading. I checked again, It appears the unpredictable IP address on default switch issue exists in build 17763.104 too. Darn thing assigns CLASS C (172.17.239.XXX) or CLASS D (192.168.75.XXX). It is still unmanegable. May be I was clouded by the workaround I had in place.
Basically I created a work around to take advantage of default switch as my two Physical NICs are teamed and fault tolerant.
- Created an Internal Switch
- Also have default switch that piles up on the bridged NIC (ICS)
- Have to VNIC's on the guest.
- Internal Switch based NIC is Static 192.168.5.XXX (255.255.255.0) for guest to guest communication.
- Default switch based NIC is Dynamic for Internet access
Regards,
Bala
No problem at all, Bala Sundaram . I really appreciate the info you've shared thus far, and thank you for clarifying your observations.
In Hyper-V on the mainline Enterprise branch (Build 1803 17134.345), I've only ever seen the Default Switch assign a Class B address in the 172.X.X.X range, and the last three octets seem variable.
Although, when I create a new External Switch (haven't tried the other types), it is assigned a Class C address in the 192.X.X.X range.
Are you sure that in your particular case the class B vs. class C assignment isn't based simply on the type of switch (Default, External, Internal, and Private)?
In any case, until there is some simple means by which to set these values statically, this behavior is going to be problematic for automation, period. :(
