From: Pablo Neira Ayuso Date: Sat, 29 Dec 2018 00:23:11 +0000 (+0100) Subject: doc: refer to meta protocol in icmp and icmpv6 X-Git-Tag: v0.9.1~162 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=fd09b75624c36a8b29fdb224287994edcaf441bc;p=thirdparty%2Fnftables.git doc: refer to meta protocol in icmp and icmpv6 Instead of meta nftproto, which is a typo. Signed-off-by: Pablo Neira Ayuso --- diff --git a/doc/payload-expression.txt b/doc/payload-expression.txt index eb98e5d7..e1a10252 100644 --- a/doc/payload-expression.txt +++ b/doc/payload-expression.txt @@ -122,7 +122,7 @@ ICMP HEADER EXPRESSION This expression refers to ICMP header fields. When using it in *inet*, *bridge* or *netdev* families, it will cause an implicit dependency on IPv4 to be created. To match on unusual cases like ICMP over IPv6, one has to add an -explicit *meta nftproto ipv6* match to the rule. +explicit *meta protocol ip6* match to the rule. .ICMP header expression [options="header"] @@ -207,7 +207,7 @@ ICMPV6 HEADER EXPRESSION This expression refers to ICMPv6 header fields. When using it in *inet*, *bridge* or *netdev* families, it will cause an implicit dependency on IPv6 to be created. To match on unusual cases like ICMPv6 over IPv4, one has to add an -explicit *meta nftproto ipv4* match to the rule. +explicit *meta protocol ip* match to the rule. .ICMPv6 header expression [options="header"]