From: Stefano Brivio <sbrivio@redhat.com>
To: Balazs Scheidler <bazsi77@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nftables 2/4] doc: added documentation on "socket wildcard"
Date: Sat, 22 Aug 2020 11:17:52 +0200 [thread overview]
Message-ID: <20200822111752.5da28997@elisabeth> (raw)
In-Reply-To: <20200822062203.3617-3-bazsi77@gmail.com>
On Sat, 22 Aug 2020 08:22:01 +0200
Balazs Scheidler <bazsi77@gmail.com> wrote:
> @@ -209,15 +209,20 @@ or non-zero bound listening socket (possibly with a non-local address).
> Value of the IP_TRANSPARENT socket option in the found socket. It can be 0 or 1.|
> boolean (1 bit)
> |mark| Value of the socket mark (SOL_SOCKET, SO_MARK). | mark
> +|wildcard|
> +Indicates weather the socket is wildcard-bound (e.g. 0.0.0.0 or ::0). |
s/weather/whether/.
> +boolean (1 bit)
> |==================
>
> .Using socket expression
> ------------------------
> -# Mark packets that correspond to a transparent socket
> +# Mark packets that correspond to a transparent socket. "socket wildcard 0"
> +# means that zero bound listener sockets are NOT matched (which is usually
"zero-bound" would be a bit clearer (and consistent with the rest).
--
Stefano
next prev parent reply other threads:[~2020-08-22 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 6:21 [PATCH nftables 0/4] socket: add support for "wildcard" key Balazs Scheidler
2020-08-22 6:22 ` [PATCH nftables 1/4] " Balazs Scheidler
2020-08-22 9:23 ` Stefano Brivio
2020-08-28 16:20 ` Pablo Neira Ayuso
2020-08-22 6:22 ` [PATCH nftables 2/4] doc: added documentation on "socket wildcard" Balazs Scheidler
2020-08-22 9:17 ` Stefano Brivio [this message]
2020-08-22 6:22 ` [PATCH nftables 3/4] tests: added "socked wildcard" testcases Balazs Scheidler
2020-08-22 9:16 ` Stefano Brivio
2020-08-22 6:22 ` [PATCH nftables 4/4] tests: allow tests to use a custom nft executable Balazs Scheidler
2020-08-22 9:15 ` Stefano Brivio
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=20200822111752.5da28997@elisabeth \
--to=sbrivio@redhat.com \
--cc=bazsi77@gmail.com \
--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).