Re: moving sockbuf in to its own header

2008-07-20 Thread Kip Macy
Actually, I'd like to re-factor multiple parts of socketvar in to separate files. Please provide feedback on the following: http://www.fsmware.com/socketvar_refactor.diff Thanks, Kip On Sun, Jul 20, 2008 at 3:14 PM, Kip Macy <[EMAIL PROTECTED]> wrote: > TOE drivers need to be able to directly

moving sockbuf in to its own header

2008-07-20 Thread Kip Macy
TOE drivers need to be able to directly enqueue data in to a socket buffer and thus benefit from having knowledge of sockbuf internals. However, there is no need for them to know about other socket definitions. Thus I would like to move sockbuf and accompanying definitions to their own header. Th

Re: OpenLISP

2008-07-20 Thread Luigi Iannone
Le 20-juil.-08 à 21:49, Julian Elischer a écrit : Luigi Iannone wrote: Hi, A word about the implementation. The interception mechanism for LISP tunneled packets in ip_input/forward is *horrible*! Some of that is due to the design, but I believe it can be implemented much cleaner if y

Re: OpenLISP

2008-07-20 Thread Julian Elischer
Luigi Iannone wrote: Hi, A word about the implementation. The interception mechanism for LISP tunneled packets in ip_input/forward is *horrible*! Some of that is due to the design, but I believe it can be implemented much cleaner if you were to use the pfil(9) API. I'd really like to a

Re: OpenLISP

2008-07-20 Thread Luigi Iannone
Hi, A word about the implementation. The interception mechanism for LISP tunneled packets in ip_input/forward is *horrible*! Some of that is due to the design, but I believe it can be implemented much cleaner if you were to use the pfil(9) API. I'd really like to avoid putting this k

Re: OpenLISP

2008-07-20 Thread Max Laier
On Sunday 20 July 2008 20:33:09 Julian Elischer wrote: > Luigi Iannone wrote: > > Hello FreeBSD Networking Community, > > hello to you too :-) > > > The latter approach is the solution chosen by the proponents of the > > Locator/Identifier Separation Protocol (LISP). LISP is a router-based > > solu

Re: OpenLISP

2008-07-20 Thread Luigi Iannone
Hi, Le 20-juil.-08 à 20:33, Julian Elischer a écrit : Luigi Iannone wrote: Hello FreeBSD Networking Community, hello to you too :-) The latter approach is the solution chosen by the proponents of the Locator/Identifier Separation Protocol (LISP). LISP is a router-based solution to sol

Re: OpenLISP

2008-07-20 Thread Julian Elischer
Luigi Iannone wrote: Hello FreeBSD Networking Community, hello to you too :-) The latter approach is the solution chosen by the proponents of the Locator/Identifier Separation Protocol (LISP). LISP is a router-based solution to solve the scaling problems of the Internet architecture that

OpenLISP

2008-07-20 Thread Luigi Iannone
Hello FreeBSD Networking Community, During the last years, there have been many discussions about the scalability of the Internet architecture notably within the IRTF RRG. With IPv6, thanks to its huge addressing space, it is possible to design protocols and mechanisms that are more scalable