New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Yes, check out the Virtual Switch Manager in Hyper-V Manager.
I believe you should be creating and associating the Virtual Switch's external network with the available network adapter(s) accordingly.
Once the Virtual Switch is created, you can assign that to your VM as its Network Adapter, via the VM's Settings in Hyper-V.
This is a good reference document
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/get-started/create-a-virtual-switch-for-hyper-v-virtual-machines#create-a-virtual-switch-by-using-hyper-v-manager
Ive always used "external" as a option on a virtual switch. Should it be set to internal to generate local ips for NAT?
I believe this will make it try to get a ip from hetzners switches, and it wont get that ofcourse.
As far as i understand it, i need to have a "router" on the actual server, to give out local ips.
Well yeah, that might not be what you intend to do, sorry, I only run Hyper-V locally on my notebook for work and unfortunately I don’t have any external Windows machines to test and guide you.
I did a quick read on this and stumbled upon the link below - maybe it’ll help.
https://4sysops.com/archives/native-nat-in-windows-10-hyper-v-using-a-nat-virtual-switch/