Wireguard Macos 10.13 Download

The wireguard configuration is not stored in config files but in the MacOS keychain. Search for "WireGuard Tunnel" in the login keychain.If you cannot find it after a Wireguard update or a Catalina update, restore your login keychain from a TimeMachine backup.The restored keychain should contain all WireGuard Tunnel configurations.The tunnel config can then be found in the "Password" field. Note that there are multiple lines; you see only [Interface] initially.Just Copy all content (CMD+A CMD+C) and then paste it into a new WireGuard tunnel config (CMD+V).

Now we can create the main /etc/wireguard/wg0.conf configuration file. Make sure to paste in your private key from /etc/wireguard/privatekey for the PrivateKey section of the file. Also, replace both ens1 instances with the interface the server connects to the internet with.

Download Zip

On the Wireguard server, shutdown the Wireguard interface with sudo wg-quick down wg0. Next, append the following to the /etc/wireguard/wg0.conf config file. The client public key can be copied directly from the Wireguard GUI. Modify the AllowedIPs to the static IP assignment from earlier, ensuring that the subnet is /32. Repeat for each client you wish to grant access.

Here for MacOS I use just WireGuard - no Eddie - using config files downloaded from Air's configurator in the client area. No or failed DNS resolution is telling you to check the "Endpoint = ..." line in the WireGuard config file that you imported into that app. If you selected just one server in the configurator, the Endpoint should be a numerical IP address and port (I think Air uses 1637 ordinarily) separated by a colon, and that should work fine. DNS resolution of course is the translation of a domain name like us.vpn.airdns.org into a numeric IP address. If you have a domain name as Endpoint, perhaps you should for now try a numerical IP instead, in case you have one of those race conditions going where DNS resolution is set to go through a wireguard tunnel that isn't up because DNS resolution isn't up yet.

In any case, I expect that using Eddie is your real goal here. I haven't tried wireguard via Eddie, so I leave that to others. Should be easy. Just don't try to enable the WireGuard app at the same time, unless I am totally uninformed and that's exactly what the Eddie instructions say to do!

Again, I haven't seen the Eddie instructions, but my educated guess is that Eddie does not need the WireGuard app itself and that running both Eddie and WireGuard at once would create a routing mess of some sort. So either just try it or - ahem! - RTFM quite carefully for Eddie and then try it. I'm leaving the reading burden entirely on you though, as I'm not an Eddie user so have no personal interest.

And readers with actual Eddie wireguard experience should feel free to join in here!

The Problem: including 0.0.0.0/0 as an allowed IP routes all traffic through the Wireguard interface (good!), including the wireguard traffic itself (not good!). As far as I can tell, all network traffic ends up in a loop and never actually leaves the machine.

caa09b180b

Page updated

Google Sites

Report abuse