Re: Removing PF

[Michael van Elst <mlelstv%serpens.de@localhost>]

On Sat, Mar 30, 2019 at 02:18:29PM +0100, Piotr Meyer wrote:
> On Sat, Mar 30, 2019 at 12:59:00PM -0000, Michael van Elst wrote:
> > >Just to get the facts straight: NPF has a bigger market share *outside*
> > >NetBSD, at least certainly for commercial users.  They also contribute.
> > 
> > Ironically, the same is also true for PF...
> 
> But contributions to PF are made against OpenBSD kernel, true? And the
> essence of problem is that:
> - NetBSD version of PF is too old to adapt them without ton of work,

That's self-evident, the "ton of work" is of course just the same that
would have been needed if you had tracked pf development.


> - even current PF in OpenBSD doesn't fit very well into MP kernels 

Whatever "MP kernel" is. It no longer fits that well to our recent
MP changes of the network stack, but that mostly results in being
less efficient, not in being more difficult to port or track.


>   and that makes "fresh" import cumbersome and fruitless

It's always cumbersome to import foreign code. NPF won't be any different,
but since it is a newer development, it has some headstart. Don't believe
NPF is something "native" and thus easier to track, see the recent change
from our "native" proplib to its proprietary library.


Greetings,
-- 
                                Michael van Elst
Internet: mlelstv%serpens.de@localhost
                                "A potential Snark may lurk in every tree."