From: Phil Sutter Date: Wed, 24 Apr 2024 21:48:56 +0000 (+0200) Subject: doc: nft.8: Highlight "hook" in flowtable description X-Git-Tag: v1.0.6.1~210 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b448e8ed3dcfd03c2ba3d49f9b513b4f8940fb0b;p=thirdparty%2Fnftables.git doc: nft.8: Highlight "hook" in flowtable description commit 9da7b00aa886012c0e59e73aa19e05a8d1568540 upstream. Lacking an explicit description of possible hook values, emphasising the word in the description text should draw readers' attention in the right direction. Signed-off-by: Phil Sutter --- diff --git a/doc/nft.txt b/doc/nft.txt index eb8df1d9..7a99f65b 100644 --- a/doc/nft.txt +++ b/doc/nft.txt @@ -702,8 +702,8 @@ protocols. Each entry also caches the destination interface and the gateway address - to update the destination link-layer address - to forward packets. The ttl and hoplimit fields are also decremented. Hence, flowtables provides an alternative path that allow packets to bypass the classic forwarding path. -Flowtables reside in the ingress hook that is located before the prerouting -hook. You can select which flows you want to offload through the flow +Flowtables reside in the ingress *hook* that is located before the prerouting +*hook*. You can select which flows you want to offload through the flow expression from the forward chain. Flowtables are identified by their address family and their name. The address family must be one of ip, ip6, or inet. The inet address family is a dummy family which is used to create hybrid IPv4/IPv6