Annotation of embedaddon/mpd/doc/mpd26.html, revision 1.1.1.4

1.1       misho       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: 
1.1.1.4 ! misho       9: <A HREF="mpd.html"><EM>Mpd 5.9 User Manual</EM></A>
1.1       misho      10:  <b>:</b> <A HREF="mpd17.html"><EM>Configuring Mpd</EM></A>
                     11:  <b>:</b> <EM>IPCP layer</EM><BR>
                     12: <b>Previous:</b> <A HREF="mpd25.html"><EM>MPPC protocol</EM></A><BR>
                     13: <b>Next:</b> <A HREF="mpd27.html"><EM>IPv6CP layer</EM></A>
                     14: 
                     15: 
                     16: <HR NOSHADE>
                     17:   <H2><A NAME="26"></A>4.7. IPCP layer<A NAME="ipcp"></A></H2>
                     18: 
                     19: <p>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.</p>
                     23: <p>
                     24: <dl>
                     25: 
                     26: <dt><b><code>set ipcp ranges (<em>local/width</em>|ippool <em>pool</em>) (<em>remote/width</em>|ippool <em>pool</em>)</code></b><dd><p>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><em>width</em></code> determines how flexible we are, i.e., how
                     30: close the actual negotiated address must be to the target address.
                     31: A <code><em>width</em></code> of 32 means they must match exactly; a
                     32: <code><em>width</em></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.</p>
                     36: <p>By convention, the <code><em>local</em></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: <em>a priori</em> what our local IP address should be.</p>
                     40: <p>The <code><em>remote</em></code> address should <em>not</em> 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><em>width</em></code> may
                     43: of course be zero.</p>
                     44: <p>It is also possible to specify ippool name to use for assigning remote ip.
                     45: In such case width 32 is assumed.</p>
                     46: <p>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.''</p>
                     49: 
                     50: <dt><b><code>set ipcp dns <em>primary</em> [ <em>secondary</em> ]</code></b><dd><p>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.</p>
                     55: 
1.1.1.4 ! misho      56: <dt><b><code>set ipcp nbns <em>primary</em> [ <em>secondary</em> ]</code></b><dd><p>Some Microsoft PPP clients request NetBIOS name server (NBNS)
1.1       misho      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.</p>
                     62: 
                     63: <dt><b><code>set ipcp accept <em>option ...</em> </code></b><dd>
                     64: <dt><b><code>set ipcp deny <em>option ...</em> </code></b><dd>
                     65: <dt><b><code>set ipcp enable <em>option ...</em> </code></b><dd>
                     66: <dt><b><code>set ipcp disable <em>option ...</em> </code></b><dd>
                     67: <dt><b><code>set ipcp yes <em>option ...</em> </code></b><dd>
                     68: <dt><b><code>set ipcp no <em>option ...</em> </code></b><dd>
                     69: <p>These commands configure various IPCP options. The <code><b>vjcomp</b></code>
                     70: option is <em>bi-directional</em> in that it can be independently
                     71: enabled and disabled in each direction.</p>
                     72: <p>The <code><b>enable</b></code> and <code><b>disable</b></code> commands determine
                     73: whether we want the corresponding option.
                     74: The <code><b>accept</b></code> and <code><b>deny</b></code> commands determine
                     75: whether we will allow the peer to request the corresponding option.</p>
                     76: 
                     77: <p>The <b><code>yes</code></b> command is the same as
                     78: <code><b>enable</b></code> and <code><b>accept</b></code>.
                     79: The <b><code>no</code></b> command is the same as
                     80: <code><b>disable</b></code> and <code><b>deny</b></code>.</p>
                     81: 
                     82: </dl>
                     83: </p>
                     84: 
                     85: <p>The options available at the IPCP layer are:</p>
                     86: <p>
                     87: <dl>
                     88: 
                     89: <dt><b><code>vjcomp</code></b><dd><p>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.</p>
                     94: <p>Default <code><b>enable</b></code> and <code><b>accept</b></code>.</p>
                     95: 
                     96: <dt><b><code>req-pri-dns </code></b><dd>
                     97: <dt><b><code>req-sec-dns </code></b><dd>
                     98: <dt><b><code>req-pri-nbns </code></b><dd>
                     99: <dt><b><code>req-sec-nbns </code></b><dd>
                    100: <p>Enabling these options causes mpd to request primary and/or secondary
                    101: DNS and/or NBNS servers from the remote peer during negotiation.</p>
                    102: <p>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.</p>
                    105: <p>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.</p>
                    107: 
                    108: </dl>
                    109: </p>
                    110: 
                    111:  <HR NOSHADE>
1.1.1.4 ! misho     112: <A HREF="mpd.html"><EM>Mpd 5.9 User Manual</EM></A>
1.1       misho     113:  <b>:</b> <A HREF="mpd17.html"><EM>Configuring Mpd</EM></A>
                    114:  <b>:</b> <EM>IPCP layer</EM><BR>
                    115: <b>Previous:</b> <A HREF="mpd25.html"><EM>MPPC protocol</EM></A><BR>
                    116: <b>Next:</b> <A HREF="mpd27.html"><EM>IPv6CP layer</EM></A>
                    117: 
                    118: 
                    119: 
                    120: </BODY>
                    121: </HTML>

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>