From: Breno Jacinto <breno@freeunix.com.br>
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.] B.A.T.M.A.N L2 over a Bluetooth PAN
Date: Fri, 13 Feb 2009 21:28:24 -0300 [thread overview]
Message-ID: <2ced936d0902131628x43ffb22eh712ec9addc03699c@mail.gmail.com> (raw)
In-Reply-To: <20090213141846.GA17394@pandem0nium>
Hello Simon,
Thank you for the insightful comment. I'll check this out and get
back to the list.
regards,
2009/2/13 Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>:
> Hello Breno,
>
> as far as i know, for 802.11 the SNAP protocol is used to encapsulate
> the complete Ethernet Frame [1]. This means that the Ethernet header is
> completly preserved and can be decapsulated on the receiver side.
> The BNEP protocol on the other hand seems to cut off the Ethernet header
> instead of encapsalutating it when i understand the specification
> correctly [2, page 13]. However the examples [2, page 15 and page 41]
> suggest that the Ethernet Header is encapsulated completly within BNEP.
>
> For batman-adv a correct Ethernet Header, especially correct MAC Addresses
> to identify the peers and support for our specific Ethernet Type is
> needed. If these fields are not (re-)generated correctly, it won't work.
>
> So the question is: is BNEP even transporting arbitrary frames with
> Ethertypes other than IP (0x0800)? Maybe there are some filters
> preventing the BATMAN frames (type 0x4305) to be transported
> [2, page 42]?
>
> I guess a good starting point would be to use some bluetooth dump tools
> or tcpdump, inject packets and see if they are received on the peer
> site. Maybe just some filter is preventing batman-adv from operation. :)
>
> best regards,
> Simon
>
>
> [1] http://osnet.inm.nchu.edu.tw/powpoint/seminar/802.11/802.11MAC.pdf (slide 28)
> [2] http://grouper.ieee.org/groups/802/15/Bluetooth/BNEP.pdf
>
> On Thu, Feb 12, 2009 at 11:42:44PM -0300, Breno Jacinto wrote:
>> Hello,
>>
>> I'm experimenting on heterogeneous ad hoc networks, which today
>> are still very restricted in terms of hardware availability for
>> off-the-shelf devices. Actually, the two most common technologies
>> available today are 802.11 and Bluetooth, being this last one able to
>> form simple personal area networks in the form of piconets.
>>
>> In practical terms, the BlueZ stack of the Linux allows the
>> formation of Bluetooth PANs consisting of up to 8 nodes, but it's an
>> incredibly difficult process - actually, the piconet master needs to
>> bridge connections so that all other devices in the network, which
>> depend on this master, are able to reach it other directly - or at
>> least feel like they are doing that. In fact, everything is just an
>> emulation, since Bluetooth is a connection-oriented technology.
>>
>> BNEP (Bluetooth Network Encapsulation Protocol) is the piece
>> responsible for emulating an Ethernet network over Bluetooth, and
>> theoretically any IP and above protocols can be used. Trying with
>> simple IP broadcasts over a Bluetooth network shows that it works, but
>> the problem comes when I try to do "straight" layer 2 broadcasts (not
>> coming from the IP layer), such as the ones that BATMAN L2 does.
>>
>> I tried to run BATMAN and add the interfaces used on each device -
>> pan0 for the master, which is a bridge device, and bnep0 for the
>> slave, but the frame dont seem to reach any destination on the
>> network. The originators table remains empty on both sides of the
>> connection. Running Wireshark shows the frame being generated, but
>> never reaching anyone.
>>
>> So, I still cannot figure out why this is happening. I'd like to
>> know if anyone has adventured in doing something similar and
>> succeeded.
>>
>>
>> best regards,
>>
>> --
>> --
>> :: Breno Jacinto ::
>> :: breno - at - gprt.ufpe.br ::
>> :: FingerPrint ::
>> 2F15 8A61 F566 E442 8581
>> E3C0 EFF4 E202 74B7 7484
>> :: Persistir no difícil é a única maneira de torná-lo fácil algum dia. ::
>> _______________________________________________
>> B.A.T.M.A.N mailing list
>> B.A.T.M.A.N@open-mesh.net
>> https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFJlYFGrzg/fFk7axYRAmIEAJwN2joajajVtRo2bw8vv5x3EImdbwCg21WU
> iyolzJNbEPn7tMKMutqVaQc=
> =Sq9K
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>
>
--
--
:: Breno Jacinto ::
:: breno - at - gprt.ufpe.br ::
:: FingerPrint ::
2F15 8A61 F566 E442 8581
E3C0 EFF4 E202 74B7 7484
:: Persistir no difícil é a única maneira de torná-lo fácil algum dia. ::
prev parent reply other threads:[~2009-02-14 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 2:42 [B.A.T.M.A.N.] B.A.T.M.A.N L2 over a Bluetooth PAN Breno Jacinto
2009-02-13 14:18 ` Simon Wunderlich
2009-02-14 0:28 ` Breno Jacinto [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=2ced936d0902131628x43ffb22eh712ec9addc03699c@mail.gmail.com \
--to=breno@freeunix.com.br \
--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