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...
Sorry but I wasn't replying to you, i was replying to the OP, your problem might be different and i didn't consider your setup.
anyhow, I don't see how any of the things you mentioned can possibly take "hours" to setup. if you know the topology you're going to deploy beforehand then it can only takes few minutes to setup. btw you don't have to set anything in the host network adapters (virtual or not), everything happens in the guests.
if you want to set something that involves DHCP? like a Windows server DHCP? you still need external network adapter with static IP set inside the guest OS, as I said in my previous comment.
anyhow, I don't see how any of the things you mentioned can possibly take "hours" to setup. if you know the topology you're going to deploy beforehand then it can only takes few minutes to setup. btw you don't have to set anything in the host network adapters (virtual or not), everything happens in the guests.
if you want to set something that involves DHCP? like a Windows server DHCP? you still need external network adapter with static IP set inside the guest OS, as I said in my previous comment.
Setting up the virtual switches takes a few minutes.
I don't have a test environment handy at all times. I certainly don't have one now. So I need to get a software firewall, download the iso, create a new VM, install the firewall and configure it. This takes a bit longer than a few minutes. But that is absolutely beside the point.
The point is, the Default Switch is broken.
> if you want to set something that involves DHCP? like a Windows server DHCP? you still need external network adapter with static IP set inside the guest OS, as I said in my previous comment.
An external network adapter inside the guest OS? Either that configuration or that terminology doesn't make any sense.
I don't have a test environment handy at all times. I certainly don't have one now. So I need to get a software firewall, download the iso, create a new VM, install the firewall and configure it. This takes a bit longer than a few minutes. But that is absolutely beside the point.
The point is, the Default Switch is broken.
> if you want to set something that involves DHCP? like a Windows server DHCP? you still need external network adapter with static IP set inside the guest OS, as I said in my previous comment.
An external network adapter inside the guest OS? Either that configuration or that terminology doesn't make any sense.
look for example in your guest OS/firewall etc you need to set up these few main parameters.
whether you do it using GUI or powershell, terminal etc it's not gonna take so long..
also is there any indication saying that the default switch in Hyper-V must give you an static IP address regardless of host reboot?
I meant making an external network adapter and connecting it to the guest OS.
that config would make sense in a nested virtualization.
