Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!
Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.
Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!
First of all: running Wireguard on your Mac, as a "server", would require your Mac to be accessible from the Internet - not something I'd want to do.
A common way of doing this would be by setting up port forwarding in your modem/router. Forward port 51820 UDP to your Mac's IP address (make sure your Mac gets a fixed IP address - either by reserving an IP address in your router/modem linked to the MAC address of your Mac, or by giving your Mac a static IP address).
Coming back to the config file:
Your server should be able to show or generate a config file.
Something like this:
[Interface] Address = [ip address client - your Firstick] PrivateKey = [Client's private key] [Peer] PublicKey = [Server's public key] Endpoint = [Server Addr:Server Port - your Mac's PUBLIC IP] AllowedIPs = [ip address range the client can access]
Wireguard, for me as well, can be rather daunting at times since both server and client are the same with Wireguard - called "peers" 😉
For the IP range you'd typically see something like "192.168.1.x/32" in CIDR notatie.
This Calculator helps you play with the values to see what they mean.
So 192.168.1.24/32 means that the client can only 192.168.1.24.
The "32" indicates the "range".
Did see these posts that may be helpful:
- Reddit Wireguard on Mac
- Wireguard for Dummies (I consider myself a dummy on this topic as well)
