From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Fernando Fernandez Mancera <ffmancera@riseup.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft v2] src: introduce SYNPROXY matching
Date: Wed, 17 Jul 2019 10:21:49 +0200 [thread overview]
Message-ID: <20190717082149.a2k7pdqvjushamf6@salvia> (raw)
In-Reply-To: <20190622171207.818-1-ffmancera@riseup.net>
On Sat, Jun 22, 2019 at 07:12:08PM +0200, Fernando Fernandez Mancera wrote:
> Add support for "synproxy" statement.
Applied, thanks Fernando.
nft-test.py -j
shows this:
ERROR: did not find JSON equivalent for rule 'synproxy mss 1460 wscale 5 timestamp sack-perm'
py/inet/synproxy.t.json.got:
WARNING: line 2: Wrote JSON equivalent for rule synproxy mss 1460 wscale 5 timestamp sack-perm
ERROR: did not find JSON equivalent for rule 'synproxy sack-perm'
py/inet/synproxy.t.json.got: WARNING: line 2: Wrote JSON equivalent for rule synproxy sack-perm
please, follow up to fix this. Thanks.
prev parent reply other threads:[~2019-07-17 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 17:12 [PATCH nft v2] src: introduce SYNPROXY matching Fernando Fernandez Mancera
2019-07-17 8:21 ` 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=20190717082149.a2k7pdqvjushamf6@salvia \
--to=pablo@netfilter.org \
--cc=ffmancera@riseup.net \
--cc=netfilter-devel@vger.kernel.org \
/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).