From: Eiji Tanioka <tanioka404@gmail.com>
To: tormen@mail.ch
Cc: wireguard@lists.zx2c4.com
Subject: Re: WireGuard for macOS
Date: Sun, 8 Mar 2020 13:18:48 +0900 [thread overview]
Message-ID: <CAA2ss9EE35hYqjOC_uY9REe-Mp0D04bPH9Ldg0wConQs8VG24A@mail.gmail.com> (raw)
In-Reply-To: <F77DB7FE-175E-48E4-A071-FF86D290B494@mail.ch>
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
next prev parent reply other threads:[~2020-03-08 4:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 17:03 tormen
2020-03-08 2:37 ` Ben Hyde
2020-03-08 4:18 ` Eiji Tanioka [this message]
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
2020-03-30 2:22 ` WireGuard for macOS Jason A. Donenfeld
-- strict thread matches above, loose matches on Subject: below --
2019-02-16 1:26 Jason A. Donenfeld
2019-02-17 19:05 ` Le Sandie
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=CAA2ss9EE35hYqjOC_uY9REe-Mp0D04bPH9Ldg0wConQs8VG24A@mail.gmail.com \
--to=tanioka404@gmail.com \
--cc=tormen@mail.ch \
--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).