All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herman Elfrink <herman.elfrink@ti-wmc.nl>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@vger.kernel.org, Simon Oosthoek <simon.oosthoek@ti-wmc.nl>
Subject: Re: [ANNOUNCE] FLAME: external kernel module for L2.5 meshing
Date: Tue, 30 May 2006 09:01:51 +0200	[thread overview]
Message-ID: <447BEDDF.2080301@ti-wmc.nl> (raw)
In-Reply-To: <20060523094324.11926fcc@localhost.localdomain>

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 neighbouring hops (we want to support dynamically 
changing configurations).

Regards,

Herman.

  parent reply	other threads:[~2006-05-30  7:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23 14:07 [ANNOUNCE] FLAME: external kernel module for L2.5 meshing Herman Elfrink
2006-05-23 14:38 ` Stephen Hemminger
2006-05-23 14:51   ` Simon Oosthoek
2006-05-23 15:09     ` Steven Rostedt
2006-05-23 15:20     ` Alan Cox
2006-05-23 14:48 ` Alan Cox
2006-05-23 14:41   ` Simon Oosthoek
2006-05-23 14:55     ` Erik Mouw
2006-05-23 15:00       ` Simon Oosthoek
2006-05-23 15:14       ` Alan Cox
2006-05-30  6:42         ` Herman Elfrink
2006-05-30  8:43           ` Herman Elfrink
2006-05-23 16:43 ` Stephen Hemminger
2006-05-23 17:43   ` Simon Oosthoek
2006-05-24 18:43     ` jamal
2006-05-25 10:53       ` Simon Oosthoek
2006-05-25 15:38         ` jamal
2006-05-30  7:01   ` Herman Elfrink [this message]
2006-05-24 20:50 ` Pavel Machek
2006-05-25  9:36   ` Simon Oosthoek
2006-05-30  8:29   ` Herman Elfrink

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=447BEDDF.2080301@ti-wmc.nl \
    --to=herman.elfrink@ti-wmc.nl \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.org \
    --cc=simon.oosthoek@ti-wmc.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.