Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pppoe-discovery(8) [debian man page]

PPPOE-DISCOVERY(8)					      System Manager's Manual						PPPOE-DISCOVERY(8)

NAME

       pppoe-discovery - perform PPPoE discovery

SYNOPSIS

       pppoe-discovery [ options ]
       pppoe-discovery { -V | -h }

DESCRIPTION

       pppoe-discovery	performs the same discovery process as pppoe, but does not initiate a session.	It sends a PADI packet and then prints the
       names of access concentrators in each PADO packet it receives.

OPTIONS

       -I interface
	      The -I option specifies the Ethernet interface to use.  Under Linux, it is typically eth0 or eth1.  The  interface  should  be  "up"
	      before you start pppoe-discovery, but should not be configured to have an IP address.  The default interface is eth0.

       -D file_name
	      The -D option causes every packet to be dumped to the specified file_name.  This is intended for debugging only.

       -U
	      Causes  pppoe-discovery  to use the Host-Uniq tag in its discovery packets.  This lets you run multiple instances of pppoe-discovery
	      and/or pppoe without having their discovery packets interfere with one another.  You must supply this option to all  instances  that
	      you intend to run simultaneously.

       -S service_name
	      Specifies  the desired service name.  pppoe-discovery will only accept access concentrators which can provide the specified service.
	      In most cases, you should not specify this option.  Use it only if you know that there are multiple  access  concentrators  or  know
	      that you need a specific service name.

       -C ac_name
	      Specifies the desired access concentrator name.  pppoe-discovery will only accept the specified access concentrator.  In most cases,
	      you should not specify this option.  Use it only if you know that there are multiple access concentrators.  If both the  -S  and	-C
	      options are specified, they must both match.

       -A
	      This option is accepted for compatibility with pppoe, but has no effect.

       -V | -h
	      Either of these options causes pppoe-discovery to print its version number and usage information, then exit.

AUTHORS

       pppoe-discovery was written by Marco d'Itri <md@linux.it>, based on pppoe by David F. Skoll <dfs@roaringpenguin.com>.

SEE ALSO

       pppoe(8), pppoe-sniff(8)

								  22 January 2006						PPPOE-DISCOVERY(8)

Check Out this Related Man Page

PPPOE-CONNECT(8)					      System Manager's Manual						  PPPOE-CONNECT(8)

NAME

       pppoe-connect - Shell script to manage a PPPoE link

SYNOPSIS

       pppoe-connect [config_file]

       pppoe-connect interface user [config_file]

DESCRIPTION

       pppoe-connect  is  a  shell  script  which  manages a PPPoE connection using the Roaring Penguin user-space PPPoE client.  If you omit con-
       fig_file, the default file /etc/sysconfig/network-scripts/ifcfg-ppp0 is used.  If you supply interface and user,  then  they  override  the
       Ethernet interface and user-name settings in the configuration file.

       Note that normally, you should not invoke pppoe-connect directly.  Instead, use pppoe-start to bring up the PPPoE connection.

       pppoe-connect  first  reads a configuration file.  It then brings up a PPPoE connection.  If the connection ever drops, a message is logged
       to syslog, and pppoe-connect re-establishes the connection.  In addition, each time the connection is dropped  or  cannot  be  established,
       pppoe-connect executes the script /etc/ppp/pppoe-lost if it exists and is executable.

       The shell script pppoe-stop causes pppoe-connect to break out of its loop, bring the connection down, and exit.

TECHNICAL DETAILS

       pppoe-connect uses the following shell variables from the configuration file:

       ETH    The Ethernet interface connected to the DSL modem (for example, eth0).

       USER   The PPPoE user-id (for example, b1xxnxnx@sympatico.ca).

       PIDFILE
	      A file in which to write the process-ID of the pppoe-connect process (for example, /var/run/pppoe.pid).  Two additional files ($PID-
	      FILE.pppd and $PIDFILE.pppoe) hold the process-ID's of the pppd and pppoe processes, respectively.

       By using different configuration files with different PIDFILE settings, you can manage multiple PPPoE connections.  Just specify  the  con-
       figuration file as an argument to pppoe-start and pppoe-stop.

AUTHOR

       pppoe-connect was written by David F. Skoll <dfs@roaringpenguin.com>.

       The pppoe home page is http://www.roaringpenguin.com/pppoe/.

SEE ALSO

       pppoe(8),  pppoe-start(8),  pppoe-stop(8), pppd(8), pppoe.conf(5), pppoe-setup(8), pppoe-status(8), pppoe-sniff(8), pppoe-server(8), pppoe-
       relay(8)

4th Berkeley Distribution					 21 February 2000						  PPPOE-CONNECT(8)
Man Page