It quickly became apparent that I would like to add more than one peer to the configuration and stopping and restarting services seemed a bit of an overkill to solve the problem.
Obviously Wireguard is still pretty much a manual solution, lets face it, it is supposed to be. If it was going to be a mammoth, then we might as well stick with the more standard solutions out there.
Anyway, to add a Peer and for it to be available immediately, then this is what you have to do.
Edit your config, usually /etc/wireguard/wg0.conf and add your new Peer to the configuration.
[Peer]PublicKey = 09m4KVG6uJ8tz7bW8vVsLiWTcnTePx8cafnucxLQdlM=AllowedIPs = 10.0.0.X/32
Now we just need to force the reload of the config.
> wg syncconf wg0 <(wg-quick strip wg0)
And now your server has a new peer that can connect to it.
Now to create a Windows 11 Wireguard Peer, you have two choices, you can either add one manually (which I did, keeping with the theme and all that). See the Screenshot (redacted obviously, but you get the idea).

A config file is pretty much the same thing, a simple text file with the same information in.
[Interface] PrivateKey = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXS3I=Address = 10.0.0.X/32DNS = 8.8.8.8 #extras can be added but must be comma separated[Peer]PublicKey = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXJDI=AllowedIPs = 0.0.0.0/0, ::/0Endpoint = A.B.C.D:51820
Then just click Add Tunnel and point it at the text file to import.
Anyway, signing off now, hope that helps.
Leave a Reply