- A different device from your home server?
- On the home server as the services but directly on the host?
- On the home server as the services but inside some VM or container?
Do you configure it manually or do you use some helper/interface like WGEasy?
I have been personally using wgeasy but recently started locking down and hardening my containers and this node app running as root is kinda…
You must log in or register to comment.
One instance runs on the router (Unifi USG) and the other on a Pi3 (as a backup) using PiVPN.
Usually, if I need to set it up, I’ll use PiVPN and either a Pi or Debian/Ubuntu host.
If your router is down how do you get to your pi backup?
A virtual machine on my LAN that runs Fedora Server
On my (OpenWrt) router, configured using the OpenWrt interface
I run one on my firewall, but it’s IPv6 only because of CGNAT. The other one is running on a VPS in case I need IPv4 access. I just configured them manually.
One end is a local VPS with insanely good peering pretty much round the damn world, other end is my opnsense router. I actually pass a block of ipv6 through the vpn and my router hands it out to devices which is a nice little bonus
Who is your VPS provider, if you don’t mind telling?
https://spartanhost.org/ owner is super chill will make custom spec deployments and they actually have a really nice management panels with nice easy custom iso support
Always in the router if it supports it. If it does not support wireguard I would rather (if you are able and allowed to) replace the router instead of using something else.
Can you elaborate on why?
For me a similar tasks should be handled by the same device. Network routing and VPN are similar things for me, therefor they are handled by the router.
It also handles VPN connections to other remote locations. So again same things in the same device.
Another benefit (which you can also have on the Server with some additional effort): the router boots up without interaction after a power outage. The Server does not. Them I can connect and unlock (LUKS password) the servers.
Maybe easier to setup because routers that support vpns come with nice-ish web uis.
That said, if you have a server (pc, pi, etc), setting up wireguard with wg-easy is mostly painless (comes with a nice web ui), so there is no reason to replace your router in this case!
Instead of replacing a router, I’d prefer buying a pi anyways.
Unless you want to route all outbound traffic through a vpn with zero config on devices, I can’t see why you’d replace a router.
Final note: most people prefer hosting a vpn on a server, even if their router supports it as far as I’m aware at least (edit: this might be erong judging from the rest of the comments saying they use their router).
I have a Raspberry Pi that runs pihole and Wireguard exclusively. My home server is a Kubernetes cluster running on an old desktop PC and 2 Intel NUCs.
The reason for the separate Pi was essentially because I only had the desktop PC initially, and for a while I had a faulty CPU, making the desktop PC crash or become unresponsive, so it helped a lot having DNS and VPN access separated from the instability.
Runs in an extra locked-down container on one of my servers.
Home 1’s Routers, Home 2’s Router, public IPv4/v6 VPS. All as the native arch package.
The routers are running Arch? What hardware are they?
I’m running pfSense as edge firewalls with a Fritzbox router as a bridge - no issues there, but would be interesting to replace that part too, if possible.
On my router, my FritzBox came with WG support built in.
Mine runs on my router which is running openwrt
What are you wanting to use Wireguard for?
OPNsense
This is the way.
I run a wireguard container on my old desktop server and wgeasy in a pi2 as backup.
That’s the fun part. I’m creating a mesh where multiple things are server and client.
K8s, mikrotik, home assistant, frigate, pangolin, etc.
I don’t get the mesh if everything is behind your router or firewall what is the point.
