NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ipfilter missing in most GENERIC kernels



"Frank Wille" <frank%phoenix.owl.de@localhost> writes:

> On 2026-11-13, Greg Troxel <gdt%lexort.com@localhost> wrote:
>
>> > I didn't read any announcement that it is obsolete and replaced by
>> > NPF or similar.
>>
>> I can't find it, but I remember that ipfilter was deprecated for maybe
>> NetBSD 9 and I think NetBSD 10.
>
> Ok. Thanks. So I should consider switching to NPF over time?

You should consider it, but my view is that npf is not entirely
complete.  My advice would be to understand npf and construct a ruleset
that does what you want, and speak up if you can't do something you did
in ipfilter.  And then to test it carefully.  It's clear to me that npf
is the future for firewall on NetBSD, and it's been getting better over
time.

>> I believe that it is not included in
>> any default kernsl; i386 and amd64 have it in ALL which is a kernel for
>> build testing, not for running.
>
> Hmm. I'm quite sure that I run the generic 11.0 release kernel on one
> of our HP Proliant servers (amd64), and there I could enable ipfilter:
>
> proteus# uname -a
> NetBSD proteus 11.0 NetBSD 11.0 (GENERIC) #0: Thu Jul 30 15:23:12 UTC 2026  mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/amd64/compile/GENERIC amd64
> proteus# /etc/rc.d/ipfilter status
> ipf: IP Filter: v5.1.2 (536)
> Kernel: IP Filter: v5.1.2
> Running: yes
> Log Flags: 0 = none set
> Default: pass all, Logging: available
> Active list: 0
> Feature mask: 0x14e

Look at 'modstat' and ipl.  It is possible that running the control
program loads the module, or you added it to modules.conf and forgot.

>> Add it to GENERIC.local and rebuild.
>
> Will do. Thanks.

Understand the module situation first


Home | Main Index | Thread Index | Old Index