DragonFly BSD : pf no longer single-threaded reddit / BSD ---------------------------------------------------------------------- NotSafeForEarth · 2014-07-03 00:42 Is the pf in DragonFly BSD an OpenBSD pf port, or a fork, or something developed independently? ---------------------------------------------------------------------- Yakulu · 2014-07-03 00:52 It seems it [comes from an old version of OpenBSD](http://www.dragonfl ybsd.org/docs/newhandbook/Security/#index16h3) yes. ---------------------------------------------------------------------- [deleted] · 2014-07-03 01:31 Most *bsds have an older version of pf they maintain ---------------------------------------------------------------------- NotSafeForEarth · 2014-07-03 02:00 > the PF version in DragonFly is not in sync with OpenBSD's PF code. We have not yet incorporated the improvements made in PF over the last few years, but we have some improvements of our own. Oh dear. The same things as the very problematic actions in the FreeBSD camp, then. The only thing worse than an unnecessary fork is a de-facto/unadmitted fork. Second thought, that's not the only thing. Two forks are also worse. And this is two forks. Two de-facto forks. But thanks for clarifying. ---------------------------------------------------------------------- [deleted] · 2014-07-03 02:21 [deleted] ---------------------------------------------------------------------- pyvpx · 2014-07-03 06:44 I was okay with NetBSD doing npf, and I don't use FreeBSD for network related things in production, so an ancient pf was just fine by me...but now this? pf is almost a decade old people...shit (just fucking track pf development!) or get off the pot (roll your own!!!!1) damnit. ---------------------------------------------------------------------- fupjack · 2014-07-03 15:33 it was already forked just by porting; there is no "OpenPF" like there is for ssh or bgpd and so on. There's no easy way to have it be the same code base, especially since OpenBSD's single-threaded - new porting effort every time. I'd like to see a compatibility test suite, so that the syntax for configuring pf is predictable, even if the underlying code is changed. That's as big a task as porting, though. ---------------------------------------------------------------------- NotSafeForEarth · 2014-07-03 15:48 > There's no easy way to have it be the same code base, especially since OpenBSD's single-threaded You've got that the wrong way round. The FreeBSD port first came into existence, wasn't updated, *and then* that older-than-sticks version was patched to add multithreading. These were the acts, by the porters/forkers, that *made* things so difficult. Things weren't as difficult before, and had the port version been current, it would have been easy for OpenBSD to take the forkers' multithreading code on board. ---------------------------------------------------------------------- garja · 2014-07-03 21:40 If I remember correctly, the situation is a bit more complex and stupid than this. FreeBSD refused to update their pf version because it would have broken existing configs due to the pf syntax change. They could have changed it, but were so anal-retentive about backwards compatibility that they have created huge compatibility problems between themselves and upstream. DragonflyBSD and FreeBSD need to get their act together and collaborate with the OpenBSD guys to get the OpenPF ball rolling. It's no doubt a huge task, but the current situation is an embarrassment to the entire community. ---------------------------------------------------------------------- NotSafeForEarth · 2014-07-03 22:05 > DragonflyBSD and FreeBSD need to get their act together and collaborate with the OpenBSD guys to get the OpenPF ball rolling. I don't actually think PF (on OpenBSD) is particularly port- unfriendly, except maybe to Linux and Windows, but that's for architectural reasons, and even there people have done some limited porting work in the past; some more successful than others. I think it only now seems as if there were a need for an OpenPF *because* of the Free/DragonFlyBSD de-facto forking. I agree that these two need to get their act together to fix what they've broken, unless they really want to cement their forks and no further relationship with upstream. > It's no doubt a huge task, Only if they wish to yet reconcile their paleo-PF-based changes with upstream somehow. If they were to abandon their changes (and start hacking on -current), it would not be such a huge task, though of course when upstream will actually get its own multithreading then is anybody's guess. (The people who wrote the multithreading for their PF fork could help with that too, but starting over from scratch with a -current based multithreading implementation would involve admitting that their prior work went to waste.) > but the current situation is an embarrassment to the entire community. I couldn't agree more. Even worse, NetBSD have started to write yet another own, separate package filter, and FreeBSD still can't make up their mind between PF and IPFW (and DragonFlyBSD and OS X thus have IPFW as well). We're surrounded by brave knights in shining armour. It's the knights who say NIH, NIH, NIH! Ironically, this leaves Henning's modern PF as a [USP](/// "unique selling point") for OpenBSD... ---------------------------------------------------------------------- techsnapp · 2014-07-05 18:45 What's up with link to reddit? Are you sure itsit's package filter? I thought it would be packet filter. ---------------------------------------------------------------------- NotSafeForEarth · 2014-07-05 20:47 > What's up with link to reddit? Hover over it. It was just a little gloss, in case tech people don't know a marketing drone abbreviation like USP for "unique selling point". > Are you sure itsit's package filter? I thought it would be packet filter. I do not understand what you're asking. ---------------------------------------------------------------------- techsnapp · 2014-07-05 21:30 >Even worse, NetBSD have started to write yet another own, separate package filter Package filter is pf. I don't know if you were also saying netbsd is starting to make their own pf (packet filter) or something for packages. ---------------------------------------------------------------------- NotSafeForEarth · 2014-07-05 22:18 Please form complete sentences. You are making it unnecessarily hard to understand what you're trying to say if you don't spell things out. *Whose* (or what) "packet filter is pf"? NetBSD's? (Yes, and no; there's a PF port, and then there's NPF.) For the record, this is the "own, separate packet filter" on NetBSD that I was referring to: https://en.wikipedia.org/wiki/NPF_%28firewall%29 ---------------------------------------------------------------------- [deleted] · 2014-07-05 22:18 [deleted] ---------------------------------------------------------------------- techsnapp · 2014-07-05 22:41 I was quoting what you said. Read above and find in your above statements. I believe you meant to write "packet filter" but you wrote "package filter". that's all. Sorry for the complexity of this thread. ---------------------------------------------------------------------- NotSafeForEarth · 2014-07-05 22:46 OH. My bad. Sorry. I fucked up there. ---------------------------------------------------------------------- techsnapp · 2014-07-05 23:26 no problem. I didn't know if there was something very similar to packet filter but for packages. ;) ---------------------------------------------------------------------- NotSafeForEarth · 2014-07-05 23:42 Yeah, sorry for being damn near a bit of an ass earlier. It turns out, the Dunning-Kruger effect applies to yours truly as well.