wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Chris Branch <cbranch@cloudflare.com>
To: WireGuard@lists.zx2c4.com
Subject: wireguard-go foreground mode broken on Linux
Date: Mon, 3 Dec 2018 10:06:30 +0000	[thread overview]
Message-ID: <CAMhRzNT3Ss4P4h4AFxiZLKcmEG59=sXYFDdFgmnpF9MMWOA0vQ@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 509 bytes --]

Though this isn't a common use case, I thought I should note that commit
2e772194cf7cd7c37d24364a9f9d407dc96a25e8 causes a regression in
wireguard-go running in foreground mode (-f flag); packets are never read
from the TUN interface.

I got as far as debugging that it works again if you call Fd() at least
once after SetNonblock i.e. it's not introduced by any of the other changes
in that commit. I've stopped looking at this for now, but thought I would
warn others and see if anyone else has some ideas.

[-- Attachment #1.2: Type: text/html, Size: 567 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2018-12-03 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 10:06 Chris Branch [this message]
2018-12-06 16:18 ` wireguard-go foreground mode broken on Linux Jason A. Donenfeld
     [not found]   ` <CAHmME9pyCqLvTOBHCFYttJJzYGSyf26Way1FmhUtr0NvB8jU6Q@mail.gmail.com>
     [not found]     ` <CAMhRzNQ6QwgGT4_LTrVrZ-8LL8bO=T5roFzLRdyGWwVHChvf2w@mail.gmail.com>
2018-12-06 16:37       ` Jason A. Donenfeld
2018-12-06 16:40         ` 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='CAMhRzNT3Ss4P4h4AFxiZLKcmEG59=sXYFDdFgmnpF9MMWOA0vQ@mail.gmail.com' \
    --to=cbranch@cloudflare.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).