From: "Matthias Bruné" <matthiasbrune@gmx.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Bypass for L2CAP packets
Date: Tue, 25 Jan 2005 11:11:43 +0000 (UTC) [thread overview]
Message-ID: <loom.20050125T121015-316@post.gmane.org> (raw)
Hi Folks,
sorry for a question to the same problem again...
I have a (problem) with the L2CAP layer from BlueZ.
I wrote a program that communicates with a mobile phone by using its own L2CAP
layer (the program builds its own L2CAP packets for protocol testing).
For example I send a valid "connection request" to that phone and the phone
answers with a valid "connection response".
So far so good.
But then the L2CAP layer from BlueZ sends a "command reject", because this
layer doesn´t know about the "connection request" and cannot handle
the "connection response".
Ok, i understand that.
But has anybody an idea how i can communicate with my own L2CAP layer and the
phone only without using the BlueZ L2CAP layer, because the Bluez layer always
prevents a further communication?
Hmm... is in this case the L2CAP RAW socket the solution?
I´m stucked with that problem and i hope anybody as an idea.
Many thanks.
Matthias
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-01-25 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 11:11 Matthias Bruné [this message]
2005-01-25 11:50 ` [Bluez-devel] Bypass for L2CAP packets Xavier Garreau
2005-01-25 12:54 ` Marcel Holtmann
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=loom.20050125T121015-316@post.gmane.org \
--to=matthiasbrune@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox