From: Nicola Ranaldo <ranaldo@unina.it>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Bnep networking with dbus on 4.*
Date: Tue, 17 Feb 2009 18:59:17 +0100 [thread overview]
Message-ID: <200902171859.17876.ranaldo@unina.it> (raw)
In-Reply-To: <1233772264.12562.2.camel@californication>
On Wednesday 04 February 2009 19:31:04 Marcel Holtmann wrote:
[...]
> > Is it possible to establish bnep connection with dbus api 4.*?
> > I'm not able to find documentation on that.
>
> yes it is. See network-api.txt document from the bluez-4.x source.
>
Hi Marcel,
I was able to migrate my code to 4.*, test networking api and succesfull
establish a bnep connection, but I have a doubt:
When a remote device offers GN and/or NAP services an org.bluez.Network
interface is created on dbus, and this may establish both GN and NAP
connection.
The only one "Connected" property suggests me that the api is constructed as
it's not possibile to establish GN *and* PAN connection to the same remote
device at the same time.
Is this a bluetooth limitation? a bluez limitation? an api limitation or am I
missing somethingh?
Best Regards
Nicola
prev parent reply other threads:[~2009-02-17 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 15:03 Bnep networking with dbus on 4.* Nicola Ranaldo
2009-02-04 18:31 ` Marcel Holtmann
2009-02-17 17:59 ` Nicola Ranaldo [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=200902171859.17876.ranaldo@unina.it \
--to=ranaldo@unina.it \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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