Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@intel.com>
To: "Zheng, Wu" <wu.zheng@intel.com>
Cc: "Von Dentz, Luiz" <luiz.von.dentz@intel.com>,
	"Xu, Martin" <martin.xu@intel.com>,
	"Wu, JiangboX" <jiangbox.wu@intel.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: Interface and the other properties is not provided when BT pan (NAP) is connected passively
Date: Tue, 1 Apr 2014 11:01:09 +0300	[thread overview]
Message-ID: <20140401080109.GA18614@t440s.lan> (raw)
In-Reply-To: <2CF57A644018A745B8FE029C7223E16E1185AD06@SHSMSX104.ccr.corp.intel.com>

Hi Zheng Wu,

On Tue, Apr 01, 2014, Zheng, Wu wrote:
> We find that "org.bluez.NetworkServer1" doesn't provide any properties.
> 
> Only "org.bluez.Network1" provides the related properties.
> 
> It means that BT PANU or BT NAP connects with the other BT pan devices actively.
> The related BT properties (such as interface) can be provided.

By "interface" I assume you mean "network interface"? (to avoid
confusion e.g. with "D-Bus interface").

> However, If BT NAP is connected passively, The related BT properties
> (such as interface) can't be provided.
> 
> In TIZEN scene, the related BT properties (such as interface) is
> required when BT NAP is connected passively.

To my understanding that shouldn't be needed. You provide a bridge name
when you call NetworkServer1.Register() and new connections are
automatically added to that bridge. What else do you need?

Johan

  reply	other threads:[~2014-04-01  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01  2:20 Interface and the other properties is not provided when BT pan (NAP) is connected passively Zheng, Wu
2014-04-01  8:01 ` Johan Hedberg [this message]
2014-04-01  8:37   ` Zheng, Wu

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=20140401080109.GA18614@t440s.lan \
    --to=johan.hedberg@intel.com \
    --cc=jiangbox.wu@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.von.dentz@intel.com \
    --cc=martin.xu@intel.com \
    --cc=wu.zheng@intel.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