Annotation of embedaddon/mpd/doc/mpd49.html, revision 1.1.1.1

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>PPPoE device type commands</TITLE>
                      6: </HEAD>
                      7: <BODY text="#000000" bgcolor="#ffffff">
                      8: 
                      9: <A HREF="mpd.html"><EM>Mpd 5.6 User Manual</EM></A>
                     10:  <b>:</b> <A HREF="mpd42.html"><EM>Device Types</EM></A>
                     11:  <b>:</b> <EM>PPPoE device type commands</EM><BR>
                     12: <b>Previous:</b> <A HREF="mpd48.html"><EM>L2TP device type commands</EM></A><BR>
                     13: <b>Next:</b> <A HREF="mpd50.html"><EM>Chat Scripting</EM></A>
                     14: 
                     15: 
                     16: <HR NOSHADE>
                     17:   <H2><A NAME="49"></A>5.7. PPPoE device type commands<A NAME="pppoe"></A></H2>
                     18: <p>This chapter describes commands that are specific to PPPoE type links.
                     19: These commands apply to the currently active link, and are only
                     20: valid if the currently active link has type <b>pppoe</b>.</p>
                     21: <p>PPPoE requires two pieces of configuration information: the name
                     22: of the Ethernet interface to use, and a service name, which should
                     23: be supplied by your ISP. If you do not have a service name, then
                     24: the empty string (the default) often suffices.</p>
                     25: <p>DSL Forum vendor-specific Circuit-ID/Remote-ID PPPoE tags extraction
                     26: supported in server mode.</p>
                     27: <p>
                     28: <dl>
                     29: 
                     30: <dt><b><code>set pppoe iface <em>interface-name</em></code></b><dd><p>Set the name of the Ethernet interface to use. PPPoE does
                     31: not affect normal use of the interface.</p>
                     32: 
                     33: <dt><b><code>set pppoe service <em>service-name</em></code></b><dd><p>Sets the requested PPPoE service name. Setting service name to "*" 
                     34: on link with allowed incoming connections allows to accept incoming 
                     35: connection requests with any service name specified.</p>
                     36: <p>Since FreeBSD 6.3-STABLE/7.0-STABLE of 2008-01-30 it is possible to use
                     37: "AC-Name\Service-Name" syntax to request specified access concentrator
                     38: for outgoing connection.</p>
                     39: <p>The default is "*".</p>
                     40: 
                     41: <dt><b><code>set pppoe acname <em>name</em></code></b><dd><p>Set name of this PPPoE access concentrator to be sent to clients.
                     42: If not specified, local hostname will be used.</p>
                     43: 
                     44: </dl>
                     45: </p>
                     46: 
                     47: 
                     48: 
                     49: 
                     50:  <HR NOSHADE>
                     51: <A HREF="mpd.html"><EM>Mpd 5.6 User Manual</EM></A>
                     52:  <b>:</b> <A HREF="mpd42.html"><EM>Device Types</EM></A>
                     53:  <b>:</b> <EM>PPPoE device type commands</EM><BR>
                     54: <b>Previous:</b> <A HREF="mpd48.html"><EM>L2TP device type commands</EM></A><BR>
                     55: <b>Next:</b> <A HREF="mpd50.html"><EM>Chat Scripting</EM></A>
                     56: 
                     57: 
                     58: 
                     59: </BODY>
                     60: </HTML>

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