[TEST/REVIEW] ng_ipfw: node to glue together ipfw(4) and netgraph(4)

Gleb Smirnoff glebius at freebsd.org
Wed Jan 19 01:36:16 PST 2005

On Wed, Jan 19, 2005 at 01:32:35AM -0800, Julian Elischer wrote:
J> If each active divert socket number had a pointer to the module to which it
J> was attached then  you could divert to either in-kernel netgraph targets or
J> to userland socket based targets.  Currently of you divert to a divert
J> 'port number' and nothing is attached to it, the packet is dropped.
J> If a divert socket is attached to it, it is sent ot teh socket.
J> I would just suggest that is not a great leap of imagination that
J> attaching to a hook named 3245 would attach a netgrpah hook to the ipfw
J> code in the sam enamespace as the divert portnumber, and that a
J> subsequent attempt to attach a divert socket to that port number woild
J> fail. The packets diverted there would simply go to the netgraph hook
J> instead of going to a socket or being dropped.

I understand your idea now. I'll work in this direction.

Totus tuus, Glebius.

More information about the freebsd-net mailing list