From: Simon Ruderich <simon@ruderich.org>
To: Mathias Hall-Andersen <mathias@hall-andersen.dk>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [PATCH 7/7] tun_darwin: adapt to TUNDevice interface change
Date: Mon, 1 Jan 2018 12:36:48 +0100 [thread overview]
Message-ID: <20180101113648.GA11049@ruderich.org> (raw)
In-Reply-To: <510f63e7-e50a-46a1-b2d8-ea49ae5f2fc8@hall-andersen.dk>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
On Sun, Dec 31, 2017 at 08:17:58PM +0100, Mathias Hall-Andersen wrote:
> I am still fixing the interface up / down semantics (stopping / starting
> peer timers and routines not needed when the interface is down).
Regarding this, with d73f960 ("Peer timer teardown", 2017-12-29)
I can't configure wireguard-go via wg anymore. wg just hangs on
any command, everything works fine with 996c7c4 ("Removed
IFF_NO_PI from TUN linux", 2017-12-04).
Any idea what's wrong? Not sure if this is related to the test
suite failure which also occurs since d73f960 (only visible with
my TUN patches or the test suite fails to build).
Regards
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-01-01 11:35 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
2018-01-01 11:14 ` Simon Ruderich
2018-01-01 11:36 ` Simon Ruderich [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=20180101113648.GA11049@ruderich.org \
--to=simon@ruderich.org \
--cc=mathias@hall-andersen.dk \
--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).