Development discussion of WireGuard
 help / color / mirror / Atom feed
From: tormen@mail.ch
To: Johnny Utahh <mailman-wireguard.com@johnnyutahh.com>
Cc: wireguard@lists.zx2c4.com, Eiji Tanioka <tanioka404@gmail.com>
Subject: Re: WireGuard for macOS (cmdline vs GUI)
Date: Sun, 22 Mar 2020 12:31:33 +0100	[thread overview]
Message-ID: <83BEF210-B2E5-4A47-888B-BD70516F9637@mail.ch> (raw)
In-Reply-To: <34c24ae1-c4b1-33ef-cf21-2c3f72db9194@johnnyutahh.com>

FYI: Thanks a lot for your answers to my initial question!

I did not know the ncutil command yet :)
It works like charm and allows for nice "remote" control of the GUI app via cmdline.

Tormen

> On 22. Mar 2020, at 04:49, Johnny Utahh <mailman-wireguard.com@johnnyutahh.com> wrote:
> 
> I wrote:
>> The macOS wireguard-tools command line does not seem to work concurrently with the GUI app
> 
> ...because it's not supposed to. (sigh)  Simple updates to https://www.wireguard.com/install/ along with a short note for macOS `launchctl` (or similar gizmo for auto bootup) will help make things more clear. Details:
> 
> https://www.reddit.com/r/WireGuard/comments/fmn93h/how_to_display_or_manage_macos_wireguard_status/fl5xscg/?context=8&depth=9
> 
> ~J
> 
> 
> On 2020-03-21 4:45 PM, Johnny Utahh wrote:
>> The macOS wireguard-tools command line does not seem to work concurrently with the GUI app, at least on my system:
>> 
>> https://www.reddit.com/r/WireGuard/comments/fmn93h/how_to_display_or_manage_macos_wireguard_status 
>> 
>> Anybody know why?
>> 
>> 
>> On 2020-03-07 10:18 PM, Eiji Tanioka wrote:
>>> Hi,
>>> 
>>> How about install wireguard-tools from Homebrew ?
>>> https://www.wireguard.com/install/#macos-homebrew-and-macports-basic-cli-homebrew-userspace-go-homebrew-tools-macports-userspace-go-macports-tools 
>>> 
>>> I have not installed, it seems installing `wg`, `wg-quick` command and
>>> "wireguard-go" backend.
>>> I think you can use them for Connect / Disconnect from CLI.
>>> 
>>> And,
>>>> I would love to use both (GUI + CLI): No automatic connect in the GUI,
>>> I'm using "On-Demand" option for automatic connect, is it appropriate
>>> for your purpose?
>>> 
>>> Regards,
>>> 
>>> 2020年3月8日(日) 10:01 <tormen@mail.ch>:
>>>> Dear Wireguard Team,
>>>> 
>>>> First off, thanks a lot for the client for macOS !!
>>>> 
>>>> Is there a possibility to issue a "Connect" / "Disconnect" command from the command line
>>>> instead of using the buttons in the GUI ?
>>>> 
>>>> I would love to use both (GUI + CLI): No automatic connect in the GUI, but rather automatically connect / reconnect via script (so via command-line interface, CLI).
>>>> And I don't like the idea of not using the GUI and switching to the cli version as then I don't have the icon.
>>>> 
>>>> Thanks a lot in advance for any hint or feedback!
>>>> 
>>>> Tormen
>> 


  reply	other threads:[~2020-03-22 11:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-07 17:03 WireGuard for macOS tormen
2020-03-08  2:37 ` Ben Hyde
2020-03-08  4:18 ` Eiji Tanioka
2020-03-21 21:45   ` Johnny Utahh
2020-03-22  3:49     ` WireGuard for macOS (cmdline vs GUI) Johnny Utahh
2020-03-22 11:31       ` tormen [this message]
2020-03-30  2:22     ` WireGuard for macOS Jason A. Donenfeld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83BEF210-B2E5-4A47-888B-BD70516F9637@mail.ch \
    --to=tormen@mail.ch \
    --cc=mailman-wireguard.com@johnnyutahh.com \
    --cc=tanioka404@gmail.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).