From 26589362c1a3a7c3f0fdb5e70e831bcb4077b0d1 Mon Sep 17 00:00:00 2001 From: Florian Westphal Date: Fri, 29 Sep 2017 13:54:21 +0200 Subject: doc: update man page you can now use "rt ip|ip6 nexthop" and "ct original|reply ip|ip6 saddr|daddr" to tell nft if you want to match ipv4 or ipv6. Signed-off-by: Florian Westphal --- doc/nft.xml | 23 ++++++++++++++++++----- 1 file changed, 18 insertions(+), 5 deletions(-) diff --git a/doc/nft.xml b/doc/nft.xml index 9d97a782..c0f42ddc 100644 --- a/doc/nft.xml +++ b/doc/nft.xml @@ -608,7 +608,6 @@ filter input iif $int_ifs accept hybrid IPv4/IPv6 tables. The meta expression nfproto keyword can be used to test which family (ipv4 or ipv6) context the packet is being processed in. - When no address family is specified, ip is used by default. @@ -2905,8 +2904,8 @@ filter output rt classid 10 # IP family dependent rt expressions ip filter output rt nexthop 192.168.0.1 ip6 filter output rt nexthop fd00::1 -inet filter meta nfproto ipv4 output rt nexthop 192.168.0.1 -inet filter meta nfproto ipv6 output rt nexthop fd00::1 +inet filter output rt ip nexthop 192.168.0.1 +inet filter output rt ip6 nexthop fd00::1 @@ -4025,8 +4024,6 @@ ip6 filter input frag more-fragments 1 counter l3proto protocol - saddr - daddr proto-src proto-dst bytes @@ -4035,6 +4032,22 @@ ip6 filter input frag more-fragments 1 counter zone + + ct + + original + reply + + + ip + ip6 + + + saddr + daddr + + + -- cgit v1.2.3