Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Derrick Lyndon Pallas <derrick@pallas.us>
To: wireguard@lists.zx2c4.com
Subject: Re: WireGuard over WireGuard
Date: Wed, 6 May 2020 10:54:42 -0700	[thread overview]
Message-ID: <71c12e22-c7b6-9753-cc44-aac0f51592ff@pallas.us> (raw)
In-Reply-To: <CAKmhVkoE_fL59VJqqXoGHX_S3E9+h=KwyNchWSBrEfPHrpNyoQ@mail.gmail.com>

Have you checked your MTUs? ~Derrick


On 5/6/20 9:57 AM, Mo Balaa wrote:
> We are running WireGuard over WireGuard. It appears to work well;
> however I am noticing some applications struggle to work reliably.
> Lots of failed page loadss / timeouts. Any pointers on how I could go
> about debugging these issues?
>
> Any general pointers on running WireGuard over WireGuard? One note
> about my deployment is that it uses socat to transparently proxy the
> inner tunnel between devices.
>
> The setup looks something like this:
> tunnel 1 (iOS) -> socat -> tunnel 0 -> Linux (tunnel 0) -> (tunnel 1)
>
> Thanks for the feedback.

  reply	other threads:[~2020-05-06 17:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 16:57 Mo Balaa
2020-05-06 17:54 ` Derrick Lyndon Pallas [this message]
2020-05-06 21:37   ` Mo Balaa
2020-05-06 22:00     ` Jason A. Donenfeld
2020-05-06 22:24       ` Justin Kilpatrick
2020-05-06 22:25         ` Jason A. Donenfeld
2020-05-06 23:28           ` John Lauro
2020-05-06 23:54             ` Jason A. Donenfeld
2020-05-07  0:57               ` Derrick Lyndon Pallas
2020-05-12  6:56                 ` Dimitar Vassilev
2020-05-12 11:14                   ` Justin Kilpatrick
2020-05-31 19:34                     ` Mo Balaa

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=71c12e22-c7b6-9753-cc44-aac0f51592ff@pallas.us \
    --to=derrick@pallas.us \
    --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).