public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Chan-Yeol Park <chanyeol.park@samsung.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Issues in PANU
Date: Thu, 26 Feb 2009 17:03:22 +0100	[thread overview]
Message-ID: <1235664202.27004.18.camel@localhost.localdomain> (raw)
In-Reply-To: <002401c99813$685521a0$38ff64e0$%park@samsung.com>

Hi,

> I have been working with PANU profile contained in BlueZ 4.30.
> 
> Whenever I try to connect NAP,I see the following message,
> "
> pan1 connected
> pan1 disconnected."

the pan1 suppose to be the bridge interface bluetoothd tries to connect
all its bnepX interface too.

> As you may know, the first line message is located in bnep_connect_cb(). and
> the second message is in bnecp_watchdog_cb().
> 
> As I inspect the condition value "GIOCondition cond" in bnep_watchdog_cb(),
> there is only "G_IO_ERR", and the others bits are all clean. 
> And I try to analyze error packet, but I couldn't do that.
> 
> I don't know why this problem happens.
> 
> If you're already experienced this, it'll be very thankful to give me a
> piece of advice?
> 
> 
> And I would like to ask
>  "Does BlueZ support both PANU and NAP officially?"
> As I see on the BlueZ wiki, it supports only PANU.

Yes, PANU and NAP are working. So does GN.

Regards

Marcel



      reply	other threads:[~2009-02-26 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08 10:14 btusb compatibility issues Brian Rogers
2009-02-08 17:10 ` Marcel Holtmann
2009-02-09  0:43   ` Brian Rogers
2009-02-09 12:39     ` Marcel Holtmann
2009-02-23 13:21       ` Brian Rogers
2009-02-25 10:00         ` Marcel Holtmann
2009-02-26 13:09           ` Issues in PANU Chan-Yeol Park
2009-02-26 16:03             ` 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=1235664202.27004.18.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=chanyeol.park@samsung.com \
    --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