From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] extensions: libip6t_hl: Add translation to nft
Date: Mon, 11 Jan 2016 19:59:12 +0100 [thread overview]
Message-ID: <20160111185912.GB15830@salvia> (raw)
In-Reply-To: <20160107093924.GA6686@gmail.com>
On Thu, Jan 07, 2016 at 03:09:24PM +0530, Shivani Bhardwaj wrote:
> Add translation for hop limit to nftables.
>
> Examples:
>
> $ sudo ip6tables-translate -t nat -A postrouting -m hl --hl-gt 3
> nft add rule ip6 nat postrouting ip6 hoplimit gt 3 counter
>
> $ sudo ip6tables-translate -t nat -A postrouting -m hl ! --hl-eq 3
> nft add rule ip6 nat postrouting ip6 hoplimit != 3 counter
>
> Signed-off-by: Shivani Bhardwaj <shivanib134@gmail.com>
> ---
> extensions/libip6t_hl.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/extensions/libip6t_hl.c b/extensions/libip6t_hl.c
> index 3559db4..0e13df1 100644
> --- a/extensions/libip6t_hl.c
> +++ b/extensions/libip6t_hl.c
> @@ -97,6 +97,23 @@ static const struct xt_option_entry hl_opts[] = {
> };
> #undef s
>
> +static int hl_xlate(const struct xt_entry_match *match,
> + struct xt_buf *buf, int numeric)
> +{
> + static const char *const op[] = {
> + [IP6T_HL_EQ] = "ip6 hoplimit",
> + [IP6T_HL_NE] = "ip6 hoplimit !=",
> + [IP6T_HL_LT] = "ip6 hoplimit lt",
> + [IP6T_HL_GT] = "ip6 hoplimit gt" };
I'd suggest you use something like:
static const char *const op[] = {
[IP6T_HL_EQ] = "",
[IP6T_HL_NE] = "!=",
[IP6T_HL_LT] = "lt",
[IP6T_HL_GT] = "gt"
};
We can later on consolidate this code by providing a common function
from libxtables for everyone.
Thanks.
prev parent reply other threads:[~2016-01-11 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 9:39 [PATCH] extensions: libip6t_hl: Add translation to nft Shivani Bhardwaj
2016-01-11 18:59 ` Pablo Neira Ayuso [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=20160111185912.GB15830@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--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).