It’s my outside device it allows things into my network might as well terminate the VPN there. I mean if my router is down I’m not getting to the VPN endpoint inside my network.
Comment on Where are you running your wireguard endpoint?
piyuv@lemmy.world 2 months agoCan you elaborate on why?
Auli@lemmy.ca 2 months ago
sakphul@discuss.tchncs.de 2 months ago
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.
dogs0n@sh.itjust.works 2 months ago
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.