From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pavel Machek <pavel@ucw.cz>
Subject: Re: [ANNOUNCE] FLAME: external kernel module for L2.5 meshing
Date: Wed, 24 May 2006 20:50:35 +0000
Message-ID: <20060524205035.GA4149@ucw.cz>
References: <44731733.7000204@ti-wmc.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Return-path: <netdev-owner@vger.kernel.org>
Received: from gprs189-60.eurotel.cz ([160.218.189.60]:63759 "EHLO
	spitz.ucw.cz") by vger.kernel.org with ESMTP id S932386AbWEXUus
	(ORCPT <rfc822;netdev@vger.kernel.org>);
	Wed, 24 May 2006 16:50:48 -0400
To: Herman Elfrink <herman.elfrink@ti-wmc.nl>
Content-Disposition: inline
In-Reply-To: <44731733.7000204@ti-wmc.nl>
Sender: netdev-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

Hi!

> FLAME stands for "Forwarding Layer for Meshing"
> 
> FLAME provides an intermediate layer between the network 
> layer (e.g. IPv4/IPv6) and the link (MAC) layer, 
> providing L2.5 meshing. Both network layer and MAC layer 

What is wrong with meshing on L3?

(It is called flame so lets at least have nice flamewar :-)
							Pavel
-- 
Thanks for all the (sleeping) penguins.