From: Andreas Rammhold <andreas@rammhold.de>
Date: Tue, 26 Sep 2017 23:54:20 +0000 (+0200)
Subject: man/systemd.network: Updated documentation about VRF traffic redirection
X-Git-Tag: v235~48^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F6924%2Fhead;p=thirdparty%2Fsystemd.git

man/systemd.network: Updated documentation about VRF traffic redirection

Starting with kernel version 4.8 the kernel has a single `l3mdev` rule
that handles this. This rule will be created when the first VRF device
is added.
---

diff --git a/man/systemd.network.xml b/man/systemd.network.xml
index 1b07f2a1a33..6325a70369a 100644
--- a/man/systemd.network.xml
+++ b/man/systemd.network.xml
@@ -1756,8 +1756,9 @@ Bond=bond1
       <title>Virtual Routing and Forwarding (VRF)</title>
       <para>Add the <literal>bond1</literal> interface to the VRF master interface
       <literal>vrf1</literal>. This will redirect routes generated on this interface to be
-      within the routing table defined during VRF creation. Traffic won't be redirected
-      towards the VRFs routing table unless specific ip-rules are added.</para>
+      within the routing table defined during VRF creation. For kernels before 4.8 traffic
+      won't be redirected towards the VRFs routing table unless specific ip-rules are added.
+      </para>
       <programlisting># /etc/systemd/network/25-vrf.network
 [Match]
 Name=bond1