wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: minus <minus@mnus.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH wireguard-go] conn: linux: fix incorrect endpoint address
Date: Wed, 24 Nov 2021 00:23:10 +0100	[thread overview]
Message-ID: <fef7daf2-adf7-e042-4977-46fda04aa07d@mnus.de> (raw)
In-Reply-To: <CAHmME9pEf9=6C3eAXfanftBt4LJ4viRszQc5oG3Jt9H7Fxd68A@mail.gmail.com>

On 23/11/2021 22.01, Jason A. Donenfeld wrote:
> Thank you for catching this regression!You're welcome. Unfortunately, I found another one: On an old Debian 8 
system, wireguard-go does not receive or send packets anymore, nor does 
`wg show` show any sent/received stats. On a current Arch system it 
works fine. git bisect points to e3134bf (device: defer state machine 
transitions until configuration is complete) as first bad commit. I 
haven't further tried reproducing it, hoping that it's something obvious 
to you.

  reply	other threads:[~2021-11-23 23:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 19:03 [PATCH wireguard-go] conn: linux: fix incorrect endpoint address Thomas Renoth
2021-11-23 21:01 ` Jason A. Donenfeld
2021-11-23 23:23   ` minus [this message]
2021-11-25 16:38     ` Jason A. Donenfeld
2021-11-29  0:24       ` wireguard-go fails to send/receive data minus
2021-11-29 17:34         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fef7daf2-adf7-e042-4977-46fda04aa07d@mnus.de \
    --to=minus@mnus.de \
    --cc=Jason@zx2c4.com \
    --cc=wireguard@lists.zx2c4.com \


* 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).