Forum Discussion
Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
Can one confirm IP address range changed to 192.168.X.Y Subnet 255.255.255.240 from 172.X.X.X Also changes the subnet randomly on every Hyper-V services startup. 192.168.X.Y . X can change from 5...
So Microsoft provide a feature that they don't want you to use ? Why don't they just delete it or give option to delete it ?
It's not smart way to change IP after each reboot for routing, not at all , it is just a stupid bug may never be fixed.
Who said they don't want you to use the default switch?
read my post again, it's for people who don't know much about networking so Hyper-V creates a pre-made virtual network adapter called default switch for them to help get internet connection on their VM.
people might be behind multiple NATs, different subnets and have multiple NICs, default switch is Smart so it identifies the difficulties of the network and creates a non-persistent route for the moment to give that user an Internet connection at any cost. the reason it chooses a non-persistent route is to Reevaluate the network environment for any changes. the random addresses gives it flexibility.
if the default switch is bugging you then you're doing it Wrong.
you're probably relying on an static IP address and instead of doing the proper and correct work of creating an external network adapter, you just used the default switch.
that's Not the right way.
this is something that I use for work and personal everyday and I've worked with lots of other professionals either IRL or collaborated over the Internet, Learned from them and experienced myself, nobody, I say again, Nobody chooses the default switch for a Virtual Server that needs a static IP address.
you can't do something wrong, get a bad result and then say it's a bug....
read my post again, it's for people who don't know much about networking so Hyper-V creates a pre-made virtual network adapter called default switch for them to help get internet connection on their VM.
people might be behind multiple NATs, different subnets and have multiple NICs, default switch is Smart so it identifies the difficulties of the network and creates a non-persistent route for the moment to give that user an Internet connection at any cost. the reason it chooses a non-persistent route is to Reevaluate the network environment for any changes. the random addresses gives it flexibility.
if the default switch is bugging you then you're doing it Wrong.
you're probably relying on an static IP address and instead of doing the proper and correct work of creating an external network adapter, you just used the default switch.
that's Not the right way.
this is something that I use for work and personal everyday and I've worked with lots of other professionals either IRL or collaborated over the Internet, Learned from them and experienced myself, nobody, I say again, Nobody chooses the default switch for a Virtual Server that needs a static IP address.
you can't do something wrong, get a bad result and then say it's a bug....