public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Stefan Seyfried <stefan.seyfried@googlemail.com>
Cc: BlueZ devel list <linux-bluetooth@vger.kernel.org>
Subject: Re: BNEP problem, hardware dependent?
Date: Wed, 16 Sep 2009 15:48:11 -0300	[thread overview]
Message-ID: <2d5a2c100909161148h7d15ebf2g1fecc84e670480f7@mail.gmail.com> (raw)
In-Reply-To: <20090916181902.52bf7e99@strolchi.home.s3e.de>

Hi Stefan,

On Wed, Sep 16, 2009 at 1:19 PM, Stefan Seyfried
<stefan.seyfried@googlemail.com> wrote:
> Hi,
>
> recently I was changing my work machine. When I wanted to do my usual
> setup (hacked up test-network script) to connect to the internet via my
> mobile phone, I got "bnep error".
>
> It is this piese of code in network/connection.c:
>
> 270         if (rsp->ctrl != BNEP_SETUP_CONN_RSP)
> 271                 return TRUE;
> 272
> 273         r = ntohs(rsp->resp);
> 274
> 275         if (r != BNEP_SUCCESS) {
> 276                 error("bnep failed");
> 277                 goto failed;
> 278         }

Weird, are you sure that it is failing in one of those checks? It
never happened to me before, you just switch dongle, right?

> I then found out that it did work with some dongles, and it did not
> work with others. Apparently there was no connection to the "quality"
> of the dongles (but I have to admit, that AFAIR all were broadcom or
> worse), there was a very cheap one that did work and more expensive
> ones that didn't.

Make sure you did paired with device before attempting to connect, you
can also mark it as trusted so it does ask for confirmation, if it
still fail could you please send us the hcidump and bluetooth output?

> I always thought that the "supported profiles" list on the packaging
> was just a "what we licensed in the driver" list and that all hardware
> could do everything.
>
> Am I wrong?

Nope, you are correct, the hardware should not affect much the
profiles, of course profiles depending on things like SCO may be
affected by the hardware but that's it. IIRC the only special
requirement for BNEP is that the MTU should be configured to 1691.
(this is easy to check with hcidump)


-- 
Luiz Augusto von Dentz
Engenheiro de Computação

  reply	other threads:[~2009-09-16 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 16:19 BNEP problem, hardware dependent? Stefan Seyfried
2009-09-16 18:48 ` Luiz Augusto von Dentz [this message]
2009-09-18 10:07   ` Stefan Seyfried
2009-09-18 10:46     ` Stefan Seyfried

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=2d5a2c100909161148h7d15ebf2g1fecc84e670480f7@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=stefan.seyfried@googlemail.com \
    /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