Sep 24 2018 10:19 AM
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 51 thru 180.
Although this is working on DHCP based IP assignment on guests, It is causing issues on static IP as it keeps changing after every boot
Regards,
Bala
Oct 04 2019 01:15 PM
Oct 04 2019 01:31 PM
Is the default switch's crazy behavior of re-creating its vEthernet adapter on every reboot fixed in 1909 (or later)?
Oct 04 2019 01:54 PM - edited Oct 04 2019 01:57 PM
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.
Oct 04 2019 01:59 PM - edited Oct 04 2019 02:02 PM
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.
Oct 04 2019 02:12 PM
Oct 04 2019 02:17 PM
Oct 04 2019 02:17 PM
@HotCakeX
Please stop speaking for MS, it is stated nowhere that
Microsoft never designed the default switch for long term usage or advanced usage like on a virtual server (VM)
The documentation said nothing about it. I've spent hours just to figure out that it's simply broken.
Any serious server admin knows Not to use the default switch for any server.
It's not true again. You could use any default switch from every other software vendor except MS no matter are you serious or not.
Why don't you just understand that it's not a feature, it's a bug, nobody doing this stuff except MS. Nobody period.
Oct 04 2019 02:20 PM
“Hyper-V has a Default Switch for easy networking.” Having just tried it out myself, I can affirm that this Default Switch makes Hyper-V networking dead simple.
if you don't believe me, I can give you thousands of guides and YouTube videos to show everyone setting up a virtual servers uses External/Internal/Private network adapters, Not the default one.
Oct 04 2019 02:24 PM
@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.
Oct 04 2019 02:26 PM
Previously you had to mess around using virtual switch manager to create a connection to network. Now you just select default switch if you like.
This option is essential for quick creating a new hyper-v session.
It is only used in existing sessions if you explicitly add it to a particular VM session.
Deleting it will not provide any additional security, or prevent other users creating a virtual switch.
Deleting things without understanding their functionality is surefire way to break things!
the 2nd comment
Oct 04 2019 02:26 PM
Oct 04 2019 02:32 PM
you said stop speaking for MS (Microsoft),
ok sure, of course, why not.
here is what Microsoft says, Not me:
Hyper-V has a Default Switch for easy networking
Does a professional user who wants to setup a Virtual Server for serious work use something that is made for easy network? if he/she does then he/she is No longer called professional, but amateur. and for amateurs, Microsoft created the Default switch.
Oct 04 2019 02:42 PM
@HotCakeX It's not a documentation. It's just a tech blogs with workarounds for an extremely buggy software.
The default switch is not usable in almost every scenario except 2 minutes demo session and I bet it could fail even in this case.
It's like a car moving randomly in every direction possible no matter the actual driver wants to drive.
And the thing that you have to add more objects to make it works doesn't make it a feature, it's still a bug. And even more, it's completely undeletable.
Please try Linux or simply VirtualBox so you could compare a MS mess and working solution from other vendors. Few hours for MS to make it work and few clicks on VB or few lines of configuration on Linux really makes a difference and MS is not a winner here.
Oct 04 2019 02:46 PM
Oct 04 2019 03:23 PM
Oct 04 2019 11:24 PM
Oct 04 2019 11:55 PM
Oct 04 2019 11:57 PM
Oct 05 2019 12:00 AM
@HotCakeX How is it "advanced networking" if I just wanna attach a computer to a network, but need it to be designated a private network so the firewall just works.
At this point you're just defending your own point of view. You can't make a statement anymore where you don't feel personally attacked. It's become very tedious. Just let go.
Oct 05 2019 12:05 AM - edited Oct 05 2019 01:42 AM
Nope,
attach your VM to the virtual network adapter, no problem, set the virtual network adapter Inside the VM to private, no problem, set the default network location for all known and unknown networks in Group Policy to private, no problem.
instead of talking about imaginary things about me, please stay on topic and Don't be rude.
so again,
1. use group policy, the local one, not the group policy management, to change network locations.
2. if you change the virtual network adapter INSIDE the VM, it WON'T change after reboot of the host.
computers on a network using DHCP do NOT change their network locations when the DHCP server gives them a different IP address.