PPPOED(8) | Maintenance Commands and Procedures | PPPOED(8) |
pppoed - PPPoE server daemon
ppoed [options]
The pppoed daemon implements the server-side negotiation of PPPoE. When a client requests service from this daemon, a copy of pppd(8) is invoked to handle the actual PPP communication.
At startup, options are read from the command line and the /etc/ppp/pppoe file. After these options have been read, options in the per-device /etc/ppp/pppoe.device files are read, using the device names specified on the command line or in /etc/ppp/pppoe. Device names are not permitted in the per-device files. It is not an error if any of these files are absent; missing files are ignored.
Options are reread in the same order on SIGHUP. Except for the possibility of short delays due to the processing time, SIGHUP does not interfere with any client operations. Current status, including options read, is dumped to /tmp/pppoed.pid on SIGINT.
The options are used to set up a list of services to be offered to PPPoE clients on the broadcast domains (Ethernet subnets) specified by the named devices. Option parsing is always in one of two modes, either global mode or service mode. The initial mode at the beginning of each file (and the command line) is global mode. Options specified in global mode serve as default values for subsequently defined services. Service mode is entered by the service name option. In this mode, the named option is defined. Options that appear in this mode override any global mode definitions for the current service.
The option parsing follows standard shell tokenizing rules, using whitespace to delimit tokens, quotes to enclose strings that can contain whitespace, and escape sequences for special characters. Environment variables are substituted using familiar $VAR and ${VAR} syntax and set using NEWVAR=string. Variables are both usable in subsequent options and provided to the pppd(8) processes spawned for each client, but they are interpreted as they are encountered during option processing. Thus, all set variables are seen by all processes spawned; position in the configuration files has no effect on this.
The pppoed daemon supports the following options:
client [except] client-list
This option can be specified more than once for a given service. For a given client, first match among all listed options encountered specifies the handling. If it matches an option with except specified, then access is denied. Otherwise, it is granted. The client list within a service is prepended to any list specified in the global context.
If no client options are given or if all options are specified with except, then all clients are permitted by default. If any client options without except are specified, then no clients are permitted by default.
The client-list is a comma-separated list of client identifiers. The match is made if any client on the list matches; thus, these are logically "ORed" together. Each client identifier can be either a symbolic name (resolved through /etc/ethers or NIS, as defined by /etc/nsswitch.conf) or a hexadecimal Ethernet address in the format x:x:x:x:x:x. In the latter case, any byte of the address can be "*", which matches any value in that position. For example, 40:0:1a:*:*:* matches Ethernet adapters from the manufacturer assigned block 40:0:1a.
debug
device device-list
extra string
file path
The global mode options specified in files read by this command use the options set in the current file's global mode; this condition extends to any file included by those files. All files read are parsed as though the command line had specified this option, and thus inherit the command line's global modes.
This option can be used to revert to global mode at any point in an option file by specifying file /dev/null.
group name
log path
nodebug
nowildcard
path path
pppd string
server string
service name
user name
wildcard
Example 1 Configuring for Particular Services
In the /etc/ppp/pppoe file:
service internet
device $DEV
pppd "proxyarp 192.168.1.1:" service debugging
device hme0,$DEV
pppd "debug proxyarp 192.168.1.1:"
You then invoke the daemon with:
example% /usr/lib/inet/pppoed DEV=eri0
The lines in /etc/ppp/pppoe and the preceding command result in offering services "internet" and "debugging" (and responding to wildcard queries) on interface eri0, and offering only service "debugging" on interface hme0.
The pppoed daemon responds to the following signals:
SIGHUP
SIGINT
/usr/lib/inet/pppoed
/dev/sppptun
/etc/ppp/pppoe
/etc/ppp/pppoe.device
/etc/ppp/pppoe-errors
/etc/ppp/pppoe.if
/tmp/pppoed.pid
sppptun(4M), pppd(8), pppoec(8), sppptun(8)
Mamakos, L., et al. RFC 2516, A Method for Transmitting PPP Over Ethernet (PPPoE). Network Working Group. February 1999
Because pppd is installed setuid root, this daemon need not be run as root. However, if it is not run as root, the user and group options are ignored.
The Ethernet interfaces to be used must be plumbed for PPPoE using the sppptun(8) utility before services can be offered.
The daemon operate runs even if there are no services to offer. If you want to modify a configuration, it is not necessary to terminate the daemon. Simply use pkill -HUP pppoed after updating the configuration files.
The PPPoE protocol is far from perfect. Because it runs directly over Ethernet, there is no possibility of security and the MTU is limited to 1492 (violating RFC 1661's default value of 1500). It is also not possible to run the client and the server of a given session on a single machine with a single Ethernet interface for testing purposes. The client and server portions of a single session must be run on separate Ethernet interfaces with different MAC addresses.
January 6, 2003 | OmniOS |