Remote Access Terminal

Introduction

There are two Windows 11 pro desktop Virtual Machines setup hostnames Walnut and Wahoo on the Terminals network, There is also a Linux Ubuntu desktop VM, Lychee, on the same network. These three will be used by RDP over the VPN. The two Win 11 VMs RDP have been tested initially against each other and later from the desktop grape(192.168.0.10) outside Pfsense as straight RDP. I have set them to use the basic security but I am less than confident that the simple basic security would be good enough for use on the WWW so I will be setting up the VPN on Vanilla. Update Lychee has been moved to the Production Network as it will be playing a more active role in the AI development and it will be lending more of it's services to support the webservers on Production.

Remote Access (RDP) to Windows 11 Desktops

There are two Windows 11 desktops setup on the terminals network Walnut and Wahoo. Both can be accessed directly by RDP from the LAN at the WAN address of Pfsense using the ports xxxx0 for walnut and xxxx1 for wahoo (as a reminder this would be the lower number). If wireguard VPN is active the hostname or local IP address needs to be used as WG allows win 11 to use the ctns1 DNS server eg walnut or wahoo, the .net could also be used but is untested with WG active. However, if OpenVPN is active the local DNS will not be used by the win 11 desktops by default so the full local DNS name has to be used (.local appears to have special meaning to Windows) ie walnut.seaoffate.local and wahoo.seaoffate.local. NB Tt should be noted that the RDP port has not been changed on the Virtual Machines only in the port forward.

Remote Access(NoMachine) to Lychee

RDP would work to a linux host like Lychee but it would not work particularly well so No Machine has been installed. By default NoMachine works on port 4000 and as there is only one Virtual Machine using it there seemed little point in setting up extra firewall rules for it so there is a basic fwd rule on Pfsense that works within the LAN and Grape has a Nomachine connection profile for use through Pfsense and another connection profile that works with Wireguard VPN active. It has been easier to access Lychee through the normal Proxmox/Spice veiwer while in front of the desktop but the NoMachine would be sort of ok at a pinch.

Update for Walnut (GPU and Jellyfin)

The PCIE Passthrough for the AMD Ryzen GPU didn't work as Pear would not allow it to be released so it never got completely passed to any Virtual Machine, this was a failure caused by AMD and Proxmox combined, AMD because they never released any drivers that would work reliably and Proxmox because it will not allow suspect packages to be installed and break the Proxmox host OS. Anyway it was a failed project and only an outside chance of working from the start and far better that the GPU passthrough fails than the Proxmox host fails.

The AMD GPU will be sold as it has no use anymore. As a replacement and to further the experiment into PCIE passthrough a low end Nvidia GPU was obtained in the form of a 5060 GPU from MSI. The Passthrough worked with some effort but worked none the less.

Jellfin

So with a working GPU to Walnut it was a good time to setup Jellyfin on it. It must be said that the Jellyfin install on the win11 VM went easily but unfortunately no notes were taken, on the positive side though if it ever has to be done again on a Win11 machine it will not need a lot of effort