From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Ivan Leonardo <ivan.leonardo@nickmaleao.stream>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: TCP traffic in ipip tunnel inside wireguard connection
Date: Mon, 29 May 2017 23:02:16 +0200 [thread overview]
Message-ID: <CAHmME9p5eZ9gv0rE_cre82Jw+FjOorz0dU+AdUQS1VcqiU0+8g@mail.gmail.com> (raw)
In-Reply-To: <3aee46648bd2d8c49fd13e1fd140d3d3@nickmaleao.stream>
Hi Ivan,
I'll try to reproduce in order to determine whether or not there's a
checksum bug with nested tunnels. However, all of this seems quite
unnecessary:
Just set allowed-ips to be your /30 for each peer. If you need one to
be 0.0.0.0/0 at one time or another, you can change these at runtime.
Alternatively, if you _must_ have multiple 0.0.0.0/0 just use two
different wireguard interfaces running on different UDP ports, and
then you'll have the full power of the ordinary linux routing table
for this sort of craziness.
Jason
next prev parent reply other threads:[~2017-05-29 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 20:57 Ivan Leonardo
2017-05-29 21:02 ` Jason A. Donenfeld [this message]
2017-06-06 20:49 ` Jörg Thalheim
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=CAHmME9p5eZ9gv0rE_cre82Jw+FjOorz0dU+AdUQS1VcqiU0+8g@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=ivan.leonardo@nickmaleao.stream \
--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).