From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Bruno Wolff III <bruno@wolff.to>
Cc: Roman Mamedov <rm@romanrm.net>,
Nico Schottelius <nico.schottelius@ungleich.ch>,
el3xyz <el3xyz@protonmail.com>,
wireguard@lists.zx2c4.com
Subject: Re: WireGuard with obfuscation support
Date: Mon, 27 Sep 2021 09:01:38 -0400 [thread overview]
Message-ID: <20210927130138.54zkvlokogcu6o3q@meerkat.local> (raw)
In-Reply-To: <20210927102157.GA23755@wolff.to>
On Mon, Sep 27, 2021 at 05:21:57AM -0500, Bruno Wolff III wrote:
> > With obfuscation there would be UDP packets of random junk, and it would be a
> > much harder job to come up with a rule to drop those without affecting
> > anything else.
>
> If your ISP is blocking your Wireguard traffic call them up and complain.
There have been times when I found myself briefly at a location that didn't
allow wireguard traffic, like an airport or a public library. Complaining
wouldn't have been a useful course of action to take, since I needed a
solution at that particular time and place.
-K
next prev parent reply other threads:[~2021-09-27 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 12:09 el3xyz
2021-09-27 0:53 ` Nico Schottelius
2021-09-27 7:11 ` Bruno Wolff III
2021-09-27 7:34 ` Roman Mamedov
2021-09-27 9:14 ` Bruno Wolff III
2021-09-27 9:36 ` Roman Mamedov
2021-09-27 10:21 ` Bruno Wolff III
2021-09-27 13:01 ` Konstantin Ryabitsev [this message]
2021-09-27 13:48 ` Lonnie Abelbeck
2021-09-27 15:28 ` StarBrilliant
2021-09-27 15:59 ` Nico Schottelius
2021-09-27 16:37 ` StarBrilliant
2021-09-27 7:44 ` Nico Schottelius
2021-09-27 8:17 ` Fredrik Strömberg
2021-09-27 16:21 ` 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=20210927130138.54zkvlokogcu6o3q@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=bruno@wolff.to \
--cc=el3xyz@protonmail.com \
--cc=nico.schottelius@ungleich.ch \
--cc=rm@romanrm.net \
--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).