embedaddon/mpd/doc/mpd26.html - view

File: [ELWIX - Embedded LightWeight unIX -] / embedaddon / mpd / doc / mpd26.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>IPCP layer</TITLE> 6: </HEAD> 7: <BODY text="#000000" bgcolor="#ffffff"> 8: 9: <A HREF="mpd.html">Mpd 5.8 User Manual</A> 10: : <A HREF="mpd17.html">Configuring Mpd</A> 11: : IPCP layer  12: Previous: <A HREF="mpd25.html">MPPC protocol</A>  13: Next: <A HREF="mpd27.html">IPv6CP layer</A> 14: 15: 16: <HR NOSHADE> 17: <H2><A NAME="26"></A>4.7. IPCP layer<A NAME="ipcp"></A></H2> 18: 19: This chapter describes commands that configure the IP Control 20: Protocol (IPCP) layer. To enable IPCP, <code>ipcp</code> option should be 21: enabled at the bundle layer. All of these commands apply to the currently 22: active bundle. 23:  24: <dl> 25: 26: <dt><code>set ipcp ranges (local/width|ippool pool) (remote/width|ippool pool)</code><dd>This command determines what IP addresses mpd will allow to be 27: negotiated at the local and remote ends of the link. For each 28: endpoint, we have a target address and a netmask width. The 29: <code>width</code> determines how flexible we are, i.e., how 30: close the actual negotiated address must be to the target address. 31: A <code>width</code> of 32 means they must match exactly; a 32: <code>width</code> of zero means any address is suitable. For 33: example, <code>192.168.1.17/25</code> means that IP address 34: <code>192.168.1.17</code> is desired, but any IP address in the range 35: <code>192.168.1.0</code> through <code>192.168.1.128</code> is acceptable. 36: By convention, the <code>local</code> address may be 37: <code>0.0.0.0</code> to request that the remote server assign us an IP 38: address. Of course, for this to work the remote side must know 39: a priori what our local IP address should be. 40: The <code>remote</code> address should not be 41: <code>0.0.0.0</code>. This is so if the peer requests <code>0.0.0.0</code>, 42: we have some address to give him. The <code>width</code> may 43: of course be zero. 44: It is also possible to specify ippool name to use for assigning remote ip. 45: In such case width 32 is assumed. 46: If the two sides cannot agree on the IP address assignments after 47: repeated negotiation attempts, then the connection will fail. This 48: is manifested with the error message ``IPCP: not converging.'' 49: 50: <dt><code>set ipcp dns primary [ secondary ]</code><dd>Some PPP clients request DNS server information from their remote peer. 51: This commands enables mpd to have an answer for any such clients. 52: This command is especially useful for supplying information to PPTP clients. 53: One or two DNS server IP addresses may be given. An address of 54: <code>0.0.0.0</code> erases that entry. 55: 56: <dt><code>set ipcp nbns primary [ secondary ]</code><dd>Some MIcrosoft PPP clients request NetBIOS name server (NBNS) 57: information from their remote peer. This commands enables mpd to 58: have an answer for any such clients. This command is especially 59: useful for supplying information to PPTP clients. One or two NBNS 60: server IP addresses may be given. An address of <code>0.0.0.0</code> 61: erases that entry. 62: 63: <dt><code>set ipcp accept option ... </code><dd> 64: <dt><code>set ipcp deny option ... </code><dd> 65: <dt><code>set ipcp enable option ... </code><dd> 66: <dt><code>set ipcp disable option ... </code><dd> 67: <dt><code>set ipcp yes option ... </code><dd> 68: <dt><code>set ipcp no option ... </code><dd> 69: These commands configure various IPCP options. The <code>vjcomp</code> 70: option is bi-directional in that it can be independently 71: enabled and disabled in each direction. 72: The <code>enable</code> and <code>disable</code> commands determine 73: whether we want the corresponding option. 74: The <code>accept</code> and <code>deny</code> commands determine 75: whether we will allow the peer to request the corresponding option. 76: 77: The <code>yes</code> command is the same as 78: <code>enable</code> and <code>accept</code>. 79: The <code>no</code> command is the same as 80: <code>disable</code> and <code>deny</code>. 81: 82: </dl> 83:  84: 85: The options available at the IPCP layer are: 86:  87: <dl> 88: 89: <dt><code>vjcomp</code><dd>This option enables Van Jacobson TCP header compression, which saves 90: several bytes per TCP data packet. You almost always want this option. 91: This compression ineffective for TCP connections with enabled modern 92: extensions like time stamping or SACK, which modify TCP options between 93: sequential packets. 94: Default <code>enable</code> and <code>accept</code>. 95: 96: <dt><code>req-pri-dns </code><dd> 97: <dt><code>req-sec-dns </code><dd> 98: <dt><code>req-pri-nbns </code><dd> 99: <dt><code>req-sec-nbns </code><dd> 100: Enabling these options causes mpd to request primary and/or secondary 101: DNS and/or NBNS servers from the remote peer during negotiation. 102: If any DNS servers are supplied by the peer, they will appear as 103: parameters to the script specified by the <code>set iface up-script</code> 104: command, if any. 105: Currently, mpd does not use the NBNS values for anything; they just 106: appear in the log. A future revision may actually do something with them. 107: 108: </dl> 109:  110: 111: <HR NOSHADE> 112: <A HREF="mpd.html">Mpd 5.8 User Manual</A> 113: : <A HREF="mpd17.html">Configuring Mpd</A> 114: : IPCP layer  115: Previous: <A HREF="mpd25.html">MPPC protocol</A>  116: Next: <A HREF="mpd27.html">IPv6CP layer</A> 117: 118: 119: 120: </BODY> 121: </HTML>