if_spppsubr: Define a few more LCP options. Recognize, sanity-check and report (but still reject for the moment) multilink PPP configuration options received.
Submitted by: Neel Chauhan <neel AT neelc DOT org>
Obtained from: NetBSD
Differential D25681
if_spppsubr: Define a few LCP options, Recognize (but still reject) multilink PPP config options eugen_grosbein.net on Jul 16 2020, 2:12 AM. Authored by Tags Referenced Files
Details
if_spppsubr: Define a few more LCP options. Recognize, sanity-check and report (but still reject for the moment) multilink PPP configuration options received. Submitted by: Neel Chauhan <neel AT neelc DOT org>
Diff Detail
Event TimelineComment Actions In case anybody is wondering, the source of the commit is here: https://freshbsd.org/commit/netbsd/src/hRr2tvIj1vj7QI2C Comment Actions CCing Roman Kurakin (ce(4)) and Serge Vakulenko (cp(4)), see later. 16.07.2020 9:23, neel_neelc.org (Neel Chauhan) wrote:
I wonder if we really have use cases for sppp(4)/ng_sppp(4) these days. This code was created in 199x to support some synchronous Cronyx adapters and their drivers: ce(4) for PCI G.703/E1 card, Both ce(4) and cp(4) are i386-only drivers at present. I could not find any other consumers of sppp code in base system and I'd like to see some comments from rik and vak, though. Comment Actions Sorry for the mess, my latest actions on this differential were unintentional, some problems with old Firefox. Comment Actions Such synchronous lines are still in use (here):
But you are right: Do we really need a specialized PPP hardware support these days? Normal PPP over serial lines (currently available) does work using ppp(4) Comment Actions Makes 100% sense. I almost forgot this when writing this patch: NetBSD is purposely designed for your old Compaq or Packard Bell with ancient hardware, whereas FreeBSD is for more modern hardware. And the oldest computer I have access to here in the Seattle area is from 2013, that not my primary. My 2000s and 90s hardware is back at my dad's place in New York. |