wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Gopakumar Choorakkot Edakkunni <gopakumar.c.e@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wintun0.13 memmod load fails in windows10 (wintun 0.12 loads fine)
Date: Fri, 27 Aug 2021 10:42:52 -0400	[thread overview]
Message-ID: <CABK1yFDmYDONbk1DRqDpZYLLTm7uoKnHK=A2E69BSf=V_ec8Dw@mail.gmail.com> (raw)
In-Reply-To: <CABK1yFAsb8uKe+rDrhg9CsE-Sw+qr-SzmL5t5mJcSdkfjsfCDQ@mail.gmail.com>

oh well I guess I dont need a new wintun, but just the new wireguard
go. Sorry I misread it, will try that


On Fri, Aug 27, 2021 at 10:40 AM Gopakumar Choorakkot Edakkunni
<gopakumar.c.e@gmail.com> wrote:
> Thanks for the response Jason. My reason for trying 0.13 version was
> because I "thought" 0.12 had some issue because I was seeing random
> packet loss (I had another email thread for it) - but then I figured
> the random loss was because I was doing a device.New()/device.UP AND
> also reading wintun from my own goroutine, so two of them reading same
> queue. Now that I fixed it, I am happy with 0.12. I will wait for the
> next wintun release which has this memod load issue fixed (0.14 ?) and
> upgrade directly to that
> Rgds,
> Gopa.
> On Fri, Aug 27, 2021 at 10:11 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> >
> > Update to the latest wireguard-go commit.
> > https://git.zx2c4.com/wireguard-go/commit/?id=bad6caeb82edd0e22bdbcfa1ca544a5805109e14

      reply	other threads:[~2021-08-27 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 13:14 wintun0.13 memmod load fails in windows10 (wintun 0.12 loads fine) Gopakumar Choorakkot Edakkunni
2021-08-27 14:11 ` Jason A. Donenfeld
2021-08-27 14:40   ` Gopakumar Choorakkot Edakkunni
2021-08-27 14:42     ` Gopakumar Choorakkot Edakkunni [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:

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

  git send-email \
    --in-reply-to='CABK1yFDmYDONbk1DRqDpZYLLTm7uoKnHK=A2E69BSf=V_ec8Dw@mail.gmail.com' \
    --to=gopakumar.c.e@gmail.com \
    --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).