Skip to contentSkip to conversation

doc: document add chain device parameter

PATCH Applied Brennan Paciorek 2 participants 2 messages Aug 2, 2023 – Aug 3, 2023 netfilter

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 doc: document add chain device parameter

nft add chain lacked documentation of its optional device parameter, specifically what values the parameter accepted, what it did and when to use it.

---
 doc/nft.txt | 5 +++++
 1 file changed, 5 insertions(+)
doc/nft.txt +5 -0
index fe123d04..7e47ca39 100644
@@ -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
Signature · 1 line
2.41.0
maintainer Applied
#1 lore raw
Quoted 3 lines · Brennan Paciorek

nft add chain lacked documentation of its optional device parameter, specifically what values the parameter accepted, what it did and when to use it.

Applied, thanks