for your help on this issue.
Herman.
Herman Elfrink wrote:
An attempt to clear up the confusion that seems to have occurred:
FLAME is an intermediate layer between existing MAC and network (IP)
layers.
From MAC layer point of view FLAME is another network layer protocol
(besides IP, IPX etc
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 link (MAC) layer,
providing L2.5 meshing. Both network layer and MAC layer
What is wrong with meshing on L3?
(It is cal
Stephen Hemminger wrote:
Didn't you just reinvent 802.1d bridging? and/or WDS?
Hi Stephen,
Yes, more or less, but with a twist.
802.1D does not allow retransmitting over the same interface (which is
what basically happens in mesh networks), and WDS uses static
configuration of neighbou
layer (IANA) protocol number.
From IP point of view FLAME behaves like a 'normal' ethernet-type MAC
layer; no need for new IEEE protocol number.
Regards,
Herman Elfrink.
Alan Cox wrote:
On Maw, 2006-05-23 at 16:55 +0200, Erik Mouw wrote:
Ethernet protocol number I assume you m
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 can be used unchanged: to the network layer
FLAME appears as a normal Ethernet-typ
