How to configure Active Directory server with bridged external IP?

[robb (Rob Bosch)]

I could think of several tricks to connect the different subnets.
Can you clarify a bit more how you configured your NethServer and AD container?

Do I understand correctly that your NethServer is installed on a VPS (cloud server) with an external IP adres that is bridged with a internal private IP address. This is your RED interface. Now you need a GREEN interface to make it possible to create a linux container to host Samba4 AD.
You could create a dummy interface that you can give an IP address in a subnet of your choice. This could be the same subnet as your local subnet at home.
There is a howto for that dummy interface. I did this too for my NethServer instance as VPS where I wanted to run Samba4 AD accountprovider.

Create a dummy interface when you only have 1 NIC available

This is a compilation of 2 discussions on these forums: Dummy Interface (virtual NIC) Virtual network interface for virtual machines Thanks to @asl and @jstammi for doing great work on this topic! add a file for your dummy interface in /etc/sysconfig/network-scripts/ let’s call it ifcfg-dummy0 [image] the kernel module dummy (which is need for dummy devices) is not loaded per default, so we need to add this during server start. Ceate a file dummy.conf inside /etc/modules-load.d. This f…

When you have created the dummy, you can create a site-to-site VPN from your home router to your cloud NethServer instance.
@support_team you think this is possible and are there any special configs in this scenario to take care of?