Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Ryan Roosa <>
To: "Jason A. Donenfeld" <>
Cc: WireGuard mailing list <>,
	Kyle Evans <>
Subject: Re: wireguard-freebsd handshaking issue upon underlying WAN
Date: Wed, 27 Oct 2021 19:45:33 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Jason,
Thank you very much for this! I received word from the OPNSense team
that the referenced snapshot should be made available in OPNSense
21.7.5. I will test and provide feedback just as soon as I can get on
the aforementioned OPNSense release which includes the fix.


On Tue, Oct 26, 2021 at 5:29 AM Jason A. Donenfeld <> wrote:
> Hi Ryan,
> Thanks for the report. Kyle saw your reddit post earlier and tracked
> this down, I think/hope, to a bug in the state machine cranking. I
> committed the fix here -- -- which will be part
> of the next snapshot. Hopefully that will fix the issue, but if it
> doesn't, please do update this thread so we can keep searching.
> Regards,
> Jason

  reply	other threads:[~2021-10-27 23:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 17:17 Ryan Roosa
2021-10-26  9:29 ` Jason A. Donenfeld
2021-10-27 23:45   ` Ryan Roosa [this message]
2021-11-09 17:19     ` Ryan Roosa
2021-11-10  6:36       ` Kyle Evans

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 \ \ \ \ \ \

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