embedaddon/mpd/doc/mpd48.html - view

File: [ELWIX - Embedded LightWeight unIX -] / embedaddon / mpd / doc / mpd48.html
Revision 1.1.1.3 (vendor branch): download - view: text, annotated - select for diffs - revision graph
Tue Nov 1 09:56:12 2016 UTC (7 years, 8 months ago) by misho
Branches: mpd, MAIN
CVS tags: v5_8p7, v5_8p1_cross, v5_8p1, v5_8, HEAD

mpd 5.8

1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> 2: <HTML> 3: <HEAD> 4: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> 5: <TITLE>L2TP device type commands</TITLE> 6: </HEAD> 7: <BODY text="#000000" bgcolor="#ffffff"> 8: 9: <A HREF="mpd.html">Mpd 5.8 User Manual</A> 10: : <A HREF="mpd42.html">Device Types</A> 11: : L2TP device type commands  12: Previous: <A HREF="mpd47.html">PPTP device type commands</A>  13: Next: <A HREF="mpd49.html">PPPoE device type commands</A> 14: 15: 16: <HR NOSHADE> 17: <H2><A NAME="48"></A>5.6. L2TP device type commands<A NAME="l2tp"></A></H2> 18: This chapter describes commands that are specific to L2TP type links. 19: These commands apply to the currently active link, and are only 20: valid if the currently active link has type l2tp. 21: The L2TP protocol utilizes UDP datagrams on port 1701 (and this is 22: the default for <code>port</code> in the commands below) 23: to create and maintain virtual tunnel between IP peers. 24: One or more independent PPP connections (sessions) can be 25: carried inside this tunnel. 26: Complete L2TP network topology looks like: 27: <pre> 28: client <- some link type -> LAC <- L2TP tunnel -> LNS 29: </pre> 30:  31: LAC is physical level repeater, which receives PPP connection of some 32: type and forwards it to LNS using L2TP protocol. LNS is a PPP endpoint, 33: which receives PPP frames via L2TP tunnel and processes them. 34: In simple case, when physical conversion is not required, topology 35: can be simplified to: 36: <pre> 37: client (LAC emulator) <- L2TP tunnel -> LNS 38: </pre> 39:  40: Mpd is able to operate in both LAC and LNS modes. As LAC mpd supports 41: both simple case LAC emulator and complete LAC topologies. Complete 42: LAC can be configured by joining two physical devices using mpd's 43: repeater functionality. 44: Windows L2TP client uses IPSec encryption for the additional tunnel 45: security. So, to let it connect you must configure IPSec on your 46: MPD router or disable IPSec on Windows by setting registry 47: DWORD value ProhibitIpSec at the key 48: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\Parameters\ 49: into "1". 50:  51: <dl> 52: 53: <dt><code>set l2tp self ipaddr [ port ]</code><dd>Sets the local IP address and port for the L2TP connection. 54: There is known implementation bug if this option is not set 55: while accepting incoming connections on the router with multiple 56: IPs and clients are connecting not to the nearest address of 57: this router. 58: 59: <dt><code>set l2tp peer ipaddr [ port ]</code><dd>Sets the peer IP address and port for the L2TP connection. 60: This command applies to both incoming and outgoing connections. 61: For outgoing connections, this command is required in order to 62: specify where to connect to. For incoming connections, this command 63: is optional; if not given, mpd accepts incoming connections from any 64: host. Otherwise, only connections from the stated IP address 65: (and, optionally, port) are allowed. 66: 67: <dt><code>set l2tp hostname name</code><dd>Sets the L2TP tunnel local hostname. For server side, only one 68: unique hostname supported for every pair of listening IP (set l2tp self ...) 69: and peer ip (set l2tp peer ...). 70: If several hostnames defined, only the first matching will be used for all 71: incoming connections. 72: 73: <dt><code>set l2tp pmask mask</code><dd>Check peer hostname, related to wildcard <code>mask</code>. 74: Wildcard can contain any shell-like mask, such as "*.myhost.com" 75: Peer can set self hostname with <code>set l2tp hostname</code> command. 76: 77: <dt><code>set l2tp secret secret</code><dd>Sets the L2TP tunnel secret. Used to authenticate tunnel connection 78: and encrypt important control packets avpairs. For server side, only 79: one unique secret supported for every pair of listening IP (set l2tp self ...) 80: and peer ip (set l2tp peer ...). 81: If several secrets defined, only the first matching will be used for all 82: incoming connections. 83: NOTE: This options is not related with usual PPP authentication. 84: Windows client does not support tunnel authentication. 85: 86: <dt><code>set l2tp callingnum number</code><dd> 87: <dt><code>set l2tp callednum number</code><dd>Sets the calling and called telephone number to use when initiating a L2TP 88: connection. For most VPN applications this is ignored, but in certain 89: cases an actual phone number is required. 90: The default is the empty string. 91: 92: <dt><code>set l2tp enable option ... </code><dd> 93: <dt><code>set l2tp disable option ... </code><dd> 94: Enable and disable L2TP device type options for the link. 95: 96: </dl> 97:  98: 99: The following options are supported: 100:  101: <dl> 102: 103: <dt><code>outcall</code><dd>Inside L2TP tunnel, each individual PPP connection (there may be several), 104: is initiated as either an incoming or an outgoing call. 105: This allows to make an outgoing phone call (by LNS) via a remote access 106: server (LAC), as well as in more common case forward an incoming 107: phone call from an access server (LAC) to a remote L2TP server (LNS). 108: When this option is enabled, mpd will initiate outgoing calls (LNS); 109: otherwise mpd will initiate incoming calls (LAC). 110: The default is disable. 111: 112: <dt><code>hidden</code><dd>When L2TP tunnel secret is configured it is possible hide (encrypt) some 113: control data for additional protection. 114: The default is disable. 115: 116: <dt><code>length</code><dd>By default L2TP uses header Length field for control packets, but not for 117: data packets. This option enables Length field for data packets. 118: This feature enabled may be useful on links where packets padding may 119: happend. Disabling it reduces overhead by 2 bytes per packet. 120: The default is disable. 121: 122: <dt><code>dataseq</code><dd>By default L2TP requires header sequence fields for control packets, but 123: not require them for data packets. This option enables sequence fields for 124: data packets. 125: This feature enabled may be useful on links where packets reordering may 126: happend but it is intolerable. Disabling it reduces overhead by 4 bytes per packet. 127: The default is enable. 128: 129: <dt><code>resolve-once</code><dd>Enables resolving peer address only once, on startup, or on manual 130: typing in CLI. 131: The default is enable. 132: </dl> 133:  134: 135: 136: 137: <HR NOSHADE> 138: <A HREF="mpd.html">Mpd 5.8 User Manual</A> 139: : <A HREF="mpd42.html">Device Types</A> 140: : L2TP device type commands  141: Previous: <A HREF="mpd47.html">PPTP device type commands</A>  142: Next: <A HREF="mpd49.html">PPPoE device type commands</A> 143: 144: 145: 146: </BODY> 147: </HTML>