Blame SOURCES/0016-doc-nft.8-Mention-wildcard-interface-matching.patch

f1d1c0
From d58192a8d2810271d5c6525dc66ba1e1ec3fd2b7 Mon Sep 17 00:00:00 2001
f1d1c0
From: Phil Sutter <psutter@redhat.com>
f1d1c0
Date: Wed, 12 Feb 2020 22:39:44 +0100
f1d1c0
Subject: [PATCH] doc: nft.8: Mention wildcard interface matching
f1d1c0
f1d1c0
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1763652
f1d1c0
Upstream Status: nftables commit 03d45ad330a25
f1d1c0
f1d1c0
commit 03d45ad330a25323610648bb05f550e0fb9d65b2
f1d1c0
Author: Phil Sutter <phil@nwl.cc>
f1d1c0
Date:   Thu Feb 6 12:24:51 2020 +0100
f1d1c0
f1d1c0
    doc: nft.8: Mention wildcard interface matching
f1d1c0
f1d1c0
    Special meaning of asterisk in interface names wasn't described
f1d1c0
    anywhere.
f1d1c0
f1d1c0
    Signed-off-by: Phil Sutter <phil@nwl.cc>
f1d1c0
---
f1d1c0
 doc/primary-expression.txt | 7 +++++++
f1d1c0
 1 file changed, 7 insertions(+)
f1d1c0
f1d1c0
diff --git a/doc/primary-expression.txt b/doc/primary-expression.txt
f1d1c0
index 5473d59..a5cab9d 100644
f1d1c0
--- a/doc/primary-expression.txt
f1d1c0
+++ b/doc/primary-expression.txt
f1d1c0
@@ -36,6 +36,13 @@ add such a rule, it will stop matching if the interface gets renamed and it
f1d1c0
 will match again in case interface gets deleted and later a new interface
f1d1c0
 with the same name is created.
f1d1c0
 
f1d1c0
+Like with iptables, wildcard matching on interface name prefixes is available for
f1d1c0
+*iifname* and *oifname* matches by appending an asterisk (*) character. Note
f1d1c0
+however that unlike iptables, nftables does not accept interface names
f1d1c0
+consisting of the wildcard character only - users are supposed to just skip
f1d1c0
+those always matching expressions. In order to match on literal asterisk
f1d1c0
+character, one may escape it using backslash (\).
f1d1c0
+
f1d1c0
 .Meta expression types
f1d1c0
 [options="header"]
f1d1c0
 |==================
f1d1c0
-- 
f1d1c0
1.8.3.1
f1d1c0