Bug #226
closedUpdate pf to 3.9 or current
Description
update pf to a current version to get latest fixes and features
       Updated by luxh over 16 years ago
      Updated by luxh over 16 years ago
      
    
    No, this isn't done. I think it's still of interest though, but I can imagine it's 
a lot of work.
       Updated by russiane39 over 16 years ago
      Updated by russiane39 over 16 years ago
      
    
    I don't think it's worth updating pf codebase rightnow, first multiple routing 
tables and route labeling should be implemented, then we can import pf from 
OpenBSD. I personally interested in this too.
       Updated by dillon over 16 years ago
      Updated by dillon over 16 years ago
      
    
    :Michael Kosarev <russiane39@gmail.com> added the comment:
:
:I don't think it's worth updating pf codebase rightnow, first multiple rout=
:ing=20
:tables and route labeling should be implemented, then we can import pf from=
:=20
:OpenBSD. I personally interested in this too.
There are other issues as well.  Our PF codebase has extensions in it
    that are different from OpenBSD's, particularly with regards to how
    persistent state is handled and also with the fairq stuff.  We can't
    just replace it wholesale.-Matt
                    Matthew Dillon 
                    <dillon@backplane.com>
       Updated by tuxillo over 11 years ago
      Updated by tuxillo over 11 years ago
      
    
    - Category set to Networking
- Status changed from New to Feedback
- Assignee deleted (0)
- Target version set to 3.8
Hi all,
Jan Lentfer updated us to the version that was in OpenBSD 4.1 (70224baa0d7c2fcfc9b51076bdc46f77a8e1e2a7) back in Aug, 2010 which is around 1 year later this bug ticket was opened.
Afterwards it was updated to the version that was in OpenBSD 4.2 (315a7da3d68fcfb2e65c94e5d9bb3ac34ed7b595). A couple months later it was updated to OBSD 4.4's version (ed1f0be2a62c659ca93a1a1d83ade5a772127bc3) after many many fixes too.
I think we can close this one.
Cheers,
Antonio Huete
       Updated by tuxillo over 11 years ago
      Updated by tuxillo over 11 years ago
      
    
    - Status changed from Feedback to Closed
- Assignee set to tuxillo
corecode agreed to close it.