kf3333

Thank you for your response. I am now quite sure it has something to do with parsec itself, because I can route bidirectional through the LANs. I will try to investigate a little more during the weekend. I've now just seen that I forget to mention in the OP that I am able to connect to the machine from wg0. So routing works between br0 <--> wg0 as expected (remote access to LAN)

nice, thank you. I know this command and just didn't think of it....thanks for reminding me! And yes, it's only because of some very specific envs that I couldn't remember on how I set them. Thanks again!

Dear all, Yesterday, I had a completly corrupted boot drive without the chance to rescue or repair any files on it. So, the contents - especially the config and docker templates are gone. The server is running fine after installing unraid on a new stick manually etc. Dockers and VMs are running without an issue. However, since the templates of the dockers are gone I am not able to edit / update them. I know that I could just recreate the dockers to get a new template but since my docker setups where rather complex I would like to double check all variables that I have set eralier. So my question is: Is there some place where the docker commands to run up the dockers are stored or can I somehow dig up the commands executed when the docker is started manually? That would be really helpful for reconfiguration..and setting up a proper backup afterward.. cheers

Hi guys, I am trying to do something that might be not very popular. I am running a Windows VM that is isolated from any WAN-Out / WAN-out, so no internet connection at all. However, this VM runs a parsec host (something like a VNC/Remote Desktop, but much faster). I only want clients to connect to the machine using parsec that are inside the LAN - either tunneled through wireguard or physically - and this works for physically connected clients. Specifically, Working scenario 1: Windows VM runs on br01 (10.10.20.0/24) Client runs on 10.10.20.0/24 Working scenario 2: Windows VM runs on 10.10.20.0/24 Client runs on 192.168.1.0/24 Not working: Windows VM runs on 10.10.20.0/24 Client runs on 10.153.1.3 (wg0 from wireguard) So, it seems that parsec can't find the host even though the network is routed correctly (the wireguard client has access to the 10.10.20.0/24 lan). Does anyone have a solution for this type of problem?