cvs commit: src/sys/contrib/pf/net if_pflog.c if_pflog.h if_pfsync.c if_pfsync.h pf.c pf_ioctl.c pf_norm.c pf_osfp.c pf_table.c pfvar.h src/sys/contrib/pf/netinet in4_cksum.c

[Luigi Rizzo]

On Fri, Feb 27, 2004 at 09:53:22AM +0100, Dag-Erling Smørgrav wrote:
> Luigi Rizzo <rizzo at icir.org> writes:
> > I believe this (convert the entire networking stack to netgraph
> > nodes) is completely unfeasible.
> 
> It shouldn't be.  Open any textbook on computer networking and you'll
> find that netgraph is the canonical way to organize a protocol stack.

except that textbooks are usually written by academics (like me)
and tend to forget 'details' such as control interfaces
(which typically talks to all layers) and interacting with
the rest of the system.

> > There are interactions among subsystems all over the place.
> 
> Otherwise known as "layering violations" and "bugs".
> 
> > The routing subsystem is used by all protocols at different
> > layers (arp, ipv4 and ipv6, probably more). TCP knows it runs
> > on top of IP and pokes into its data structures below. It also
> > plays with the socket buffers on the layer above.
> 
> Repeat after me: "layering violations"

whatever. Are you going to fix them ?

	cheers
	luigi
> DES
> -- 
> Dag-Erling Smørgrav - des at des.no