en Copyright 2015 Java http://kernelsources.org:8080/source/history/freebsd/sbin/pfilctl/Makefile#e9ac41698b2f322d55ccf9da50a3596edb2c1800 Remove residual blank line at start of MakefileThis is a residual of the $FreeBSD$ removal.MFC After: 3 days (though I'll just run the command on the branches)Sponsored by: Netflix List of files: /freebsd/sbin/pfilctl/Makefile Mon, 15 Jul 2024 06:46:32 +0200 Warner Losh <imp@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sbin/pfilctl/Makefile#d0b2dbfa0ecf2bbc9709efc5e20baf8e4b44bbbf Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ List of files: /freebsd/sbin/pfilctl/Makefile Wed, 16 Aug 2023 19:55:03 +0200 Warner Losh <imp@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sbin/pfilctl/Makefile#7cc42f6d25ef2e19059d088fa7d4853fe9afefb5 Do a sweep and remove most WARNS=6 settingsRepeating the default WARNS here makes it slightly more difficult toexperiment with default WARNS changes, e.g. if we did something absolutelybananas and introduced a WARNS=7 and wanted to try lifting the default tothat.Drop most of them; there is one in the blake2 kernel module, but I suspectit should be dropped -- the default WARNS in the rest of the build doesn'tcurrently apply to kernel modules, and I haven't put too much thought intowhether it makes sense to make it so. List of files: /freebsd/sbin/pfilctl/Makefile Thu, 01 Oct 2020 03:10:51 +0200 Kyle Evans <kevans@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sbin/pfilctl/Makefile#c2c227a53646ba18d440c4376b41d8cb94ed0cd7 Merge ^/head r343571 through r343711. List of files: /freebsd/sbin/pfilctl/Makefile Sun, 03 Feb 2019 12:41:43 +0100 Dimitry Andric <dim@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sbin/pfilctl/Makefile#b252313f0b3a4659c02e61d3a0bba471c89bcfa9 New pfil(9) KPI together with newborn pfil API and control utility.The KPI have been reviewed and cleansed of features that were plannedback 20 years ago and never implemented. The pfil(9) internals havebeen made opaque to protocols with only returned types and functiondeclarations exposed. The KPI is made more strict, but at the same timemore extensible, as kernel uses same command structures that userlandioctl uses.In nutshell [KA]PI is about declaring filtering points, declaringfilters and linking and unlinking them together.New [KA]PI makes it possible to reconfigure pfil(9) configuration:change order of hooks, rehook filter from one filtering point to adifferent one, disconnect a hook on output leaving it on input only,prepend/append a filter to existing list of filters.Now it possible for a single packet filter to provide multiple rulesetsthat may be linked to different points. Think of per-interface ACLs inCisco or Juniper. None of existing packet filters yet support that,however limited usage is already possible, e.g. default ruleset canbe moved to single interface, as soon as interface would pride theirfiltering points.Another future feature is possiblity to create pfil heads, that providenot an mbuf pointer but just a memory pointer with length. That wouldallow filtering at very early stages of a packet lifecycle, e.g. whenpacket has just been received by a NIC and no mbuf was yet allocated.Differential Revision: https://reviews.freebsd.org/D18951 List of files: /freebsd/sbin/pfilctl/Makefile Fri, 01 Feb 2019 00:01:03 +0100 Gleb Smirnoff <glebius@FreeBSD.org>