From: Wei Chen <weichen302@zoho.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Iptables WireGuard obfuscation extension
Date: Sun, 2 Oct 2022 18:13:22 -0500 [thread overview]
Message-ID: <YzobElsJwblnVzI2@tungsten> (raw)
In-Reply-To: <20220928163356.183baef9@nvm>
Hi Roman,
> The "Usage" section speaks of "server" and "client". However in the WG world
> there's not really a server or client per se, but all WG network members are
> peers. As such, is it possible to propose an universal set of iptables rules
> that would be fine to use on any network node?
>
> As I understand, all INPUT packets to our local --dport need to be --unobfs,
> and all OUTPUT packets from us to any other node need to be --obfs. Right?
>
Yes, you are right. Besides unobfs/obfs INPUT/OUTPUT chain for a local
WG installation, one can also use it on a Linux gateway, mangle the
FORWARD chain. I haven't test it but it should work.
Wei
next prev parent reply other threads:[~2022-10-02 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 11:34 Iptables WireGuard obfuscation extension Wei Chen
2022-09-28 11:33 ` Roman Mamedov
2022-10-02 23:13 ` Wei Chen [this message]
2022-09-28 16:35 ` Jason A. Donenfeld
2022-09-28 18:17 ` Jean-Philippe Aumasson
2022-10-02 23:35 ` Wei Chen
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=YzobElsJwblnVzI2@tungsten \
--to=weichen302@zoho.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.