Development discussion of WireGuard
 help / color / mirror / Atom feed
From: ѽ҉ᶬḳ℠ <vtol@gmx.net>
To: wireguard@lists.zx2c4.com
Subject: high count of dropped packets
Date: Fri, 17 May 2019 15:18:28 +0200	[thread overview]
Message-ID: <de3c132d-9c25-dcd8-77f9-179c149dc179@gmx.net> (raw)

Hi,

I am experiencing an inexplicable high count of dropped packets between
2 wg nodes:

local node (0.0.20190123 in kernel mode on OpenWRT 18.06 with kernel
4.14.113)

> wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc cake state UNKNOWN
> mode DEFAULT group defau
>     link/none  promiscuity 0
>     wireguard addrgenmode none numtxqueues 1 numrxqueues 1
> gso_max_size 65536 gso_max_segs 65535
>     RX: bytes  packets  errors  *dropped* overrun mcast
>     8598420    6020     0           *9518*        0              0
>     TX: bytes  packets  errors  dropped carrier collsns
>     3188456    12491    0       0       0       0

remote node (0.0.20190406 in kernel mode on Ubuntu 19.04 with kernel
5.0.0-13)

>  wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state
> UNKNOWN mode DEFAULT group default qlen 1000
>     link/none  promiscuity 0
>     wireguard addrgenmode none numtxqueues 1 numrxqueues 1
> gso_max_size 65536 gso_max_segs 65535
>     RX: bytes                          packets  errors  dropped
> overrun mcast
>     1442441184 3511784  1386        50      0       0
>     TX: bytes        packets  errors  dropped carrier collsns
>     8661652804 7150433  0       454     0       0

What could be the cause and how to remedy?

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

                 reply	other threads:[~2019-05-18 16:45 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:
  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=de3c132d-9c25-dcd8-77f9-179c149dc179@gmx.net \
    --to=vtol@gmx.net \
    --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).