]> git.ipfire.org Git - thirdparty/systemd.git/commitdiff
man/systemd.network: Updated documentation about VRF traffic redirection 6924/head
authorAndreas Rammhold <andreas@rammhold.de>
Tue, 26 Sep 2017 23:54:20 +0000 (01:54 +0200)
committerAndreas Rammhold <andreas@rammhold.de>
Wed, 27 Sep 2017 18:02:15 +0000 (20:02 +0200)
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.

man/systemd.network.xml

index 1b07f2a1a33b0d31d7f428215445fe6dfc00699c..6325a70369a5379025e88492dd8960a3c342c807 100644 (file)
@@ -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