|NG_IPFW(4)||Device Drivers Manual||NG_IPFW(4)|
ipfwnode implements interface between ipfw(4) and netgraph(4) subsystems.
ipfwnode supports an arbitrary number of hooks, which must be named using only numeric characters.
ng_ipfwmodule is loaded into the kernel, a single node named ipfw is automatically created. No more
ipfwnodes can be created. Once destroyed, the only way to recreate the node is to reload the
Packets can be injected into netgraph(4) using
commands of the ipfw(8) utility. These commands require a
numeric cookie to be supplied as an argument. Packets are sent out of the
hook whose name equals the cookie value. If no hook matches, packets are
discarded. Packets injected via the
are tagged with struct ipfw_rule_ref. This tag
contains information that helps the packet to re-enter
ipfw(4) processing, should the packet come back from
netgraph(4) to ipfw(4).
Packets received by a node from netgraph(4) subsystem must be tagged with struct ipfw_rule_ref tag. Packets re-enter IP firewall processing at the next rule. If no tag is supplied, packets are discarded.
CONTROL MESSAGES¶This node type supports only the generic control messages.
SHUTDOWN¶This node shuts down upon receipt of a
NGM_SHUTDOWNcontrol message. Do not do this, since the new
ipfwnode can only be created by reloading the
SEE ALSO¶ipfw(4), netgraph(4), ipfw(8), mbuf_tags(9)
ipfwnode type was implemented in FreeBSD 6.0.
ipfwnode was written by Gleb Smirnoff <glebius@FreeBSD.org>.
|March 2, 2010||Linux 4.19.0-10-amd64|