I'm sponsoring this fast-track request for myself.  The timer is set
to 05/29/2009.


This project will add two minor features to Solaris PPP ("Vector"
PSARC 2000/003) and PPPoE ("Vector PPPoE" PSARC 2000/485).  All of the
interfaces described are "Committed" and are being given "Patch/Micro"
release binding, although no actual backport is expected at this time.

The first feature allows PPP and PPPoE to be used inside exclusive IP
stack non-global zones.  Currently, the sppp and sppptun drivers use
PRIV_SYS_NET_CONFIG for administrative access.  This privilege, which
encompasses many different low-level networking features, is
intentionally excluded from non-global zones.

PPP and PPPoE aren't necessarily IP features, so PRIV_SYS_IP_CONFIG
(which is otherwise suitable) doesn't seem right for them.  They're
datalink layer features.  But unlike the existing PRIV_SYS_DL_CONFIG,
non-global zones *should* be able to use them by default.

Thus, we will introduce a new PRIV_SYS_PPP_CONFIG.  This is a subset
of PRIV_SYS_NET_CONFIG, so processes holding that privilege can still
use PPP and PPPoE administrative interfaces.  The new privilege will
be documented as:

        Allows a process to create and destroy PPP (sppp) interfaces.
        Allows a process to configure PPP tunnels (sppptun).

The second feature in this project allows for interoperability with
some peculiar PPPoE access devices that use Ethertype values other
than those documented in RFC 2516.  These devices appear to be popular
in some non-US locations.  (See CR 4695172 for details.)

The additions for this feature are a new "-s" option for the
sppptun(1M) command:

        sppptun plumb [-s <sap>] [<protocol> <device>]

This allows the user to specify a particular SAP (Ethertype) value in
hexadecimal to be used for each plumbed stream.  The more common way
to configure PPPoE, though, is through the /etc/ppp/pppoe.if file,
which is used to run sppptun at boot time.  This file currently takes
one interface name per line.  It will be updated to use this syntax:

        if-name [session-SAP [discovery-SAP]]

where session-SAP and discovery-SAP are used to set the SAP values for
sppptun.  The problem described in the original bug report could now
be handled by using:

        e1000g0 3c13 3c12

The defaults (per RFC 2516) are 8864 and 8863, respectively.  The
sppptun(1M) man page, which describes both the sppptun command line
and the /etc/ppp/pppoe.if file, will be updated to describe the new
interfaces.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

Reply via email to