-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please support native VPNs from network preferences #7
Comments
Doubtful. To do that I need to be able to get a list of the system VPNs, and that doesn't work (on my El Cap system, at least). The command that is supposed to list system VPNs ( So unless you know of a way to get a list of system VPNs that actually works, it's not possible. |
I'd like to bump this - I have no idea why Any chance you'd be open to revisiting this? I'd be happy to try and generate a pull request or something similar - would be very handy, as I have multiple system VPNs and multiple OpenVPNs in Viscosity. This would also possibly be a way to get WireGuard support, since that hooks into the native VPN framework from my understanding, which would also be awesome. EDIT: wow that was fast. Thank you! |
Sure. I'm on Catalina now. I'll add a VPN and see if I can do anything with it. |
I can also confirm after testing that whatever that plugin is doing for managing system VPNs, it works with WireGuard as well (since it adds VPNs to the system network interfaces via the network extension framework). See attached for L2TP and WireGuard VPNs (and I know screenshots aren't code, but, it's at least a start...): Appears to work even when the WireGuard menubar app is closed, which is great - the config should only need to be imported, and after that, unless status is desired in the menubar, the workflow would not need to open the app. |
The problem was that it didn't work on my Mac. And if it doesn't work on my Mac, I can't build a workflow around it. |
For sure. Are you saying it still doesn't work on your Mac, or that it didn't work when you tested it a year or two back? |
Umm … both, I think. I've just checked, and I have a bunch of IKEv2 VPNs in Network Preferences, but |
I just created a test WireGuard VPN and then ran
|
Further testing reveals that the wireguard menubar app does need to be running for the VPN to connect, but that seems easy enough to fix. The other issue is a bit trickier. scutil does not support IKEv2 VPNs; this is apparently a bug. What about including something like vpnutil bundled into the workflow? |
|
Huh? Maybe we're not looking at the same version. The one in the blog post doesn't do listing, no. I followed the link at the bottom of the post to the GitHub for vpnutil. It looks like he cut the 1.0 release not two weeks ago, and that version definitely has listing. $ curl -O https://github.com/Timac/VPNStatus/releases/download/1.0/vpnutil.zip
$ unzip vpnutil.zip
$ xattr -c vpnutil; chmod +x vpnutil; mv vpnutil /usr/local/bin/vpnutil
$ vpnutil list
L2TP Disconnected
algo-wireguard Disconnected seems to work for me. |
Right. I built it from the source code, which hasn't been updated in 2 years, and it doesn't support listing. |
Following up on this - the source code is not updated in master, no. I've no idea why. I'll reach out and ask, and see if he's willing to change that. Meantime, however, the Source code.zip file attached to the 1.0 release does have the most recent source for I'm also curious as to why you're building from source; would bundling the compiled utility and checking for new binary releases via GitHub not be an option? Cheers again for this utility, even as it stands. :) |
Following up on this, the source for VPNutil is definitely up to date in the tree (as of April 2023). I don't use IKE VPNs anymore, so I don't know if scutil is still broken, but more VPNs would be awesome. |
This is a fantastic workflow!
I'm a heavy user of VPNs, so I'm desperately want this workflow to manage all my VPN softwares and the VPN configured natively in the macOS.
Could you also add support to that?
Thanks!
The text was updated successfully, but these errors were encountered: