embedaddon/mpd/doc/mpd48.html - view

File: [ELWIX - Embedded LightWeight unIX -] / embedaddon / mpd / doc / mpd48.html
Revision 1.1.1.4 (vendor branch): download - view: text, annotated - select for diffs - revision graph
Wed Mar 17 00:39:23 2021 UTC (3 years, 7 months ago) by misho
Branches: mpd, MAIN
CVS tags: v5_9p16, v5_9, HEAD

mpd 5.9

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>L2TP device type commands</TITLE> </HEAD> <BODY text="#000000" bgcolor="#ffffff"> <A HREF="mpd.html">Mpd 5.9 User Manual</A> : <A HREF="mpd42.html">Device Types</A> : L2TP device type commands  Previous: <A HREF="mpd47.html">PPTP device type commands</A>  Next: <A HREF="mpd49.html">PPPoE device type commands</A> <HR NOSHADE> <H2><A NAME="48"></A>5.6. L2TP device type commands<A NAME="l2tp"></A></H2> This chapter describes commands that are specific to L2TP type links. These commands apply to the currently active link, and are only valid if the currently active link has type l2tp. The L2TP protocol utilizes UDP datagrams on port 1701 (and this is the default for <code>port</code> in the commands below) to create and maintain virtual tunnel between IP peers. One or more independent PPP connections (sessions) can be carried inside this tunnel. Complete L2TP network topology looks like: <pre> client <- some link type -> LAC <- L2TP tunnel -> LNS </pre>  LAC is physical level repeater, which receives PPP connection of some type and forwards it to LNS using L2TP protocol. LNS is a PPP endpoint, which receives PPP frames via L2TP tunnel and processes them. In simple case, when physical conversion is not required, topology can be simplified to: <pre> client (LAC emulator) <- L2TP tunnel -> LNS </pre>  Mpd is able to operate in both LAC and LNS modes. As LAC mpd supports both simple case LAC emulator and complete LAC topologies. Complete LAC can be configured by joining two physical devices using mpd's repeater functionality. Windows L2TP client uses IPSec encryption for the additional tunnel security. So, to let it connect you must configure IPSec on your MPD router or disable IPSec on Windows by setting registry DWORD value ProhibitIpSec at the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\Parameters\ into "1".  <dl> <dt><code>set l2tp self ipaddr [ port ]</code><dd>Sets the local IP address and port for the L2TP connection. There is known implementation bug if this option is not set while accepting incoming connections on the router with multiple IPs and clients are connecting not to the nearest address of this router. <dt><code>set l2tp peer ipaddr [ port ]</code><dd>Sets the peer IP address and port for the L2TP connection. This command applies to both incoming and outgoing connections. For outgoing connections, this command is required in order to specify where to connect to. For incoming connections, this command is optional; if not given, mpd accepts incoming connections from any host. Otherwise, only connections from the stated IP address (and, optionally, port) are allowed. <dt><code>set l2tp hostname name</code><dd>Sets the L2TP tunnel local hostname. For server side, only one unique hostname supported for every pair of listening IP (set l2tp self ...) and peer ip (set l2tp peer ...). If several hostnames defined, only the first matching will be used for all incoming connections. <dt><code>set l2tp pmask mask</code><dd>Check peer hostname, related to wildcard <code>mask</code>. Wildcard can contain any shell-like mask, such as "*.myhost.com" Peer can set self hostname with <code>set l2tp hostname</code> command. <dt><code>set l2tp secret secret</code><dd>Sets the L2TP tunnel secret. Used to authenticate tunnel connection and encrypt important control packets avpairs. For server side, only one unique secret supported for every pair of listening IP (set l2tp self ...) and peer ip (set l2tp peer ...). If several secrets defined, only the first matching will be used for all incoming connections. NOTE: This options is not related with usual PPP authentication. Windows client does not support tunnel authentication. <dt><code>set l2tp callingnum number</code><dd> <dt><code>set l2tp callednum number</code><dd>Sets the calling and called telephone number to use when initiating a L2TP connection. For most VPN applications this is ignored, but in certain cases an actual phone number is required. The default is the empty string. <dt><code>set l2tp enable option ... </code><dd> <dt><code>set l2tp disable option ... </code><dd> Enable and disable L2TP device type options for the link. </dl>  The following options are supported:  <dl> <dt><code>outcall</code><dd>Inside L2TP tunnel, each individual PPP connection (there may be several), is initiated as either an incoming or an outgoing call. This allows to make an outgoing phone call (by LNS) via a remote access server (LAC), as well as in more common case forward an incoming phone call from an access server (LAC) to a remote L2TP server (LNS). When this option is enabled, mpd will initiate outgoing calls (LNS); otherwise mpd will initiate incoming calls (LAC). The default is disable. <dt><code>hidden</code><dd>When L2TP tunnel secret is configured it is possible hide (encrypt) some control data for additional protection. The default is disable. <dt><code>length</code><dd>By default L2TP uses header Length field for control packets, but not for data packets. This option enables Length field for data packets. This feature enabled may be useful on links where packets padding may happend. Disabling it reduces overhead by 2 bytes per packet. The default is disable. <dt><code>dataseq</code><dd>By default L2TP requires header sequence fields for control packets, but not require them for data packets. This option enables sequence fields for data packets. This feature enabled may be useful on links where packets reordering may happend but it is intolerable. Disabling it reduces overhead by 4 bytes per packet. The default is enable. <dt><code>resolve-once</code><dd>Enables resolving peer address only once, on startup, or on manual typing in CLI. The default is enable. </dl>  <HR NOSHADE> <A HREF="mpd.html">Mpd 5.9 User Manual</A> : <A HREF="mpd42.html">Device Types</A> : L2TP device type commands  Previous: <A HREF="mpd47.html">PPTP device type commands</A>  Next: <A HREF="mpd49.html">PPPoE device type commands</A> </BODY> </HTML>