From: Florian Westphal <fw@strlen.de>
To: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Cc: netfilter-devel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>,
Shivani Bhardwaj <shivanib134@gmail.com>,
Max Laverse <max@laverse.net>,
kernel@openvz.org
Subject: Re: [PATCH iptables] ip6tables: masquerade: use fully-random so that nft can understand the rule
Date: Wed, 4 Aug 2021 17:57:45 +0200 [thread overview]
Message-ID: <20210804155745.GF607@breakpoint.cc> (raw)
In-Reply-To: <20210804155057.16829-1-ptikhomirov@virtuozzo.com>
Pavel Tikhomirov <ptikhomirov@virtuozzo.com> wrote:
> That's because nft list ruleset saves "random-fully" which is wrong
> format for nft -f, right should be "fully-random".
Right. Patch is applied, thanks!
prev parent reply other threads:[~2021-08-04 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 15:50 [PATCH iptables] ip6tables: masquerade: use fully-random so that nft can understand the rule Pavel Tikhomirov
2021-08-04 15:57 ` Florian Westphal [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=20210804155745.GF607@breakpoint.cc \
--to=fw@strlen.de \
--cc=kernel@openvz.org \
--cc=max@laverse.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=shivanib134@gmail.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).