From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: wenxu@ucloud.cn
Cc: dsahern@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] tc: flower: add tc conntrack inv ct_state support
Date: Tue, 19 Jan 2021 17:08:46 -0300 [thread overview]
Message-ID: <20210119200846.GB3961@horizon.localdomain> (raw)
In-Reply-To: <1611045299-764-1-git-send-email-wenxu@ucloud.cn>
On Tue, Jan 19, 2021 at 04:34:59PM +0800, wenxu@ucloud.cn wrote:
> --- a/man/man8/tc-flower.8
> +++ b/man/man8/tc-flower.8
> @@ -387,6 +387,8 @@ new - New connection.
> .TP
> est - Established connection.
> .TP
> +inv - The packet is associated with no known connection.
This is not accurate. Please write it after OVS' description of it, on
ovs-fields.7 (not saying to copy it):
inv (0x10)
The state is invalid, meaning that the connection tracker couldn’t iden‐
tify the connection. This flag is a catch-all for problems in the connec‐
tion or the connection tracker, such as:
• L3/L4 protocol handler is not loaded/unavailable. With the Linux
kernel datapath, this may mean that the nf_conntrack_ipv4 or
nf_conntrack_ipv6 modules are not loaded.
• L3/L4 protocol handler determines that the packet is malformed.
• Packets are unexpected length for protocol.
Something like: The packet couldn't be associated to a connection.
> +.TP
> Example: +trk+est
> .RE
> .TP
Thanks,
Marcelo
prev parent reply other threads:[~2021-01-19 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 8:34 [PATCH iproute2-next] tc: flower: add tc conntrack inv ct_state support wenxu
2021-01-19 20:08 ` Marcelo Ricardo Leitner [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=20210119200846.GB3961@horizon.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=wenxu@ucloud.cn \
/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