This may not be possible and if so that’s ok. I just thought I would ask since everyone here seems smart and helpful.
I have a very odd setup I know. But, it is what I am needing.
I have a cloud based FOG server running Debian running version 1.5.9 on Debian 9. I have another cloud based VPN server using Pritunl on Ubuntu 18.04. The current setup has a local FOG storage node and the network is connected to the VPN server. The FOG server has the VPN client installed and connected to the VPN server.
Both servers have public IP, but both are also connected together via a second interface on a private network. I have blocked all traffic on the public IP of the FOG server and am using the private IP to connect to it.
My hope was to be able to use this setup without installing the VPN client on the FOG server. I added static routes to both servers and can login to the webui of the FOG server, but PXE booting fails. Now, bear in mind, I am not booting to the FOG server directly. The computers are booting to the local storage node.
So, I am attempting to PXE boot from a device in a 192.168 network via the local storage server. The main FOG server is connected via VPN to VPN server and then via second network adapter on VPN server to FOG server. Is this possible or should I just keep the VPN client on the FOG server?
Ok, I don’t what happened, but it’s working now.
@eseelke Definitely good if you can post a “network map” of the setup!
I added static routes to both servers and can login to the webui of the FOG server, but PXE booting fails.
Which device is serving DHCP in those networks? Just asking because DHCP broadcasts might not be forwarded between your sites. Please add this part to your network map and/or explain more in detail.
You are going to have to draw a picture with IP addresses of how this infrastructure is connected. Use fake public addresses, but real internal addresses.
I can tell that that the way FOG with a master, storage nodes, and FOG clients are designed… they are expected (storage node and fog clients) to be able to reach the master node 100% of the time to remain operational. So If you have a fully routeable site to site VPN then everything will work as designed. If you have intermittent connection then things won’t work quite as well. The storage node needs to be able to contact the master node because the database only exists on the master node. So this link needs to be up 100% of the time. PXE booting is local then jumps to the master node to load boot.php.