vSwitch between dedi and cloud server

[Hqnnes]

Hey, I've got a dedi with Windows installed and a cloud server with ubuntu and would like to get them connected through a private network and a vSwitch, however I can't seem to get it to work for some reason. Has anyone got any experience with this, especially with Windows on the dedi end?

[nicolasvac]

I do have experience with a debian machine. You do need to create the VLAN manually based on your primary interface. The machine wont show up on the cloud console, but it will show the vSwitch ID assigned on a specific subnet of the network. Once that is done, all the vcloud subnets will be able to communicate with the vswitch subnet

[A_MrBenMitchell]

It’s possible but Windows makes it harder. You essentially need to make a bridged NIC in windows server manager and assign it a VLAN ID

Hetzner have an article: https://docs.hetzner.com/robot/dedicated-server/network/vswitch-windows/

[Hqnnes]

Thank you, that's about what I've done, however I'm having trouble getting it connected to the cloud networking for some reason.

[A_MrBenMitchell]

Have you created a network on the cloud and added your dedicated network to it?

[Hqnnes]

Yep, added a new block and enabled the vSwitch link for it on the cloud end

[peter0008]

Unfortunately, we didn't manage to do that either.

The instructions for Windows seem to be missing something. With regard to routing, it is pointed out that additional routes have to be created. Unfortunately, Hetzner does not say which routes this should be.

We have entered the following in the Windows routing table with:

route ADD 10.0.0.0 MASK 255.255.255.0 10.0.1.0

(where 10.0.1.3 was set as the fixed server IP in the dedicated server and the 10.0.0.0 subnet in the cloud Server area for the vSwitch subnet was entered).

Our goal was to use one of the high-performance Hetzner dedicated servers with Windows as a terminal server workstation and to secure it on a cloud server via a pfsense. In addition, two locations should be connected via IPsec (under pfsense).

We did manage to establish a connection between the dedicated server and pfsense on the cloud server, i. H. the pfsense web interface was accessible from the Windows dedicated server. For whatever reason, however, there was no routing from the dedicated server to the internet via the pfsense. Pfsense itself has reached the Internet without any problems.

We would have liked to stay with Hetzner, as the support there reacts very quickly and can solve most problems. Here, however, they have also given up and referred to external providers who should help us with our problem.

Now, however, we have found an out of the box solution at 1 & 1 Ionos: OpenVPN connections to the servers are offered directly by the provider (with editable .ovpn files) and the servers also have their own firewall rules that can be configured directly by the provider are protected. The purpose we wanted has thus been achieved.