Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Samuel Holland <samuel@sholland.org>
To: wireguard@lists.zx2c4.com
Subject: Re: Instability during large transfers
Date: Thu, 16 Feb 2017 22:48:56 -0600	[thread overview]
Message-ID: <05adeaed-20ff-ce42-b8c6-73bbc55d7021@sholland.org> (raw)
In-Reply-To: <7a3a5f6d-1eb5-ef32-097e-e24c2f9d2805@sholland.org>

[-- Attachment #1: Type: text/plain, Size: 729 bytes --]

On 02/16/17 12:38, Samuel Holland wrote:
> I will enable netconsole on the firewall now that I can hopefully
> reproduce the panic, but since the networking setup there is rather
> complicated (vlans on top of bridges) I'm not sure if I will get all
> of the panic messages.

Success! I reproduced the panic and got full logs.

I ran:
$ ssh <server> cat /dev/zero | dd of=/dev/null bs=4096 status=progress
108295966720 bytes (108 GB, 101 GiB) copied, 17437 s, 6.2 MB/s
packet_write_wait: Connection to <server> port 22: Broken pipe

26440386+4 records in
26440386+4 records out
108299829248 bytes (108 GB, 101 GiB) copied, 18413 s, 5.9 MB/s

Attached is the extended netconsole output from the firewall.

Hope this helps,
Samuel

[-- Attachment #2: wireguardpanic.gz --]
[-- Type: application/gzip, Size: 3740 bytes --]

  reply	other threads:[~2017-02-17  4:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 18:38 Samuel Holland
2017-02-17  4:48 ` Samuel Holland [this message]
2017-02-17 13:36   ` Jason A. Donenfeld
2017-02-17 17:37     ` Samuel Holland
2017-03-01 22:44     ` Samuel Holland
2017-03-21 15:06       ` Samuel Holland
2017-03-21 17:33         ` Jason A. Donenfeld

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=05adeaed-20ff-ce42-b8c6-73bbc55d7021@sholland.org \
    --to=samuel@sholland.org \
    --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).