From: Mathias Hall-Andersen <mathias@hall-andersen.dk>
To: Simon Ruderich <simon@ruderich.org>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [PATCH 7/7] tun_darwin: adapt to TUNDevice interface change
Date: Sun, 31 Dec 2017 20:17:58 +0100 [thread overview]
Message-ID: <510f63e7-e50a-46a1-b2d8-ea49ae5f2fc8@hall-andersen.dk> (raw)
In-Reply-To: <33cfb3925304d5047a6e9e81eef0900329aad3b5.1514726309.git.simon@ruderich.org>
Hi Simon
Thanks for your patches!
I am still fixing the interface up / down semantics (stopping / starting
peer timers and routines not needed when the interface is down).
I hope to fix this and merge your linux code in the next couple of days.
This should bring us very close to a usable linux client.
I will look at your OSX code when I have access to an OSX machine.
On Windows, we preferably want to move away from the OpenVPN driver
horrer show altogether.
Once again, thanks for the patch set.
Best Regards & A happy new year
Mathias Hall-Andersen
next prev parent reply other threads:[~2017-12-31 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 16:16 [PATCH 0/7] TUN fixes Simon Ruderich
2017-12-31 16:16 ` [PATCH 1/7] tun: TUNDevice: document behavior of offset parameter Simon Ruderich
2017-12-31 16:16 ` [PATCH 2/7] tun_linux: add PIHeaderSize constant instead of magic value Simon Ruderich
2017-12-31 16:16 ` [PATCH 3/7] tun_linux: document packet information header values Simon Ruderich
2017-12-31 16:16 ` [PATCH 4/7] helper_test: reorder DummyTUN functions to follow interface order Simon Ruderich
2017-12-31 16:16 ` [PATCH 5/7] helper_test: adapt to TUNDevice interface change Simon Ruderich
2017-12-31 16:16 ` [PATCH 6/7] tun_darwin: " Simon Ruderich
2017-12-31 16:16 ` [PATCH 7/7] " Simon Ruderich
2017-12-31 19:17 ` Mathias Hall-Andersen [this message]
2018-01-01 11:14 ` Simon Ruderich
2018-01-01 11:36 ` Simon Ruderich
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=510f63e7-e50a-46a1-b2d8-ea49ae5f2fc8@hall-andersen.dk \
--to=mathias@hall-andersen.dk \
--cc=simon@ruderich.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).