Greetings. I'm using PiVPN right now. Works great for me, connecting via Wireguard clients and able to use both WAN and LAN. There is one client that I would like to allow to connect to my VPN and be able to use the WAN only, and this is where I'm running into some trouble finding a solution. I took a few swings at the problem by trying to narrow down the Allowed IPs in the wg config file but that not only didn't work but in hindsight it seems like an ineffective way to attack the problem to begin with.
Is there a way to set this up, either via something in the client config file or something else on the hosting side? I don't want to disallow all Wireguard clients from accessing the LAN+WAN. It's just one particular client that I want to allow access to only the WAN.
I have 3 DDNS hostnames from 3 separate providers. I have had issues with at least 2 of them where the updater got messed up, or the service required a login to keep it from going "dormant". This was slow for me to catch...
Can I add multiple "endpoints" to my config file to get some redundancy, or will this just cause problems?
After using WireGuard to VPN into my LAN, I can use RDP or SSH+VNC to control machines on my LAN. I am able to reach them via IP or by host.domain.private for remote control, but I cannot browse to \\host.domain.private\share for the same machine to access its network share.
So I have two sites: my home network and my cloud VPSs. I have setup a FreeIPA
domain that I would like to use for all my machines, local and remote. While I
wait for Linode/Akamai to add their new VPC feature, I want to create Wireguard
tunnels from each VPS to my home network with my UDMP as the r...