public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Breno Jacinto" <breno@freeunix.com.br>
To: linux-bluetooth@vger.kernel.org
Subject: BNEP and Raw Ethernet Sockets
Date: Sat, 3 Jan 2009 07:00:28 -0300	[thread overview]
Message-ID: <2ced936d0901030200y205b1f8fqb758a0483025dea8@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]

Hello,

    I've been trying for a while to make a BNEP network exchange
messages through raw ethernet sockets, but up to now I could not come
with a reasonable explanation of why it is not working. I have done
the following experiments:

1) Build the network according to the BlueZ PAN Howto
(http://bluez.sourceforge.net/contrib/HOWTO-PAN), consisting of 2
nodes, then 3 nodes with bridging.

2) Tested simple UDP broadcasts: worked fine, everyone receives the packet.

3) Tested with Raw Ethernet sockets: Source Node sends, but the frame
simply doesnt seem to reach the destinations (it is also a broadcast,
but a link-layer one).

    The codes I have been testing are attached, if anyone has
experienced the same situation and found a solution, or if anyone is
suspicious about what might be happening, I'd be glad to hear.

    My main suspect is that hand-made Ethernet frames are not what the
BNEP layer is expecting (and thus I see some errors in Wireshark), but
then, what is it that BNEP expects?


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.  ::

[-- Attachment #2: source.tar.gz --]
[-- Type: application/x-gzip, Size: 4207 bytes --]

             reply	other threads:[~2009-01-03 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 10:00 Breno Jacinto [this message]
2009-01-03 15:26 ` BNEP and Raw Ethernet Sockets Luiz Augusto von Dentz
2009-01-04  5:20   ` Breno Jacinto

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=2ced936d0901030200y205b1f8fqb758a0483025dea8@mail.gmail.com \
    --to=breno@freeunix.com.br \
    --cc=linux-bluetooth@vger.kernel.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