Date: Sun, 30 Apr 2017 00:47:51 +0800 From: Julian Elischer <julian@freebsd.org> To: Brooks Davis <brooks@freebsd.org>, freebsd-net@freebsd.org, freebsd-atm@freebsd.org Subject: Re: The fate of ngatm Message-ID: <752628c6-f6a2-c4e4-e756-66b115428766@freebsd.org> In-Reply-To: <20170427180029.GB35387@spindle.one-eyed-alien.net> References: <20170427180029.GB35387@spindle.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28/4/17 2:00 am, Brooks Davis wrote: > As previous threatened, I've removed support for NATM (as well as a > remarkable number of remnants of the old ATM framework). One piece > that still remains is the ngatm framework in netgraph. This includes > the ng_ccatm(4), ng_sscfu(4), ng_sscop(4), and ng_uni(4) nodes. > > These don't attach to physical interfaces and didn't depend on the NATM > interface code so I left them alone in the first cut. My question > is, are they useful without physical interfaces? If so, keeping them > doesn't appear to have a high support burden. If not, we should remove > them. > > -- Brooks I don't know if people are using these now, but at one stage people were using them to decode/encode atm higher level protocols over an ethernet transport to implement a PPPoA infrastructure. No idea if it's still being used .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?752628c6-f6a2-c4e4-e756-66b115428766>