Forum Discussion
Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
Nope,
if you need to use the default switch you can create your own persistent route from the powershell.
what is actually crazy is that when someone decides to setup servers and then use the default switch for that server, after that complain why the default switch gets a new IP address after each reboot!!!
Microsoft never designed the default switch for long term usage or advanced usage like on a virtual server (VM). the default switch, as the name applies, is just a set up and forget virtual network adapter, made by Default, for Anyone without Any networking experience, to setup a quick VM using the quick VM creation in Hyper-V.
Any serious server admin knows Not to use the default switch for any server.
I don't know why some people fail to understand this.
Default switch changes IP address after every reboot because it is Smart, it evaluates the network environment and chooses a free and routable temporary IP address for the user to use it on their VM.
a user that doesn't need or doesn't know how to go through more advanced setups like External virtual network adapter.
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.
- True, but I have to re-disable it after every boot.
mlmathews wrote:
Yeah, I'd be fine if I could just remove the default. It's a real headache when I need to connect my work laptop to the corporate network. I can't get on the corporate WLAN if there are any other unauthenticated adapter connections...and the vEthernet adapter is not authenticated. I know a registry hack to get around this issue...but the dang vEthernet adapter gets recreated on every boot and I have to re-apply the hack. I could write a script to do it, but its madness that I can't just get rid of the thing.You can disable it from the network settings or device manager.
- Yeah, I'd be fine if I could just remove the default. It's a real headache when I need to connect my work laptop to the corporate network. I can't get on the corporate WLAN if there are any other unauthenticated adapter connections...and the vEthernet adapter is not authenticated. I know a registry hack to get around this issue...but the dang vEthernet adapter gets recreated on every boot and I have to re-apply the hack. I could write a script to do it, but its madness that I can't just get rid of the thing.
- 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....
