From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Stephen Suryaputra <ssuryaextr@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH libnftnl v2] src: libnftnl: add support for matching IPv4 options
Date: Fri, 21 Jun 2019 18:06:53 +0200 [thread overview]
Message-ID: <20190621160653.ektgcsz2oo47etsh@salvia> (raw)
In-Reply-To: <20190620115429.3678-1-ssuryaextr@gmail.com>
On Thu, Jun 20, 2019 at 07:54:29AM -0400, Stephen Suryaputra wrote:
[...]
> diff --git a/src/expr/exthdr.c b/src/expr/exthdr.c
> index bef453e..e5f714b 100644
> --- a/src/expr/exthdr.c
> +++ b/src/expr/exthdr.c
> @@ -200,6 +200,9 @@ static const char *op2str(uint8_t op)
> case NFT_EXTHDR_OP_TCPOPT:
> return " tcpopt";
> case NFT_EXTHDR_OP_IPV6:
> + return " ipv6";
> + case NFT_EXTHDR_OP_IPV4:
> + return " ipv4";
> default:
> return "";
> }
Would you mind to install libnftnl with this patch on top and run:
nftables/tests/py/# python nft-tests.py
to check if this breaks testcases, if so a patch to update tests in
nftables would be great too.
Thanks!
> @@ -209,6 +212,8 @@ static inline int str2exthdr_op(const char* str)
> {
> if (!strcmp(str, "tcpopt"))
> return NFT_EXTHDR_OP_TCPOPT;
> + if (!strcmp(str, "ipv4"))
> + return NFT_EXTHDR_OP_IPV4;
>
> /* if str == "ipv6" or anything else */
> return NFT_EXTHDR_OP_IPV6;
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-06-21 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 11:54 [PATCH libnftnl v2] src: libnftnl: add support for matching IPv4 options Stephen Suryaputra
2019-06-21 16:06 ` Pablo Neira Ayuso [this message]
2019-06-24 18:25 ` Stephen Suryaputra
2019-07-04 12:32 ` Pablo Neira Ayuso
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=20190621160653.ektgcsz2oo47etsh@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ssuryaextr@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