[nft] nft.8: Document limitation of reject statement in bridge family

Message ID 20180515153430.3174-1-phil@nwl.cc
State Accepted
Delegated to: Pablo Neira
Headers show
Series
  • [nft] nft.8: Document limitation of reject statement in bridge family
Related show

Commit Message

Phil Sutter May 15, 2018, 3:34 p.m.
Bridge family allows reject statement in prerouting and input chains
only. Users can't know without looking at kernel code.

Signed-off-by: Phil Sutter <phil@nwl.cc>
---
 doc/nft.xml | 4 ++++
 1 file changed, 4 insertions(+)

Comments

Florian Westphal May 17, 2018, 3:09 p.m. | #1
Phil Sutter <phil@nwl.cc> wrote:
> Bridge family allows reject statement in prerouting and input chains
> only. Users can't know without looking at kernel code.

Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Patch

diff --git a/doc/nft.xml b/doc/nft.xml
index 05193e67ed6dc..cd6c012ff1b6d 100644
--- a/doc/nft.xml
+++ b/doc/nft.xml
@@ -4873,6 +4873,10 @@  ip6 filter output log flags all
 				The common default reject value is
 				<command>port-unreachable</command>.
 			</para>
+			<para>
+				Note that in bridge family, reject statement is only allowed in base chains which
+				hook into <literal>input</literal> or <literal>prerouting</literal>.
+			</para>
 		</refsect2>
 		<refsect2>
 			<title>Counter statement</title>