Development discussion of WireGuard
 help / color / mirror / Atom feed
From: eric brandl <ericb0813@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Data Connection Lost Win10 (Server) Win10 (Clients) 37
Date: Sat, 28 Dec 2019 15:03:20 -0600	[thread overview]
Message-ID: <CALXT2kFp9SPFELS97vHJFndGH7cFh0=gjC1h9Tuv2LgSMHeJ-Q@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2384 bytes --]

Issue I am having is sporadically around every 5 to 30 min all peer
connections no longer send traffic over them, and the only way to get them
working again is to restart the WireGuard server (Win 10) .


The log shows this:

2019-12-28 01:39:46.625: [TUN] [GameNet] Failed to write packet to TUN
device: file already closed

2019-12-28 01:39:46.629: [TUN] [GameNet] Binding v4 socket to interface 16
(blackhole=false)

2019-12-28 01:39:46.631: [TUN] [GameNet] Failed to write packet to TUN
device: file already closed

2019-12-28 01:39:46.649: [TUN] [GameNet] Failed to write packet to TUN
device: file already closed

2019-12-28 01:39:46.668: [TUN] [GameNet] Failed to write packet to TUN
device: file already closed

2019-12-28 01:39:46.692: [TUN] [GameNet] Failed to write packet to TUN
device: file already closed

2019-12-28 01:39:46.714: [TUN] [GameNet] Failed to write packet to TUN
device: file already closed

2019-12-28 01:39:46.730: [TUN] [GameNet] Failed to write packet to TUN
device: file already closed


Server Config:

[Interface]
PrivateKey = SNIP
ListenPort = 5687
Address = 10.152.152.1/24
MTU = 1360

[Peer]
PublicKey = BMIr6jiTNpu1wiSAqTLBUBFnM3DBW+RMdvapkmnFAiY=
AllowedIPs = 10.152.152.2/32

[Peer]
PublicKey = gY0SvOX8lKfLkMXHIwA6pNnB8ooc36vCOPlQ0WmR5Es=
AllowedIPs = 10.152.152.3/32

[Peer]
PublicKey = NcbtXceq1dh3khRv+YXXXw9RmJJH+r0acVIGbJ3qWSY=
AllowedIPs = 10.152.152.4/32

[Peer]
PublicKey = LkMrfhjHOz6VgL9gTsBkcahkw++RMYokMbJnViQ9xVM=
AllowedIPs = 10.152.152.5/32

[Peer]
PublicKey = YAKEhGM4Wr1SYSb197ugyV7IKqUOh+Jzpg7NVNLa3AM=
AllowedIPs = 10.152.152.6/32

[Peer]
PublicKey = MZ1ycd1MdUvFUDpRxgY0hc7/jwTP9TuuYB6uwmyYdmQ=
AllowedIPs = 10.152.152.7/32

[Peer]
PublicKey = Re5hkZG10PuN993GVRkkYCjjnyKyk96SCN4vFP5l/mM=
AllowedIPs = 10.152.152.8/32

[Peer]
PublicKey = Yrx9W1PC60Uw9tpsRIByV0U+aW3eE210X1LCxTnk21w=
AllowedIPs = 10.152.152.10/32

Example Client Config:

[Interface]
PrivateKey = generated_private_key
ListenPort = 5687
Address = 10.152.152.3/24
MTU = 1360

[Peer]
PublicKey = wQE513lYAgeLMcA72rGUnAcqknTYRlC2+oyWKI4Q1j4=
AllowedIPs = 10.152.152.0/24
Endpoint = SNIP:5687
PersistentKeepalive = 40

Things I have tried:

Rolling back to 35

Changing MTU

Switching NIC in Proxmox from Intel to Realtek and back


Other Notes:

With only two peers connected it seems to be less of an issue, with 8 or so
connected we get this issue quicker.

[-- Attachment #1.2: Type: text/html, Size: 10716 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

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

             reply	other threads:[~2019-12-30  9:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-28 21:03 eric brandl [this message]
2019-12-30 11:03 ` Jason A. Donenfeld
2019-12-30 21:01 ` Blaok
2020-01-08  7:40   ` Jason A. Donenfeld
2020-01-15 23:49     ` Blaok

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='CALXT2kFp9SPFELS97vHJFndGH7cFh0=gjC1h9Tuv2LgSMHeJ-Q@mail.gmail.com' \
    --to=ericb0813@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).