From owner-freebsd-net@FreeBSD.ORG Wed Mar 21 09:05:24 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7A78B16A407 for ; Wed, 21 Mar 2007 09:05:24 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 52C4213C46C for ; Wed, 21 Mar 2007 09:05:24 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id E0D7720A017; Wed, 21 Mar 2007 05:05:17 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Wed, 21 Mar 2007 05:05:17 -0400 X-Sasl-enc: Rtss3CMemqTzEgtD67iEBLqqLv0p+NHkKEXtrCI+qslA 1174467916 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 22A38331AA; Wed, 21 Mar 2007 05:05:16 -0400 (EDT) Message-ID: <4600F54A.10501@FreeBSD.org> Date: Wed, 21 Mar 2007 09:05:14 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Sam Wun References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: MPLS implementation X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2007 09:05:24 -0000 Sam Wun wrote: > Hi, > > Is there any MPLS implementation for FreeBSD? > I found a port ayame mpls for netbsd, but the last implementation was > dated > back to 2003, seems very old. There is NISTswitch, but it is most likely very bit-rotted by now. I would suggest helping Anihudda Bodhra out on the Click port as it would be a great starting point for prototyping MPLS due to how Click will most likely attach to the kernel forwarding paths. The key to success with MPLS is to learn from the layer 2 forwarding stuff in if_bridge; to integrate cleanly with the Ethernet code; to use ALTQ for the token bucket filter and traffic classification policies; and to not break the regular forwarding path. Regards, BMS