Date: Sun, 20 Jul 2008 21:56:34 +0200 From: Luigi Iannone <Luigi.Iannone@uclouvain.be> To: Julian Elischer <julian@elischer.org> Cc: Max Laier <max@love2party.net>, Olivier Bonaventure <olivier.bonaventure@uclouvain.be>, freebsd-net@freebsd.org Subject: Re: OpenLISP Message-ID: <E31140E2-B62F-4B4B-A2BA-7EAEBBC6C5B4@uclouvain.be> In-Reply-To: <488396CE.1060008@elischer.org> References: <AAC239F7-5483-4C9A-9C7B-FC4DF524EDB7@uclouvain.be> <488384E5.3060608@elischer.org> <200807202051.04431.max@love2party.net> <4711A2FE-DFB4-44C0-9FA6-D69BD1B05C2E@uclouvain.be> <488396CE.1060008@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 20-juil.-08 =E0 21:49, Julian Elischer a =E9crit : > Luigi Iannone wrote: >>> >> Hi, >>> A word about the implementation. The interception mechanism for =20 >>> LISP tunneled packets in ip_input/forward is *horrible*! Some of =20= >>> that is due to the design, but I believe it can be implemented =20 >>> much cleaner if you were to use the pfil(9) API. I'd really like =20= >>> to avoid putting this kind of stuff into the main ip code as it =20 >>> hurts readability a lot. >>> >> Thanks for the hint I'll get a look at that. > > my head hurts after reading that :-) > > I think I only 'got' half of it.. > I'll read it again later.. > The aim of this is to reduce routing table size and allow multihoming > You got it. > with the destination being able to suggest to a remote sight how to =20= > route back to it right? > or at least suggest where to go through ... L. > >> Cheers >> Luigi > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" Luigi Iannone luigi.iannone@uclouvain.be
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E31140E2-B62F-4B4B-A2BA-7EAEBBC6C5B4>