From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Jason@zx2c4.com Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id a7b29223 for ; Sat, 12 Nov 2016 14:34:42 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id db79e544 for ; Sat, 12 Nov 2016 14:34:42 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 6ba92ba5 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Sat, 12 Nov 2016 14:34:41 +0000 (UTC) Received: by mail-lf0-f45.google.com with SMTP id o141so30807789lff.1 for ; Sat, 12 Nov 2016 06:37:02 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <20161111070445.GB10286@c3po> From: "Jason A. Donenfeld" Date: Sat, 12 Nov 2016 15:36:59 +0100 Message-ID: To: n3ph Content-Type: text/plain; charset=UTF-8 Cc: WireGuard mailing list Subject: Re: [WireGuard] OpenWRT/MIPS Improvements List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hey folks, Small update on the OOM issue. With LEDE devices that only have 32megs, if you run iperf3 on the device itself, eventually iperf3 will use tons of memory in trying to use different sized buffers, that the device will OOM and kill init. However, if you use packet forwarding and put iperf3 on a different device -- more closely resembling the actual workload of a router -- there is no OOM, and memory usage stays stable overtime, indicating there isn't a memory leak or anything of that nature in WireGuard. So, I think at this point WireGuard is quite stable on LEDE. Looking forward to hearing your feedback on the matter. Regards, Jason