On 8/20/2019 5:49 AM, Kristof Provost wrote:
> [snip]
> We’ve not done wholesale imports from OpenBSD in a long time, yes, but
> FreeBSD’s pf is maintained, and regularly gets new features and bug
> fixes. Fixes even flow in both directions between OpenBSD and FreeBSD.
Around the time the work
Hey Kristof,
Thatnk you for your very thorugh explanation! It is very interesting to
read that FreeBSD's PF is, in some ways, "better" than OpenBSD's (with
regards to scalability).
It was also very simplistic to state FreeBSD's version of PF essentially
equals OpenBSD 4.1's version. I made this s
On 20 Aug 2019, at 12:32, Goran Mekić wrote:
> On Tue, Aug 20, 2019 at 11:49:18AM +0200, Kristof Provost wrote:
>> One thing I’ve thought of trying, and that might be an interesting stepping
>> stone, is to create a port (/usr/ports/net/opf or whatever) of OpenBSD’s pf.
>> In that version it’d be a
On Tue, Aug 20, 2019 at 11:49:18AM +0200, Kristof Provost wrote:
> One thing I’ve thought of trying, and that might be an interesting stepping
> stone, is to create a port (/usr/ports/net/opf or whatever) of OpenBSD’s pf.
> In that version it’d be acceptable to not fix any of the above issues. It’d
On 20 Aug 2019, at 11:36, Tom Marcoen wrote:
Hey all,
I'm quite new to FreeBSD so appologies if this is a stupid question.
Is there a good reason for not upgrading PF to the version from
OpenBSD
6.5?
There are several reasons why updating pf is a non-trivial problem.
From an e-mail I sent o
Hey all,
I'm quite new to FreeBSD so appologies if this is a stupid question.
Is there a good reason for not upgrading PF to the version from OpenBSD
6.5? Currently it seems to be at the version from OpenBSD 4.1.
Regards,
Tom
___
freebsd-pf@freebsd.org
