> It's only truly associative with the socket itself, if you think about it.
> I'd like to see
> what David thinks about this change, since networking is seemingly 'his'
> where IPFW is
> 'yours'.
nothing is mine, and certainly not IPFW -- i merely added the dummynet
hooks!
> > On the ipfw side, yes i think the switch to locate & check credential
> > can be simplified by merging the final part (and perhaps even the
> > in_pcblookup() calls).
>
> Yes, I think I'll clean up ipfw :) Parts of it are due for a rewrite, as the
> code has grown
> unwieldly.
correct. however, with rules being so "complex" (lots of things you can
specify in a rule) the kernel part cannot be simplified a lot. The
userland code, on the other hand, would really deserve some cleanup!
cheers
luigi
-----------------------------------+-------------------------------------
Luigi RIZZO, lu...@iet.unipi.it . Dip. di Ing. dell'Informazione
http://www.iet.unipi.it/~luigi/ . Universita` di Pisa
TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy)
http://www.iet.unipi.it/~luigi/ngc99/
==== First International Workshop on Networked Group Communication ====
-----------------------------------+-------------------------------------
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
