diff options
author | Phil Sutter <phil@nwl.cc> | 2022-06-23 17:49:20 +0200 |
---|---|---|
committer | Florian Westphal <fw@strlen.de> | 2022-07-28 09:45:11 +0200 |
commit | 446e76dbde713327358f17a8af6ce86b8541c836 (patch) | |
tree | 0617eccd45bae71a02a9e7e7255d99b3ef60f077 | |
parent | a2ddb38f7eb818312c50be78028bc35145c039ae (diff) |
doc: Document limitations of ipsec expression with xfrm_interface
Point at a possible solution to match IPsec info of locally generated
traffic routed to an xfrm-type interface.
Signed-off-by: Phil Sutter <phil@nwl.cc>
Signed-off-by: Florian Westphal <fw@strlen.de>
-rw-r--r-- | doc/primary-expression.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/primary-expression.txt b/doc/primary-expression.txt index f97778b9..4d6b0878 100644 --- a/doc/primary-expression.txt +++ b/doc/primary-expression.txt @@ -428,6 +428,10 @@ Destination address of the tunnel| ipv4_addr/ipv6_addr |================================= +*Note:* When using xfrm_interface, this expression is not useable in output +hook as the plain packet does not traverse it with IPsec info attached - use a +chain in postrouting hook instead. + NUMGEN EXPRESSION ~~~~~~~~~~~~~~~~~ |