Development discussion of WireGuard
 help / color / mirror / Atom feed
From: jens <jens@viisauksena.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] LEDE / OpenWrt test - on TP-Link841Nv11 - 15MBs and crash
Date: Thu, 4 Aug 2016 13:34:08 +0200	[thread overview]
Message-ID: <b1788ba6-edc5-98d9-2f49-8321e6c3e7b1@viisauksena.de> (raw)
In-Reply-To: <CAHmME9oNd9o6rzqPU-Lh69E09oWb8_gHApxuD5+asAdQbgAcwA@mail.gmail.com>

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

On 04.08.2016 10:15, Jason A. Donenfeld wrote:
> Your prior communications have not been clear to me, and recently
> somebody took the mailing list off the CC. In order to steer this
> conversation back on a useful track, please check all that apply:
>
> [ X  ] I have tried removing "sk_clear_memalloc(sock);" and
> "sk_set_memalloc(sock->sk);" from socket.c, and the problem still
> continued.
> [  ] I have tried removing "sock->sk->sk_sndbuf = INT_MAX;" from
> socket.c, and the problem still continued.
> [ X ] I do not know how or am unable to make changes to the source
> code, recompile, and test these changes.
> [ X ] I have an extra device that I can mail to Jason so that he can
> debug the issue.
* for the extra device we may pay new ones , since you easily get them
for 15 euro per part (the TP link 841N)
* buildchain for crosscompiling is ready now, but unfortunately we test
it in our local hack space when there is free time, (n3ph and me) could
be in the next days ..

by the way : the setup from Rene is different: see this same thread -
message from 11h today from Rene.
(mainly he run iperf on one routerdevice direct, and only connect to wg
outside, where we build a uniqe wireguard bridge between two similar
routerdevices and no iperf had to be done (and regulated) on this
devices ... just storms of packets)

-- 
make the world nicer, please use PGP encryption


[-- Attachment #2: Type: text/html, Size: 2288 bytes --]

  reply	other threads:[~2016-08-04 11:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27  5:55 jens
2016-07-27  8:38 ` Jason A. Donenfeld
2016-07-27 10:13   ` Jens Viisauksena
2016-07-27 10:14     ` Jason A. Donenfeld
2016-07-27 10:26       ` Jens Viisauksena
2016-07-27 11:05         ` Jason A. Donenfeld
2016-07-27 15:02           ` Michael Gerlach
2016-07-28 11:48             ` Jason A. Donenfeld
2016-07-28 19:16               ` Michael Gerlach
2016-07-29 11:08               ` Michael Gerlach
2016-07-29 12:56                 ` Jason A. Donenfeld
2016-08-02 23:39           ` jens
2016-08-03  1:14             ` Jason A. Donenfeld
2016-08-03  6:48             ` René van Dorst
2016-08-03 16:14               ` jens
2016-08-03 20:10                 ` René van Dorst
     [not found]                   ` <923cdc92-aa01-758a-5741-99a3f6009dc5@viisauksena.de>
2016-08-04  8:15                     ` Jason A. Donenfeld
2016-08-04 11:34                       ` jens [this message]
2016-08-10  1:37                         ` jens
2016-08-15 23:05                           ` jens

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=b1788ba6-edc5-98d9-2f49-8321e6c3e7b1@viisauksena.de \
    --to=jens@viisauksena.de \
    --cc=Jason@zx2c4.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).