linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Valsecchi <patrick@thus.ch>
To: linux-bluetooth@vger.kernel.org
Subject: RFCOMM connection failing
Date: Mon, 16 Dec 2013 16:55:57 +0100	[thread overview]
Message-ID: <52AF228D.1000608@thus.ch> (raw)

Hi,

I'm trying to connect my PC:
     Linux ... 3.11.0-14-generic #21-Ubuntu SMP ... x86_64 x86_64 x86_64 
GNU/Linux
     0a5c:2198 Broadcom Corp. Bluetooth 3.0 Device

To connect with my bluetooth dive computer:
     Shearwater Petrel

It fails with a "Transport endpoint is not connected (107)" most of the 
time or go further but seem to have corrupted RFCOMM payload.

If I pass the USB device to a W7 VM (virtualbox) and try from them, the 
communication works like charm.

So I went ahead and sniffed the USB communication in both cases using 
wireshark. The two dumps () can be found here (UsbDumpFrom*.pcapng, can 
be open using wireshark):
https://cloud.thus.ch/public.php?service=files&t=de2eabf30c82efa08cf546ff5045e585

Basically the Linux one is just stopping at frame 203 where it sends a 
RFCOMM SABM, gets the answer and reports an error to the user. The 
windows dump show the same RFCOMM SABM command in frame 191 and gets the 
same answer but continues and everything works.

On IRC aholler told me you guys would prefer to get a btmon dump with 
bluez v5. So I went ahead, installed bluez 5.12 and generated a dump 
(yes, the comm still fails the same way) that you can find in the same 
location as the dumps.

I'm stuck there. Can somebody help me go further?

Thanks

             reply	other threads:[~2013-12-16 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 15:55 Patrick Valsecchi [this message]
2014-01-01  8:34 ` RFCOMM connection failing Patrick Valsecchi

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=52AF228D.1000608@thus.ch \
    --to=patrick@thus.ch \
    --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;
as well as URLs for NNTP newsgroup(s).