From: kay <kay.diam@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: A go package for a fine-grained tunnels configuration
Date: Wed, 7 Apr 2021 08:31:08 +0200 [thread overview]
Message-ID: <CANaOheawQLTSWejhEC20FwVKPyE62DpRCvVB-Bun2y2hMC49Cw@mail.gmail.com> (raw)
In-Reply-To: <a34b4bf4a6910e7438351eee360a421e6d15aa79.camel@infradead.org>
You can create a dedicated executable if you wish. Currently I use it
only as a package for certain projects.
On Tue, Apr 6, 2021 at 11:51 AM David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Sun, 2021-03-14 at 18:05 +0100, kay wrote:
> > Hi Everyone,
> >
> > I'm developing a package for the fine-grained tunnel configuration in
> > different OS's, e.g. IP address, routes, DNSsettings.
> >
> > It already supports Windows, Linux and FreeBSD (+macOS with an os.Exec
> > dependency to run networksetup for DNS configuration, need help for a
> > native support without os.Exec).
> >
> > I hope you can find it useful and contribute to improving it.
> >
> > https://github.com/kayrus/tuncfg
>
> That looks interesting. Is there any chance it could be used with
> OpenConnect in place of a vpnc-script? It would be invoked as a
> separate executable with the address, routing, DNS information in
> environment variables.
>
> There may be some accumulated platform knowledge in the canonical
> vpnc-script at http://git.infradead.org/users/dwmw2/vpnc-scripts.git/
> that would be useful in tuncfg too?
>
>
prev parent reply other threads:[~2021-04-07 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 17:05 kay
2021-04-06 9:51 ` David Woodhouse
2021-04-07 6:31 ` kay [this message]
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=CANaOheawQLTSWejhEC20FwVKPyE62DpRCvVB-Bun2y2hMC49Cw@mail.gmail.com \
--to=kay.diam@gmail.com \
--cc=dwmw2@infradead.org \
--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).