Setting up a home VPN server with WireGuard

Re:Setting up a home VPN server with WireGuard by nemosaltat on Friday November 01, 2019 @07:46PM (#21424877)

That’s the real question.

I wrote a little script that creates the configuration files, and shows a QR code in the terminal to easily add new clients.

The problem I ran into is dynamic IP allocation, without extra logging, or storing the client config files after they’ve been distributed. If I want to avoid assigning a used IP, I need to know what I’ve already given out.

I mocked up a few things then decided the perfect was becoming the enemy of the good. Since I’ll only ever have a few peers, I ultimately just decided randomize the 4th octet, each time I create a new client config. Obviously, this opens me up to a potential conflict in the future (prayers to St. YAGNI for benevolence).

I suppose I could/should be pre-generating all the configs, handing one out at random, then deleting it.

[ Parent | on HN ]

Re:Setting up a home VPN server with WireGuard by judge2020 on Saturday November 02, 2019 @12:55AM (#21425964)

This script[0] gets that part right by having a `lastip` file containing the latest assigned IP, so the script counts up for new clients. You can add a line for qrencode to the end to get the QR[1].

0: https://gist.github.com/Belphemur/b014a11f9ae6c20203276f214e...

1: https://gist.github.com/judge2020/e9631be086ea105005614c70a8...

[ Parent | on HN ]

Re:Setting up a home VPN server with WireGuard by nemosaltat on Saturday November 02, 2019 @02:47AM (#21426251)

Thank you!! This is very close to what I’m doing.

[ Parent | on HN ]