July 27, 20223 yr Goals: connect to my home network via wireguard have access to all shares / webgui's of devices on my home network do NOT use the internet connection of my home network (my remote device uses its own local internet connection) be able to ssh into my VMs Currently I run wireguard-easy on a RPI, and it achieves all the above goals. But I thought I could use the wireguard implementation in Unraid instead and replace the RPI that way. So to achieve the above goals I selected "Peer type of access: remote access to LAN" in the Unraid Wireguard config. That way I achieved goals 1 ,2, and 3. HOWEVER I cannot ssh into my VMs through that tunnel, the connection cant be established. I also run into the same issue when I use the "Wireguard-easy" docker in unraid. So I guess there is some networking issue inside unraid preventing me from using ssh through the tunnel?
July 29, 20223 yr Author Tried a couple more things, but I always run into the same issue that SSH does not work through the wireguard tunnel.
July 29, 20223 yr Community Expert Are you trying to ssh to the name of the server on your local LAN, or using the ip address assigned to the tunnel? Reason I am asking is that if doing the former and both client and server are on the same ip subnet (i.e. 192.168.0.?) then you may have a name resolution issue. I deliberately avoid using a subnet of the form 192.168.0.X or 192.168.1.X for my local LAN as a remote client is often on a subnet with that address range. Perhaps a screenshot of the WireGuard settings on Unraid for the tunnel you are using and the command you are trying to use to ssh would help clarify?
July 29, 20223 yr Author thx for your reply! Unraid: 192.168.1.5 (my main network - gateway 192.168.1.1) 192.168.2.5 (this interface is used so that my brother also has access to the SMB shares from his network, that is the only thing this interface is used for) Ubuntu VM running on Unraid: (br0 - static IP) 192.168.1.26 Windows VM running on Unraid: (br0 - static IP) 192.168.1.10 docker image plex: (host) 192.168.1.5 docker image n8n: (br0 - static IP) 192.168.1.21 docker image code-server: (br-0 static IP) 192.168.1.9 on my Router: port 51820 (UDP) forwarded to 192.168.1.5 Network I am connecting from: 192.168.123.0/24 ------------------- The following happens with "remote tunneled access" as well as "remote access to LAN" ------------------- Through the Unraid Wireguard tunnel I can: access the WebGUI of Unraid 192.168.1.5 access the WebGUI of Plex on 192.168.1.5:32400 access the WebGUI of docker image code-server on 192.168.1.9:8443 access the SMB shares on unraid 192.168.1.5 Through the Wireguard tunnel I can not: ping nor access the WebGUI of any other device on my network (i.e. 192.168.1.1 - router) access the WebGUI of docker image n8n on IP 192.168.1.21:5678 ping nor ssh (putty) into the Ubuntu VM ping nor remote desktop into the Windows VM I have the exact same issues when I use the "wireguard-easy" docker on unraid - however using wireguard-easy on my RPI works just great. blow are my routing tables. I have no idea where these came from or what they are used for: br-b14fa2d6b9b6 br-b14fa2d6b9b6 shim-br0 virbr0 Edited July 29, 20223 yr by cholzer
August 29, 20223 yr Author I gave this another whirl - same outcome. I can only partially access devices/services on my network. No one else has this problem? https://forums.unraid.net/topic/126490-wireguard-unable-to-ssh-into-vm-running-on-unraid/?do=findComment&comment=1153218
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.