diff options
| author | Christian Poessinger <christian@poessinger.com> | 2020-03-07 18:39:05 +0100 |
|---|---|---|
| committer | Christian Poessinger <christian@poessinger.com> | 2020-03-07 18:39:18 +0100 |
| commit | 4bd9bca4c0a5879c9f3c16b711f0cba258589827 (patch) | |
| tree | ca2dbdeb48810306e6d53b24990adb36b963398a | |
| parent | bf85fa8a306232cae4809da01a5e96a0c217612d (diff) | |
| download | vyos-documentation-4bd9bca4c0a5879c9f3c16b711f0cba258589827.tar.gz vyos-documentation-4bd9bca4c0a5879c9f3c16b711f0cba258589827.zip | |
vrf: add PPPoE to supported interfaces
| -rw-r--r-- | docs/vrf.rst | 12 |
1 files changed, 9 insertions, 3 deletions
diff --git a/docs/vrf.rst b/docs/vrf.rst index cf082484..139a3d93 100644 --- a/docs/vrf.rst +++ b/docs/vrf.rst @@ -10,6 +10,11 @@ VRFs, VRF-lite to be specific) in the Linux network stack. One use case is the multi-tenancy problem where each tenant has their own unique routing tables and in the very least need different default gateways. +.. warning:: VRFs are an "needs testing" feature. If you think things should be + different then they are implemented and handled right now - please feedback + via a task created in Phabricator_. + + Configuration ============= @@ -61,9 +66,9 @@ itself needs to be assigned to an interface. Assign bridge interface identified by `<interface>` to VRF named `<name>`. -.. warning:: VRFs are still experimental - thus they are only available to - certain interfaces types right now (``dummy, ethernet, bond, bridge``) to test - out the functionality. +.. cfgcmd:: set interfaces pppoe <interface> vrf <name> + + Assign PPPoE interface identified by `<interface>` to VRF named `<name>`. Routing ------- @@ -214,3 +219,4 @@ Operation C>* fe80::/64 is directly connected, dum1, 00:43:19 K>* ff00::/8 [0/256] is directly connected, dum1, 00:43:19 +.. include:: common-references.rst |