From: Phil Sutter <phil@nwl.cc>
To: Stephen Suryaputra <ssuryaextr@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nftables v4] exthdr: doc: add support for matching IPv4 options
Date: Thu, 4 Jul 2019 18:14:15 +0200 [thread overview]
Message-ID: <20190704161415.GP9218@orbyte.nwl.cc> (raw)
In-Reply-To: <20190704003052.469-1-ssuryaextr@gmail.com>
Hi,
On Wed, Jul 03, 2019 at 08:30:52PM -0400, Stephen Suryaputra wrote:
> This is the userspace change for the overall changes with this
> description:
> Add capability to have rules matching IPv4 options. This is developed
> mainly to support dropping of IP packets with loose and/or strict source
> route route options.
I would have split the netlink debug output change adjustments (the
majority of changes in tests/py) into a separate patch to ease reviews.
Apart from that:
Acked-by: Phil Sutter <phil@nwl.cc>
Thanks, Phil
next prev parent reply other threads:[~2019-07-04 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 0:30 [PATCH nftables v4] exthdr: doc: add support for matching IPv4 options Stephen Suryaputra
2019-07-04 12:33 ` Pablo Neira Ayuso
2019-07-04 16:14 ` Phil Sutter [this message]
2019-07-04 16:53 ` Phil Sutter
2019-07-04 18:05 ` Pablo Neira Ayuso
2019-07-04 18:11 ` 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=20190704161415.GP9218@orbyte.nwl.cc \
--to=phil@nwl.cc \
--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;
as well as URLs for NNTP newsgroup(s).