Linux bluetooth development
 help / color / mirror / Atom feed
From: "Matthias Bruné" <matthiasbrune@gmx.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] RFCOMM: UIH response is splitted into 3 packets
Date: Thu, 17 Feb 2005 11:57:20 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050217T125538-559@post.gmane.org> (raw)

Hi,

i wrote a programm for testing the RFCOMM layer and during a connection
i observed a strange behaviour that could be an implementation error within 
BlueZ?!
My connection is always broken at this point.
The scenario is decsribed during the traces below.
I hope somebody can help me with this problem, because i need a solution 
urgently.

regards
Matthias


command 1 (Request): Set Asynchronous Balanced Mode (SABM)
20050217 12:34:09 port 1047 --> 127.0.0.1 port 8000 4 octet(s)
20050217 12:34:09 000000 03 3f 01 1c                 

command 2 (Response): Unnumbered Acknowledgement (UA)
20050217 12:34:13 port 1047 <-- 127.0.0.1 port 8000 4 octet(s)
20050217 12:34:13 000000 03 73 01 d7             

command 3 (Request): Unnumbered Information with Header Check (UIH)
20050217 12:34:13 port 1047 --> 127.0.0.1 port 8000 14 octet(s)
20050217 12:34:13 000000 03 ef 15 83 11 1c f0 00 ........
20050217 12:34:13 000008 00 9a 02 00 04 70       .....p  


so far so good, but now i get 3 packets response back instead of one with 
14Bytes length:
4 Bytes, 6Bytes and 4 Bytes

command 4_1 (Response): Unnumbered Information with Header Check (UIH)
20050217 12:34:13 port 1047 <-- 127.0.0.1 port 8000 4 octet(s)
20050217 12:34:13 000000 01 ef 15 81             ....    

After the first response, the next request for further connection is made.
But because of the missing 10 Bytes from command 4 the conection is broken down.
Could this be an implementation error within BlueZ?

command 5 (Request): Set Asynchronous Balanced Mode (SABM)
20050217 12:34:13 port 1047 --> 127.0.0.1 port 8000 4 octet(s)
20050217 12:34:13 000000 73 00 00 28            

command 4_2: (Response): Unnumbered Information with Header Check (UIH)
20050217 12:34:13 port 1047 <-- 127.0.0.1 port 8000 6 octet(s)
20050217 12:34:13 000000 11 1c e0 00 00 9a       ......  

command 4_3: (Response): Unnumbered Information with Header Check (UIH)
20050217 12:34:14 port 1047 <-- 127.0.0.1 port 8000 4 octet(s)
20050217 12:34:14 000000 02 00 00 aa             ....  



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2005-02-17 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-17 11:57 Matthias Bruné [this message]
2005-02-21 23:13 ` [Bluez-devel] RFCOMM: UIH response is splitted into 3 packets 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.20050217T125538-559@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