Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Mike O'Connor <mike@pineview.net>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Significant Dropped Packets on WG interface
Date: Thu, 14 May 2020 16:35:30 +0930	[thread overview]
Message-ID: <21e7d9c5-1d0d-efc0-e698-f59325960df1@pineview.net> (raw)

Hi All

For the last few weeks my Wireguard link which I use to as my default
gateway has been having issues with TCP connections stalling.

I've been trying to work out what is wrong. I just noticed that the
Wireguard link has dropped packets at both ends.

wg-p2p    Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:104.127.123.10  P-t-P:103.127.123.10 
Mask:255.255.255.248
          inet6 addr: 2506:c500:ff4:1::ab/64 Scope:Global
          inet6 addr: fe80::e6/64 Scope:Link
          UP POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:141849 errors:0 dropped:5915 overruns:0 frame:0
          TX packets:141626 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:33771496 (33.7 MB)  TX bytes:14348632 (14.3 MB)

wg-p2p    Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:104.127.123.9  P-t-P:103.127.123.9  Mask:255.255.255.248
          inet6 addr: 2506:c500:ff4:1::aa/64 Scope:Global
          inet6 addr: fe80::dc/64 Scope:Link
          UP POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:663287 errors:1 dropped:1433 overruns:0 frame:1
          TX packets:1023948 errors:594 dropped:13 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:110192140 (110.1 MB)  TX bytes:872273836 (872.2 MB)

Note the above is after a reboot of both end points (about 4 mins)

One end is running a 4.4.0 kernel

ii  wireguard                            
1.0.20200510-1~16.04                            all          fast,
modern, secure kernel VPN tunnel (metapackage)
ii  wireguard-dkms                       
1.0.20200429-2~16.04                            all          fast,
modern, secure kernel VPN tunnel (DKMS version)
ii  wireguard-tools                      
1.0.20200510-1~16.04                            i386         fast,
modern, secure kernel VPN tunnel (userland utilities)

The other is

ii  wireguard                                
1.0.20200319-1ubuntu1~14.04                          all          fast,
modern, secure kernel VPN tunnel (metapackage)
ii  wireguard-dkms                           
1.0.20200429-1~14.04                                 all          fast,
modern, secure kernel VPN tunnel (DKMS version)
ii  wireguard-tools                          
1.0.20200319-1ubuntu1~14.04                          amd64        fast,
modern, secure kernel VPN tunnel (userland utilities)

I was thinking of rebuilding the ubuntu 14.04 to a 16.04 (18.04 uses
netplan and can be a real pain to setup)


I've done my best to check the underlying Internet and I do not think
packets are be dropped in general or between the two end points.

How do I tell why the packets have been dropped ?

What do I need to look at to try to fix this ?


Thanks

Mike


             reply	other threads:[~2020-05-14  7:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14  7:05 Mike O'Connor [this message]
2020-05-14  9:15 ` Roman Mamedov
2020-05-14  9:34   ` Mike O'Connor
2020-05-14  9:53   ` Mike O'Connor
2020-05-17  8:50   ` Mike O'Connor

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=21e7d9c5-1d0d-efc0-e698-f59325960df1@pineview.net \
    --to=mike@pineview.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).