diff options
| author | Liping Zhang <liping.zhang@spreadtrum.com> | 2016-09-22 22:28:51 +0800 |
|---|---|---|
| committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2016-09-25 14:54:02 +0200 |
| commit | d767ff2c84f19be1aa403762f34eebbb403caf6d (patch) | |
| tree | fd0b02f9d67749c6ada59b7db5558e92ed5fd604 /tools/perf/scripts/python/netdev-times.py | |
| parent | netfilter: seqadj: Fix the wrong ack adjust for the RST packet without ack (diff) | |
| download | linux-d767ff2c84f19be1aa403762f34eebbb403caf6d.tar.gz linux-d767ff2c84f19be1aa403762f34eebbb403caf6d.zip | |
netfilter: nft_ct: unnecessary to require dir when use ct l3proto/protocol
Currently, if the user want to match ct l3proto, we must specify the
direction, for example:
# nft add rule filter input ct original l3proto ipv4
^^^^^^^^
Otherwise, error message will be reported:
# nft add rule filter input ct l3proto ipv4
nft add rule filter input ct l3proto ipv4
<cmdline>:1:1-38: Error: Could not process rule: Invalid argument
add rule filter input ct l3proto ipv4
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Actually, there's no need to require NFTA_CT_DIRECTION attr, because
ct l3proto and protocol are unrelated to direction.
And for compatibility, even if the user specify the NFTA_CT_DIRECTION
attr, do not report error, just skip it.
Signed-off-by: Liping Zhang <liping.zhang@spreadtrum.com>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'tools/perf/scripts/python/netdev-times.py')
0 files changed, 0 insertions, 0 deletions