Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Kyle Evans <kevans@freebsd.org>
To: Ryan Roosa <ryanroosa@gmail.com>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard-freebsd handshaking issue upon underlying WAN
Date: Wed, 10 Nov 2021 00:36:41 -0600	[thread overview]
Message-ID: <CACNAnaHYUxPvV53NditMvNfkn9YvYSv=ief=FDew2kmHjJ5hgg@mail.gmail.com> (raw)
In-Reply-To: <CABOEyuKT7ebroX2yRU9xixDVCBmJV15Hy1vh-nUwrmdGjX6=QQ@mail.gmail.com>

On Tue, Nov 9, 2021 at 11:19 AM Ryan Roosa <ryanroosa@gmail.com> wrote:
>
> On Wed, Oct 27, 2021 at 7:45 PM Ryan Roosa <ryanroosa@gmail.com> wrote:
> >
> > On Tue, Oct 26, 2021 at 5:29 AM Jason A. Donenfeld <Jason@zx2c4.com> 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 -- https://w-g.pw/l/yQTw -- 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
> >
> > 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.
> >
> > Cheers,
> > -Ryan
> >
>
> Just wanted to provide some feedback that pfSense development
> snapshots of 2.6.0 running WireGuard package v0.1.5_2 include the fix
> and there I have validated that removing WAN connectivity at various
> intervals up to 10 minutes no longer impacts subsequent handshaking
> once the connection is restored. I have not yet tested on OPNSense but
> I imagine the results will match once I do (if not I will reach out).
> Thanks to everyone for their efforts on resolving this one, I really
> appreciate it.
>
> -Ryan
>

That's good to hear, thanks for following up! :-)

Kyle Evans

      reply	other threads:[~2021-11-10  6:39 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
2021-11-09 17:19     ` Ryan Roosa
2021-11-10  6:36       ` Kyle Evans [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='CACNAnaHYUxPvV53NditMvNfkn9YvYSv=ief=FDew2kmHjJ5hgg@mail.gmail.com' \
    --to=kevans@freebsd.org \
    --cc=Jason@zx2c4.com \
    --cc=ryanroosa@gmail.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).