jamal wrote:
Essentially you are extending the broadcast domain i.e a bridge within
on top of a bridge. I would question the scalability of such a beast
in the presence of many nodes. Also take a look at some of the work
Radia Perlman (who invented bridging really) is up to these days.
Hi J
Hi Pavel
(I've removed linux-kernel from CC, this is only network related and
added Herman to the CC, since he's not subscribed)
Pavel Machek wrote:
Hi!
FLAME stands for "Forwarding Layer for Meshing"
FLAME provides an intermediate layer between the network
layer (e.g. IPv4/IPv6) and the
Stephen Hemminger wrote:
On Tue, 23 May 2006 16:07:47 +0200
Herman Elfrink <[EMAIL PROTECTED]> wrote:
FLAME stands for "Forwarding Layer for Meshing"
Didn't you just reinvent 802.1d bridging? and/or WDS?
I wouldn't say "reinvent", but the difference is small but significant.
FLAME could
Erik Mouw wrote:
On Tue, May 23, 2006 at 04:41:48PM +0200, Simon Oosthoek wrote:
Alan Cox wrote:
On Maw, 2006-05-23 at 16:07 +0200, Herman Elfrink wrote:
FLAME uses an unofficial protocol number (0x4040), any tips on how to
get an official IANA number would be highly appreciated.
Ethernet
Stephen Hemminger wrote:
O
Usage
=
- Load module:
modprobe flame [debuglevel=] [flm_topo_timer=]
: debug level, default: 1
: topology check timer (in seconds), default: 5
- Open/close a device with:
echo "up []" > /proc/net/flame/cmd
echo "down " > /proc/net/flame/
Alan Cox wrote:
On Maw, 2006-05-23 at 16:07 +0200, Herman Elfrink wrote:
FLAME uses an unofficial protocol number (0x4040), any tips on how to
get an official IANA number would be highly appreciated.
Ethernet protocol number I assume you mean. If so this at least used to
be handled by the IE
