Macport Wireguard installation not recognized

[digeratus]

I installed Wireguard using Macports instead of Homebrew - at the time the the brew version of Wireguard was out of date. https://www.wireguard.com/install/#macos-homebrew-and-macports-basic-cli-homebrew-userspace-go-homebrew-tools-macports-userspace-go-macports-tools

Macports installs wireguard binaries in /usr/local/bin and the configuration files are expected to be in /opt/local/etc/wireguard not /usr/local/etc/wireguard as created by Homebrew.

Would it be possible to adjust for the Macport installation paths?

Thanks

[aequitas]

Sure, only need to update the list here: https://github.com/aequitas/macos-menubar-wireguard/blob/master/Shared/Const.swift#L37

Please note this app is not really maintained anymore since the official client for Wireguard is released. But if you prefer to use this App over the official client I can make a new release with this feature if you like.

[digeratus]

Hi Johan, First thinks for your work. Very much appreciated. The problem with the official wireguard client is that it doesn't support older versions of macOS - I believe it requires Catalina now. For environments like schools that still have some of these older Macs in use your app is gold. If it doesn't require much work from you, please make a new release version available with this feature. Thanks

…

On Dec 16, 2019, 1:42 PM -0500, Johan Bloemberg ***@***.***>, wrote: Sure, only need to update the list here: https://github.com/aequitas/macos-menubar-wireguard/blob/master/Shared/Const.swift#L37 Please note this app is not really maintained anymore since the official client for Wireguard is released. But if you prefer to use this App over the official client I can make a new release with this feature if you like. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[aequitas]

No problem. Do I understand correctly that the binary is in the same place as with Homebrew /usr/local/ and only the config is in /opt/local/ or are both under /opt/local/?

[digeratus]

The binary is in /opt/local/bin and the config is expected in /opt/local/etc/wireguard. All of it is in /opt/local/.

…

On Dec 17, 2019, 4:12 AM -0500, Johan Bloemberg ***@***.***>, wrote: No problem. Do I understand correctly that the binary is in the same place as with Homebrew /usr/local/ and only the config is in /opt/local/ or are both under /opt/local/? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[aequitas]

In that case there is already a workaround, you can try:

sudo defaults write WireGuardStatusbarHelper brewPrefix /opt/local

This will change the prefix for both the binary and the config to /opt/local. You might get a warning from the App that Wireguard is not installed, but that can be ignored.

Let me know if this works for you.

[digeratus]

Ok I'll give it a try and let you know. Thanks

…

On Dec 17, 2019, 3:22 PM -0500, Johan Bloemberg ***@***.***>, wrote: In that case there is already a workaround, you can try: sudo defaults write WireGuardStatusbarHelper brewPrefix /opt/local This will change the prefix for both the binary and the config to /opt/local. You might get a warning from the App that Wireguard is not installed, but that can be ignored. Let me know if this works for you. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[digeratus]

It didn't work. I figure I'll just wait for the brew version of wireguard to get updated and then reinstall. Thanks

…

On Dec 17, 2019, 3:22 PM -0500, Johan Bloemberg ***@***.***>, wrote: In that case there is already a workaround, you can try: sudo defaults write WireGuardStatusbarHelper brewPrefix /opt/local This will change the prefix for both the binary and the config to /opt/local. You might get a warning from the App that Wireguard is not installed, but that can be ignored. Let me know if this works for you. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[Fastidious]

I know this is quite old, but I am using WireGuard installed by brew, and this app works like a charm. Thank you so much for creating it, @aequitas!

[Fastidious]

@aequitas I just got a new machine, able to run Catalina. I tried the official WireGuard app, and it worked, mostly. I have two server profiles, one for mesh and one for full VPN. The mesh one (which uses Unbound) will not work for most websites. It is supposed not to use WireGuard for anything, but for IPs the WireGuard server hands out (hence mesh).

Installing WireGuard with brew, and using your app made it work like a charm, as intended, just as it did on my previous machine with High Sierra. There are advantages on using your app instead of the official client and, for me, using your app was vital to get my setup running as wanted.

[aequitas]

Good to hear :). I still plan on fixing the underlying issue of using different/custom paths for the Wireguard executable sometime, so I'll keep the issue open for now.

[alexanderharm]

Hello there, it would be great if you could find the time to update this app. The official app is out but it only supports one active tunnel at anytime which I find a nuissance. I like your app since it simply does the job and does it right. Thank you!

[thenktor]

I also found this because I need to start multiple tunnels, which does not work with the official app. But sadly it does not work with wireguard-tools from Macports.

[alexanderharm]

You create simply create a symlinks in the expected places to make it work... e. g.

create a symlink for the binaries into /usr/local/bin and the configs to /usr/local/etc/wireguard