nft add chain lacked documentation of its optional device parameter, specifically what values the parameter accepted, what it did and when to use it. Closes: https://bugzilla.netfilter.org/show_bug.cgi?id=1093 Suggested-by: Phil Sutter <phil@xxxxxx> Signed-off-by: Brennan Paciorek <bpaciore@xxxxxxxxxx> --- doc/nft.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/nft.txt b/doc/nft.txt index fe123d04..7e47ca39 100644 --- a/doc/nft.txt +++ b/doc/nft.txt @@ -434,6 +434,11 @@ further quirks worth noticing: *prerouting*, *input*, *forward*, *output*, *postrouting* and this *ingress* hook. +The *device* parameter accepts a network interface name as a string, and is +required when adding a base chain that filters traffic on the ingress or +egress hooks. Any ingress or egress chains will only filter traffic from the +interface specified in the *device* parameter. + The *priority* parameter accepts a signed integer value or a standard priority name which specifies the order in which chains with the same *hook* value are traversed. The ordering is ascending, i.e. lower priority values have precedence -- 2.41.0
