From: "Florian Franzeck" <fmfranzeck@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: System crash consistently after transferring around 280 Mbyte over Wireguard
Date: Thu, 27 Apr 2017 21:48:36 +0000 [thread overview]
Message-ID: <em2d98f94f-86e9-49a2-88de-5960b0aa5e13@fmf-laptop> (raw)
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Hi,
I compiled version 20170421 for my turris omnia running a modified
OpenWRT OS. I was really happy to see, how well wireguard performed
between my 2 routers compared to OpenVPN. But i consistently could
reproduce a relevant error: after transferring about 280Mbyte over the
wireguard VPN over a samba share, both my routers crash and restart. As
far as i can tell, there is no memory leak (1 router has 1Gbyte of RAM,
the other 2 Gbyte and they don't fill up during the process). Im not
sure what information i could post, as no logs are written or how to
debug this, but i'm more than happy to help out. I opened the
respective Ports on the firewall.
Configuration is pretty basic:
Router 1:
Interface]
ListenPort = 443
PrivateKey = xxx
[Peer]
PublicKey = xxx
Endpoint = xxx:443
AllowedIPs = 0.0.0.0/0,::/0
Router 2:
[Interface]
ListenPort = 443
PrivateKey = xx
[Peer]PublicKey = xxx
Endpoint = xxx:443
AllowedIPs = 0.0.0.0/0,::/0
I start the tunnel by these two scripts:
#!/bin/sh
ip link add dev tun1 type wireguard
ip addr add 10.1.3.1/32 peer 10.2.3.1 dev tun1
wg setconf tun1 /etc/wireguard/staticfmf/conf
ip link set tun1 up
route add -net 10.2.0.0 netmask 255.255.0.0 gw 10.1.3.1
#!/bin/sh
ip link add dev tun0 type wireguard
ip addr add 10.2.3.1/32 peer 10.1.3.1 dev tun0
wg setconf tun0 /etc/wireguard/staticheim/conf
ip link set tun0 up
route add -net 10.0.0.0 netmask 255.240.0.0 gw 10.2.3.1
Anyone able to help?
[-- Attachment #2: Type: text/html, Size: 1973 bytes --]
next reply other threads:[~2017-04-27 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 21:48 Florian Franzeck [this message]
2017-04-27 22:06 ` 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=em2d98f94f-86e9-49a2-88de-5960b0aa5e13@fmf-laptop \
--to=fmfranzeck@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).