James Carlson wrote: > ... > 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.
What use do you forsee for these new configuration options? ... why would I ever want to change it? To me, it looks like I never would, so I'm wondering if these new interfaces are even necessary? A non architectural question... What happens if they're configured in reverse or to be the same#? Darren
