diff options
| author | Eshenko Dmitriy <snooppy@mail.ua> | 2019-07-28 11:12:17 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-07-28 11:12:17 +0300 |
| commit | d058ea377967ad1b93f52c9d495d943cabf265dc (patch) | |
| tree | 7fcb8a7729acc5402c7980e9a4740548f3b0a699 /docs/services/ipoe-server.rst | |
| parent | e41ff1585c50dabec16fa1b81a4eb611df3717d9 (diff) | |
| download | vyos-documentation-d058ea377967ad1b93f52c9d495d943cabf265dc.tar.gz vyos-documentation-d058ea377967ad1b93f52c9d495d943cabf265dc.zip | |
Fix typos
Diffstat (limited to 'docs/services/ipoe-server.rst')
| -rw-r--r-- | docs/services/ipoe-server.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/services/ipoe-server.rst b/docs/services/ipoe-server.rst index 633de880..925ef373 100644 --- a/docs/services/ipoe-server.rst +++ b/docs/services/ipoe-server.rst @@ -14,7 +14,7 @@ Configuration IPoE can be configure on different interfaces, it will depend on each specific situation which interface will provide IPoE to clients. The clients mac address and the incoming interface is being used as control parameter, to authenticate a client. -The example comnfiguration below will assign an IP to the client on the incoming interface eth2 with the client mac address 08:00:27:2f:d8:06. +The example configuration below will assign an IP to the client on the incoming interface eth2 with the client mac address 08:00:27:2f:d8:06. Other DHCP discovery requests will be ignored, unless the client mac has been enabled in the configuration. .. code-block:: sh @@ -26,7 +26,7 @@ Other DHCP discovery requests will be ignored, unless the client mac has been en set service ipoe-server interface eth2 client-subnet '192.168.0.0/24' -The first address of the paramter ``client-subnet``, will be used as the default gateway. +The first address of the parameter ``client-subnet``, will be used as the default gateway. Connected sessions can be checked via the ``show ipoe-server sessions`` command. .. code-block:: sh @@ -72,7 +72,7 @@ globally communicate without the need of any NAT rules. Automatic VLAN creation ======================= -To create VLANs per user during runtime, the follwing settings are required on a per interface basis. VLAN ID and VLAN range can be present in the configuration at the same time. +To create VLANs per user during runtime, the following settings are required on a per interface basis. VLAN ID and VLAN range can be present in the configuration at the same time. .. code-block:: sh |