From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] MAC and OLSR
Date: Tue, 25 Sep 2007 11:20:12 +0200 [thread overview]
Message-ID: <20070925092012.GA31929@hrz.tu-chemnitz.de> (raw)
In-Reply-To: <46F84B93.2080702@toyota-ti.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 2456 bytes --]
Currently you should use the batman-saxnet branch for batman-advanced, it
features bridging and some other fixes which are not merged back yet.
Use subversion to check out:
svn co https://dev.open-mesh.net/svn/batman/batman-saxnet/
Regards
Simon
On Tue, Sep 25, 2007 at 08:43:15AM +0900, giuseppe de marco wrote:
> Simon Wunderlich wrote:
> >Hello,
> >
> >maybe you already noticed, but we implemented batman on layer 2,
> >called batman-advanced. It uses MAC-addresses as identifies, sends
> >protocol information and payload in own ethernet frames and does the
> >whole switching/routing part on its own. Maybe you want to have a look.
> >:)
> >
> >For your question, i don't know but a guess would be to look in the
> >wireless-tools accesible information and the driver itself.
> >
> >Regards
> > Simon
> >
> >
> >On Fri, Sep 21, 2007 at 10:28:10AM +0900, giuseppe de marco wrote:
> >
> >>I agree that OLSR and also BATMAN should be moved to link layer.
> >>Anyway, now I am trying to do some experiment with OLSR and BATMAN, but
> >>by using also the information of MAC layer.
> >>I am using linux and ieee80211. Does anybody know how to read the mac
> >>parameters, such as
> >>lost frames, number of retransmission and so on?
> >>Regards
> >>
> >>--
> >>Giuseppe De Marco, PhD
> >>Toyota Technological Institute
> >>468-8511 Aichi 2-12-1 Hisakata, Tenpaku-ku,
> >>Nagoya, Japan
> >>Email: demarco at toyota-ti dot ac dot jp
> >>Tel (int): +81 (052)-809-1802
> >>Skype-Id: giuseppe_dem2
> >>
> >>_______________________________________________
> >>B.A.T.M.A.N mailing list
> >>B.A.T.M.A.N@open-mesh.net
> >>https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
> >>
> >>------------------------------------------------------------------------
> >>
> >>_______________________________________________
> >>B.A.T.M.A.N mailing list
> >>B.A.T.M.A.N@open-mesh.net
> >>https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
> >>
> Where I can download the code from?
> G
>
>
> --
> Giuseppe De Marco, PhD
> Toyota Technological Institute
> 468-8511 Aichi 2-12-1 Hisakata, Tenpaku-ku,
> Nagoya, Japan
> Email: demarco at toyota-ti dot ac dot jp
> Tel (int): +81 (052)-809-1802
> Skype-Id: giuseppe_dem2
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-09-25 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 1:28 [B.A.T.M.A.N.] MAC and OLSR giuseppe de marco
2007-09-21 9:40 ` Simon Wunderlich
2007-09-24 23:43 ` giuseppe de marco
2007-09-25 1:07 ` Karl Wagner
2007-09-25 9:20 ` Simon Wunderlich [this message]
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=20070925092012.GA31929@hrz.tu-chemnitz.de \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/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