wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Gopakumar Choorakkot Edakkunni <gopakumar.c.e@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: wireguard-windows: packets dropped in NativeTun Read()
Date: Wed, 25 Aug 2021 15:05:19 -0400	[thread overview]
Message-ID: <CABK1yFC+mH4=EzCGd7m20qFykAnwG=hxiAcvVets-HP1=JKA9Q@mail.gmail.com> (raw)


I am experimenting with wintun as the choice of my driver for a vpn
client I am writing on windows. I was very quickly able to get
bootstrapped using the wireguard-windows repository (thanks!!), I
created a tunnel and when I use the Read() api (tun_windows.go), I see
that quite often I am missing packets. How do I know this ? - I run a
tshark on the tun interface (needs editpcap to convert from ethernet
to ip format), and then I compare packets there with what I get, and I
see my read missing packets present in wireshark.

The traffic rate is very low - just regular browsing to websites, no
major traffic. I am reading from the tun interface from a goroutine, I
suspected maybe I/O bound reads might be not scheduled enough by go
scheduler, so I increased the go threads. I thought maybe the ring
size need to increase so I made it 32Mb etc.. - still no good, I still
get Rx packets missing. Kind of clueless at this point - any
pointers/hints/suggestions will be appreciated a lot !!


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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CABK1yFC+mH4=EzCGd7m20qFykAnwG=hxiAcvVets-HP1=JKA9Q@mail.gmail.com' \
    --to=gopakumar.c.e@gmail.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).