public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Sending own L2CAP packets to HCI
Date: Fri, 21 Jan 2005 01:36:20 +0100	[thread overview]
Message-ID: <1106267780.7955.38.camel@pegasus> (raw)
In-Reply-To: <loom.20050121T013101-9@post.gmane.org>

Hi Matthias,

> i tried to change the l2ping program by using another command header.  
> Instead of L2CAP_ECHO_REQ and L2CAP_ECHO_RES i used L2CAP_CONN_REQ and 
> L2CAP_CONN_RES, because i want to build a full connection with connect, 
> configure and disconnect later... 
> It seemed that it works, but hcidump said that the connect request is 
> rejected.  
> Is it in general possible to inject own L2CAP packets (with configure 
> requests) to a phone by using the l2ping programm. I mean is the socket setup 
> in this program for this use sufficient or do i have to inject the packets 
> directly to the usb driver? Because i think the command reject comes from the 
> Bluez stack and i have to inject the L2CAP packets without using the BlueZ 
> stack? 

you can use the L2CAP raw socket for this, but actually you should read
the Bluetooth specification and understand it.
 
> HCI Command: Create Connection(0x01|0x0005) plen 13 
> 65 CF 93 EE 02 00 18 CC 02 00 00 00 01 
> HCI Event: Command Status(0x0f) plen 4 
> 00 01 05 04 
> HCI Event: Connect Complete(0x03) plen 11 
> 00 29 00 65 CF 93 EE 02 00 01 00 
> HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 
> 29 00 0F 00 
> ACL data: handle 0x0029 flags 0x02 dlen 28 
> L2CAP(s): Connect req: psm 17989 scid 0x4847 

The PSM and the scid are looking wrong.

> HCI Event: Number of Completed Packets(0x13) plen 5 
> 01 29 00 01 00 
> HCI Event: Command Complete(0x0e) plen 6 
> 01 0D 08 00 29 00 
> HCI Event: Page Scan Repetition Mode Change(0x20) plen 7 
> 65 CF 93 EE 02 00 01 
> HCI Event: Max Slots Change(0x1b) plen 3 
> 29 00 05 
> ACL data: handle 0x0029 flags 0x02 dlen 16 
>  
> L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0000 result 2 status 0 

Read the specification. It says that result code 2 means PSM not
supported. See comment above.

Regards

Marcel




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

      reply	other threads:[~2005-01-21  0:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 11:21 [Bluez-devel] Sending own L2CAP packets to HCI Matthias Bruné
2005-01-19 12:09 ` Marcel Holtmann
2005-01-21  0:31   ` [Bluez-devel] " Matthias Brune
2005-01-21  0:36     ` Marcel Holtmann [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=1106267780.7955.38.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox