From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Raw Sockets
Date: Tue, 24 May 2005 19:06:52 +0200 [thread overview]
Message-ID: <1116954412.30044.154.camel@pegasus> (raw)
In-Reply-To: <6951a38b0505240932769defa9@mail.gmail.com>
Hi Nuno,
> I'm writting from Portugal and I'm developing an application with
> bluez. This application's objective is to develop an program to
> receive data from several bluetooth devices and create a Data Base
> with that information. I need to use Raw Sockets, so I can create
> specific headers for the bluetooth packets.
>
> Rigth now I'm having some problems using this raw sockets... So, I
> have some questions...
> 1 - How can I capture bluetooth packets using Raw Sockets?
> 2 - What kind of structure do I need to use to manage the packets (in
> sockets tcp/ip we use specific structures to receive/send packets)
> 3 - Can I capture all the packets or just the packets sent to my
> bluetooth device??
what makes you think that you need raw sockets. I don't see any need for
it. Write a client/server application that communicates over L2CAP or
RFCOMM.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-24 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 16:32 [Bluez-devel] Raw Sockets Nuno Gomes
2005-05-24 17:06 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-25 17:16 Nuno Gomes
2005-05-25 17:22 ` Marcel Holtmann
2005-05-25 18:56 ` Nuno Gomes
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=1116954412.30044.154.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.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 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.