public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.net
Cc: olsr list users mailing <olsr-users@lists.olsr.org>
Subject: Re: [B.A.T.M.A.N.] point me to some OSI layer diagrams if possible ?
Date: Thu, 10 Dec 2009 12:00:33 +0800	[thread overview]
Message-ID: <200912101200.33322.lindner_marek@yahoo.de> (raw)
In-Reply-To: <15EDF7F5-2A4A-4A77-87F4-193AFAA1B7CD@lo-res.org>

On Thursday 10 December 2009 07:40:53 L. Aaron Kaplan wrote:
> | link, 802.11s, B.A.T.M.A.N  layer 2 version, OLPC's  802.11s|  2    the
> | HWMP and all the 80.211s stuff resides here. 802.11a/b/g/n resides here.
> | Madwifi, ath5k and ath9k reside here. 

Sorry, but that is not (entirely) correct. It is no problem calling batman-adv 
a layer 2 protocol for the sake of simplicity (it deals with MAC addresses 
instead of IP addresses, etc ..). But if you mention batman-adv and 
802.11s/ath5k/etc in the same sentence you have to be more precise as they do 
not operate on the same layer.

batman-adv is layer 2.5 and runs on top of all ethernet based layer 2 
protocols which means you can run it over wireless 
(managed/adhoc/mesh/whatever mode), plain ethernet cable, VPNs and so on.

However, 802.11s is "true" layer 2 and as such is limited to the medium 
(wireless) as well as to the hardware & drivers. 


Regards,
Marek

  reply	other threads:[~2009-12-10  4:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 20:42 [B.A.T.M.A.N.] point me to some OSI layer diagrams if possible ? George Sanders
2009-12-09 23:40 ` L. Aaron Kaplan
2009-12-10  4:00   ` Marek Lindner [this message]
2009-12-10  4:28     ` [B.A.T.M.A.N.] [Olsr-users] point me to some OSI layer diagramsif " Bhat, Ishwara
2009-12-10  4:33       ` Marek Lindner
2009-12-10  4:55         ` Bhat, Ishwara
2009-12-10  9:41           ` L. Aaron Kaplan

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=200912101200.33322.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    --cc=olsr-users@lists.olsr.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox