internal/wguser: support for MacOS

[aep]

is macox supported? i'm just getting "file does not exist" for ConfigureDevice

[mdlayher]

I don't have a Mac. It's possible the userspace implementation's UNIX socket lives in an unexpected path on Mac, so PRs are welcome.

[aep]

yeah looks like it doesnt expose the same control sockets. no idea if it can even be controlled

[d1ss0nanz]

Works fine on my device.

It's important that you bring up the interface with "wireguard-go " before you configure it.

[duyleekun]

Works fine on my device.

It's important that you bring up the interface with "wireguard-go " before you configure it.

wireguard-go works but I want to leverage the version in the Mac App Store. Could have better implementation than the wireguard-go

[mdlayher]

Pretty sure they are the same underlying implementation and the GUI just connects to wireguard-go.

[qzi]

Works fine on my device.

It's important that you bring up the interface with "wireguard-go " before you configure it.

it there a sample about the programming WireGuard?

[stv0g]

@duyleekun

wireguard-go works but I want to leverage the version in the Mac App Store.
Could have better implementation than the wireguard-go

The version from the AppStore is based on WireGuardKit (wireguard-apple repo) which bundles wireguard-go as an macOS/iOS Network Extension.

WireGuardKit does not expose the UAPI via a standard socket. which wireguard-go uses.
Instead it uses device.IpcSet() to directly configure the tunnel device:
https://git.zx2c4.com/wireguard-apple/tree/Sources/WireGuardKitGo/api-apple.go

We maybe can extend WireGuardKit to also open a UAPI socket for macOS (iOS doesnt really make sense imho).
However, we would need to check if macOS Network Extensions are sandboxed and such a socket would be accessible by the user.

[nohajc]

We maybe can extend WireGuardKit to also open a UAPI socket for macOS (iOS doesnt really make sense imho). However, we would need to check if macOS Network Extensions are sandboxed and such a socket would be accessible by the user.

Hi, I have a working implementation of your suggestion. Since all software distributed via App Store has to be sandboxed, there's a limitation as to where you can place the unix socket. However, there's no problem accessing that socket from outside if you assume all the command-line tooling is not sandboxed (which is the case for Homebrew installations at least).

WireGuard/wireguard-apple#27
WireGuard/wireguard-go#89
#143
WireGuard/wireguard-tools#21

[stv0g]

Great work 👍🏻 I would love to see this merged.