Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Tom Yan <tom.ty89@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [PATCH] wg-quick: avoid traffics from momentarily leaking into the tunnel
Date: Fri, 17 Jun 2022 13:53:09 +0200	[thread overview]
Message-ID: <YqxrJRfTG+7WL16u@zx2c4.com> (raw)
In-Reply-To: <20220617113419.17329-1-tom.ty89@gmail.com>

On Fri, Jun 17, 2022 at 07:34:19PM +0800, Tom Yan wrote:
> The wireguard route table ip rule should stay as a NOP until the
> `suppress_prefixlength 0 table main` rule is in effect. Therefore,
> add the wireguard default route to its route table after the latter
> rule is added.
> 
> Signed-off-by: Tom Yan <tom.ty89@gmail.com>

Applied, thanks.

> ---
>  src/wg-quick/linux.bash | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/src/wg-quick/linux.bash b/src/wg-quick/linux.bash
> index e4d4c4f..69e5bef 100755
> --- a/src/wg-quick/linux.bash
> +++ b/src/wg-quick/linux.bash
> @@ -220,9 +220,9 @@ add_default() {
>  	fi
>  	local proto=-4 iptables=iptables pf=ip
>  	[[ $1 == *:* ]] && proto=-6 iptables=ip6tables pf=ip6
> -	cmd ip $proto route add "$1" dev "$INTERFACE" table $table
>  	cmd ip $proto rule add not fwmark $table table $table
>  	cmd ip $proto rule add table main suppress_prefixlength 0
> +	cmd ip $proto route add "$1" dev "$INTERFACE" table $table
>  
>  	local marker="-m comment --comment \"wg-quick(8) rule for $INTERFACE\"" restore=$'*raw\n' nftable="wg-quick-$INTERFACE" nftcmd 
>  	printf -v nftcmd '%sadd table %s %s\n' "$nftcmd" "$pf" "$nftable"
> -- 
> 2.36.1
> 

      reply	other threads:[~2022-06-17 11:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 11:34 Tom Yan
2022-06-17 11:53 ` Jason A. Donenfeld [this message]

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=YqxrJRfTG+7WL16u@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=tom.ty89@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).