From: Mats Erik Andersson <mats.andersson64@comhem.se>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] dbus problem, Was: Only one pand-daemon?
Date: Wed, 04 Jul 2007 15:43:44 +0200 [thread overview]
Message-ID: <1183556624.4951.10.camel@localhost> (raw)
In-Reply-To: <1183513706.6351.47.camel@aeonflux.holtmann.net>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
Dear Marcel,
I did find one solution to this:
ons 2007-07-04 klockan 03:48 +0200 skrev Marcel Holtmann:
> Hi Mats,
>
> > > > I am facing the problem that I cannot start more than
> > > > one listening pand-daemon, in spite of using two usb-dongles.
> > > > beginning to think that it could be DBUS that haunts me, but I
> > > > have just begun studying the source code of pand to make sure.
> > >
> >
> > I need more than one Bluetooth radio, i.e. usb-dongle, each providing
> > a NAP service, since I am not content with only seven clients in one
> > piconet. Hence my belief was that I could simply start one pand-daemon
> > for each dongle and have my system up and running.
>
> by default pand listens on all attached dongles. So that should work out
> of the box.
>
I made an addition to the dbus-configuration in bluez-hcid.conf by
inserting paths for hci0 and hci1 for root and console like this:
<policy user="root">
<allow own="org.bluez"/>
<allow send_path="/org/bluez/hci0"/>
<allow send_path="/org/bluez/hci1"/>
</policy>
After that a single listening PAN daemon is receptive on both
usb-dongles. My full configuration is attached here. It was already
previously expanded, but it was the four lines with 'hci#' that brought
the magic. I myself and probably other bluez-users, would improve our
knowledge, could you be so kind as to commenting on what additions
that could/should be eliminated from my configuration file. Please!
Best regards, Mats E A
[-- Attachment #2: bluez-hcid.conf.dbus --]
[-- Type: text/plain, Size: 936 bytes --]
<busconfig>
<!-- ../system.conf have denied everything, so we just punch some holes -->
<policy user="root">
<allow own="org.bluez"/>
<allow send_path="/org/bluez/hci0"/>
<allow send_path="/org/bluez/hci1"/>
</policy>
<policy at_console="true">
<allow send_destination="org.bluez.Adapter"/>
<allow receive_sender="org.bluez.Adapter"/>
<allow send_path="/org/bluez/Adapter"/>
<allow send_path="/org/bluez/hci0"/>
<allow send_path="/org/bluez/hci1"/>
<allow send_destination="org.bluez.Manager"/>
<allow receive_sender="org.bluez.Manager"/>
<allow send_path="/org/bluez/Manager"/>
<allow send_destination="org.bluez.PasskeyAgent"/>
<allow receive_sender="org.bluez.PasskeyAgent"/>
<allow send_path="/org/bluez/PasskeyAgent"/>
<allow send_destination="org.bluez.Security"/>
<allow receive_sender="org.bluez.Security"/>
</policy>
</busconfig>
[-- Attachment #3: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-07-04 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 21:49 [Bluez-users] Only one pand-daemon? Mats Erik Andersson
2007-07-03 3:33 ` Marcel Holtmann
2007-07-03 11:39 ` Mats Erik Andersson
2007-07-04 1:48 ` Marcel Holtmann
2007-07-04 13:43 ` Mats Erik Andersson [this message]
2007-07-05 8:10 ` [Bluez-users] dbus problem, Was: " Marcel Holtmann
2007-07-06 9:53 ` [Bluez-users] dbus problem for pand service Mats Erik Andersson
2007-07-11 9:54 ` Marcel Holtmann
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=1183556624.4951.10.camel@localhost \
--to=mats.andersson64@comhem.se \
--cc=bluez-users@lists.sourceforge.net \
/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