From owner-freebsd-net@FreeBSD.ORG Sun Mar 17 18:57:35 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C863E7D0 for ; Sun, 17 Mar 2013 18:57:35 +0000 (UTC) (envelope-from melifaro@FreeBSD.org) Received: from mail.ipfw.ru (unknown [IPv6:2a01:4f8:120:6141::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8DA2BE03 for ; Sun, 17 Mar 2013 18:57:35 +0000 (UTC) Received: from v6.mpls.in ([2a02:978:2::5] helo=ws.su29.net) by mail.ipfw.ru with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1UHIpL-000DQY-1V; Sun, 17 Mar 2013 23:01:03 +0400 Message-ID: <5146121B.5080608@FreeBSD.org> Date: Sun, 17 Mar 2013 22:57:31 +0400 From: "Alexander V. Chernikov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120121 Thunderbird/9.0 MIME-Version: 1.0 To: Sami Halabi Subject: Re: MPLS References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Mar 2013 18:57:35 -0000 On 17.03.2013 13:20, Sami Halabi wrote: > any one? :) > > > On Fri, Mar 15, 2013 at 6:28 PM, Sami Halabi wrote: > >> Hi, >> Are there ongoing job of mpls in freebsd? >> I saw thd site http://freebsd.mpls.in for aboug a year now and I don't >> see much progress. Yep. It was frozen for a while. Currently I'm working on it again. control plane code was heavily redesigned, see http://bird.mpls.in/projects/mpls-bird/repository/show?rev=bird_mpls I have some working MPLS code on 8-S and I hope to create freebsd svn branch with base MPLS support in 2-3 weeks. >> ITOH OpenBSD has a complete implementation of MPLS out of the box, maybe Their control plane code is mostly useless due to design approach (routing daemons talk via kernel). Their data plane code, well.. Yes, we can use some defines from their headers, but that's all :) >> porting it would be short and more straight forward than porting linux LDP >> implementation of BIRD. It is not 'linux' implementation. LDP itself is cross-platform. The most tricky place here is control plane. However, making _fast_ MPLS switching is tricky too, since it requires chages in our netisr/ethernet handling code. >> >> Thanks in advance, >> Sami >> > > >