![]() Once connected, you can head over to to make sure your DNS is not “leaking”. Replace YOUR_CLIENT_PUBLIC_KEY with your generated public key and YOUR_CLIENT_VPN_IP with the IP address you should be authorized to use ( 10.0.0.2 in my example).įor more information on why you need to run this command, check out my “important concepts” post on how this all works. ON YOUR SERVER run this command: sudo wg set wg0 peer YOUR_CLIENT_PUBLIC_KEY allowed-ips YOUR_CLIENT_VPN_IP Make sure to press Allow so you can manage the VPN natively within the macOS Network Manager. Upon saving, you might get a message like this: Here is what mine looks like (compare it to the diagram at the beginning of the post for more detail): IMPORTANT: You need to replace YOUR_SERVER_PUBLIC_KEY and YOUR_SERVER_WAN_IP PrivateKey = abcdefghijklmnopqrstuvwxyz1234567890=+ Read my other post if you want to understand this in detail. Add your server as a “peer” and configure your IP Address & DNS for the remote network. Now we need to add a few more things to get it working. You can enable this if you ALWAYS want to connect to your VPN when your local network connection becomes active. You’ll also notice that there is an option for On-demand for “Ethernet” and “Wi-Fi”. You will see that it will generate keys for you. We want need to create a tunnel, so let’s start from scratch. You can find the official app on the App Store here. You need a macOS computer with admin privilegesĭownload WireGuard Client from the macOS App Store.You need a working WireGuard VPN Server ( learn how to set that up here).This is what it looks like: Prerequisites We will be connecting our macOS client to send traffic through our Ubuntu 20.04 WireGuard VPN server.If you haven’t seen that, that link is a great place to start. I am continuing my “mini-course” on Gain Flexibility & Increase Privacy with WireGuard VPN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |