OpenLISP
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 and more powerful than with IPv4. A typical example is the multihoming problem. This problem occurs when a site is attached to several Internet Service providers. With IPv4, the classical solution is for the site to obtain one IPv4 prefix and advertise it by using BGP. This solution works and traffic engineering is possible, but unfortunately, it contributes to a significant growth of the BGP routing tables in the global Internet. Approaches to better scale the Internet architecture are being discussed, notably within the Routing Research Group of the Internet Research Task Force. Several of these approaches rely on separating the two roles of IP addresses: the locator role and the identifier role. In today's IPv4 Internet, IPv4 addresses are used both to indicate the location in the Internet topology of a host (the locator role) and to terminate the transport flows on end-hosts (the identifier role). This means that it is difficult to change the IP address of a host without disrupting transport flows. The techniques that separate identifiers from locators take a different approach. First, an identifier is attached to each end- host. This identifier is used to terminate the transport flows. Second, each identifier may be reachable through multiple locators and a mapping mechanism is used to map an identifier (or a set of identifiers) onto a set of locators. This improves the scalability of the routing system as only the locators need to be distributed by BGP provided, of course, that the mapping system remains scalable. Furthermore, separating identifiers and locators has several additional benefits in terms of path diversity and performance. Some approaches propose to attach locators to hosts while other prefer to attach locators only to routers. 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 is currently being developed by Cisco. There are still many open questions concerning notably the mapping between identifiers and locators. To allow researchers and network operators to experiment with LISP, the IP Networking Lab of UCLouvain releases OpenLISP. OpenLISP is the first publicly available implementation of LISP on the FreeBSD kernel. OpenLISP was designed and implemented by Luigi Iannone. You can find more details about OpenLISP from http://inl.info.ucl.ac.be Any feedback from the FreeBSD Networking community is more than welcome. Best regards, Luigi Iannone [EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OpenLISP
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 solve the scaling problems of the Internet architecture that is currently being developed by Cisco. Couldn't possibly come up with a better acronym? "lisp" is kinda taken.. are there any documents with PICTURES you can recommend to us? Well, the official document can be found here: http://www.ietf.org/internet-drafts/draft-farinacci-lisp-08.txt If you want some _pictures_ you can get a look here: http://rosie.ripe.net/ripe/meetings/ripe-56/presentations/uploads/ Tuesday/Plenary%2016:00/upl/Fuller-LISP_Intro_and_Update.gNyX.pps Does this connect at all with SCTP's capacity to multihome? Not really. As far as I know SCTP is an end-to-end solution, where end-to-end stand for end-hosts. LISP is meant to be deployed mainly on border routers of stub domains. Cheers Luigi [EMAIL PROTECTED] Luigi Iannone [EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OpenLISP
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 kind of stuff into the main ip code as it hurts readability a lot. Thanks for the hint I'll get a look at that. Cheers Luigi -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]" Luigi Iannone [EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OpenLISP
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 you were to use the pfil(9) API. I'd really like to avoid putting this kind of stuff into the main ip code as it 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 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 "[EMAIL PROTECTED]" Luigi Iannone [EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
MPLS
Hi! I developped a basic implementation of MPLS over Ethernet in the FreeBSD Environment! If someone is interested in my code just e.mail me! Bye Luigi Iannone > Luigi Iannone LIP 6 : Laboratoire d'Informatique de Paris VI 8, Rue du Capitaine Scott 75015 Paris France E-mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Host AP porting!!!
Hi, Can anyone tell me if there exist a port of the HostAP software on freebsd (any version)??? Thank you all Ciao Luigi > Luigi Iannone - Laboratoire D'Informatique Paris 6 e.mail: [EMAIL PROTECTED] Tel: +33 (0)1 44 27 88 48 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
