p Packet filtering points are registered with .Fn pfil_head_register . Filtering points are identified by a key (void *) and a data link type (int) in the .Em pfil_head structure. Packet filters use the key and data link type to look up the filtering point with which they register themselves. The key is unique to the filtering point. The data link type is a .Xr bpf 4 DLT constant indicating what kind of header is present on the packet at the filtering point. Filtering points may be unregistered with the .Fn pfil_head_unregister function.
p Packet filters register/unregister themselves with a filtering point with the .Fn pfil_add_hook and .Fn pfil_remove_hook functions, respectively. The head is looked up using the .Fn pfil_head_get function, which takes the key and data link type that the packet filter expects. Filters may provide an argument to be passed to the filter when invoked on a packet.
p When a filter is invoked, the packet appears just as if it .Dq came off the wire . That is, all protocol fields are in network byte order. The filter is called with its specified argument, the pointer to the pointer to the mbuf containing the packet, the pointer to the network interface that the packet is traversing, and the direction .Dv ( PFIL_IN or .Dv PFIL_OUT , see also below) that the packet is traveling. The filter may change which mbuf the mbuf ** argument references. The filter returns an errno if the packet processing is to stop, or 0 if the processing is to continue. If the packet processing is to stop, it is the responsibility of the filter to free the packet.
p The .Em flags parameter, used in the .Fn pfil_add_hook and .Fn pfil_remove_hook functions, indicates when the filter should be called. The flags are: l -tag -offset indent -width PFIL_WAITOK -compact t PFIL_IN call me on incoming packets t PFIL_OUT call me on outgoing packets t PFIL_ALL call me on all of the above t PFIL_IFADDR call me on interface reconfig (mbuf ** is ioctl #) t PFIL_IFNET call me on interface attach/detach (mbuf ** is either .Dv PFIL_IFNET_ATTACH or .Dv PFIL_IFNET_DETACH ) t PFIL_WAITOK OK to call malloc with M_WAITOK. .El
p The .Nm interface is enabled in the kernel via the .Sy PFIL_HOOKS option. .Sh SEE ALSO .Xr bpf 4 .Sh HISTORY The .Nm interface first appeared in .Nx 1.3 . The .Nm input and output lists were originally implemented as .Aq Pa sys/queue.h .Dv LIST structures; however this was changed in .Nx 1.4 to .Dv TAILQ structures. This change was to allow the input and output filters to be processed in reverse order, to allow the same path to be taken, in or out of the kernel.
p The .Nm interface was changed in 1.4T to accept a 3rd parameter to both .Fn pfil_add_hook and .Fn pfil_remove_hook , introducing the capability of per-protocol filtering. This was done primarily in order to support filtering of IPv6.
p In 1.5K, the .Nm framework was changed to work with an arbitrary number of filtering points, as well as be less IP-centric. .Sh AUTHORS The .Nm interface was designed and implemented by Matthew R. Green, with help from Darren Reed, Jason R. Thorpe and Charles M. Hannum. Darren Reed added support for IPv6 in addition to IPv4. Jason R. Thorpe added support for multiple hooks and other clean up. .Sh BUGS The current .Nm implementation will need changes to suit a threaded kernel model.