diff --git a/SUMMARY.md b/SUMMARY.md index 65dd7c5..ed65270 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -36,6 +36,7 @@ * [Roaming RRM and SON](configuration-examples/roaming-rrm-and-son.md) * [Multi-PSK \(MDU Shared Key\)](configuration-examples/multi-psk-mdu-multiple-shared-key.md) * [VxLAN](configuration-examples/vxlan.md) +* [L2TP](configuration-examples/l2tp.md) * [RADIUS Authenticated SSID](configuration-examples/radius-authenticated-ssid.md) * [Passpoint®](configuration-examples/passpoint-r1/README.md) * [Configuration Introduction](configuration-examples/passpoint-r1/configuration-introduction.md) diff --git a/configuration-examples/l2tp.md b/configuration-examples/l2tp.md new file mode 100644 index 0000000..b6acb92 --- /dev/null +++ b/configuration-examples/l2tp.md @@ -0,0 +1,66 @@ +--- +description: OpenWiFi 2.0 +--- + +# L2TP + +Layer 2 Tunneling Protocol may be associated to any interface using the "tunnel" configuration option. + +This makes it possible to configure L2TP for multiple types of deployments as any interface may be encapsulated by the "tunnel" parameter. + +For example, to send all content of a specific SSID over an L2TP tunnel, the following configuration would apply. + +```text + { + "name": "LAN", + "role": "downstream", + "services": [ "ssh" ], + "ethernet": [ + { + "select-ports": [ + "LAN*" + ] + } + ], + "ipv4": { + "addressing": "static", + "subnet": "192.168.1.1/24", + "dhcp": { + "lease-first": 10, + "lease-count": 100, + "lease-time": "6h" + } + } + }, + { + "name": "L2TP", + "role": "downstream", + "tunnel": { + "proto": "l2tp", + "server": " far end IP address ", + "user-name": "secret-l2tp-username", + "password": "secrectPassword" + }, + "ipv4": { + "addressing": "static", + "subnet": "192.168.10.1/24", + "dhcp": { + "lease-first": 10, + "lease-count": 100, + "lease-time": "6h" + } + }, + "ssids": [ + { + "name": "Tunneled SSID", + "wifi-bands": [ + "5G", "2G" + ], + "bss-mode": "ap" + } + ] + } + ], + +``` +