summaryrefslogtreecommitdiff
path: root/docs/configuration/interfaces
diff options
context:
space:
mode:
Diffstat (limited to 'docs/configuration/interfaces')
-rw-r--r--docs/configuration/interfaces/openvpn.rst6
-rw-r--r--docs/configuration/interfaces/pppoe.rst4
-rw-r--r--docs/configuration/interfaces/wireguard.rst4
3 files changed, 7 insertions, 7 deletions
diff --git a/docs/configuration/interfaces/openvpn.rst b/docs/configuration/interfaces/openvpn.rst
index 2c273b34..8b32743f 100644
--- a/docs/configuration/interfaces/openvpn.rst
+++ b/docs/configuration/interfaces/openvpn.rst
@@ -159,13 +159,13 @@ Local Configuration:
.. code-block:: none
- set protocols static interface-route 10.1.0.0/16 next-hop-interface vtun1
+ set protocols static route 10.1.0.0/16 interface vtun1
Remote Configuration:
.. code-block:: none
- set protocols static interface-route 10.0.0.0/16 next-hop-interface vtun1
+ set protocols static route 10.0.0.0/16 interface vtun1
Firewall policy can also be applied to the tunnel interface for `local`, `in`,
and `out` directions and function identically to ethernet interfaces.
@@ -253,7 +253,7 @@ internally, so we need to create a route to the 10.23.0.0/20 network ourselves:
.. code-block:: none
- set protocols static interface-route 10.23.0.0/20 next-hop-interface vtun10
+ set protocols static route 10.23.0.0/20 interface vtun10
Generate X.509 Certificate and Keys
-----------------------------------
diff --git a/docs/configuration/interfaces/pppoe.rst b/docs/configuration/interfaces/pppoe.rst
index 0fdbba42..1bbccc0c 100644
--- a/docs/configuration/interfaces/pppoe.rst
+++ b/docs/configuration/interfaces/pppoe.rst
@@ -130,7 +130,7 @@ PPPoE options
.. note:: In all modes except 'none', all default routes using this interface
will be removed when the interface is torn down - even manually installed
- static interface-routes.
+ static routes.
.. cfgcmd:: set interfaces pppoe <interface> idle-timeout <time>
@@ -251,7 +251,7 @@ Requirements:
default gateway you receive from your DSL ISP to the routing table if you
have no other WAN connections. If you wish to use a dual WAN connection,
change the ``default-route`` option to ``force``. You could also install
- a static interface-route and set the ``default-route`` option to ``none``.
+ a static route and set the ``default-route`` option to ``none``.
* With the ``name-server`` option set to ``none``, VyOS will ignore the
nameservers your ISP sens you and thus you can fully rely on the ones you
have configured statically.
diff --git a/docs/configuration/interfaces/wireguard.rst b/docs/configuration/interfaces/wireguard.rst
index c4dfbee7..852ff520 100644
--- a/docs/configuration/interfaces/wireguard.rst
+++ b/docs/configuration/interfaces/wireguard.rst
@@ -78,7 +78,7 @@ one.
set interfaces wireguard wg01 peer to-wg02 port '12345'
set interfaces wireguard wg01 peer to-wg02 pubkey 'XMrlPykaxhdAAiSjhtPlvi30NVkvLQliQuKP7AI7CyI='
set interfaces wireguard wg01 port '12345'
- set protocols static interface-route 10.2.0.0/24 next-hop-interface wg01
+ set protocols static route 10.2.0.0/24 interface wg01
The last step is to define an interface route for 10.2.0.0/24 to get
through the WireGuard interface `wg01`. Multiple IPs or networks can be
@@ -113,7 +113,7 @@ the public key, which needs to be shared with the peer.
set interfaces wireguard wg01 peer to-wg02 port '12345'
set interfaces wireguard wg01 peer to-wg02 pubkey 'u41jO3OF73Gq1WARMMFG7tOfk7+r8o8AzPxJ1FZRhzk='
set interfaces wireguard wg01 port '12345'
- set protocols static interface-route 10.1.0.0/24 next-hop-interface wg01
+ set protocols static route 10.1.0.0/24 interface wg01
Assure that your firewall rules allow the traffic, in which case you
have a working VPN using WireGuard