From: Mats Erik Andersson <mats.andersson64@comhem.se>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] dbus problem for pand service
Date: Fri, 06 Jul 2007 11:53:30 +0200 [thread overview]
Message-ID: <1183715610.5288.22.camel@localhost> (raw)
In-Reply-To: <1183623040.6351.85.camel@aeonflux.holtmann.net>
Hi Marcel,
tor 2007-07-05 klockan 10:10 +0200 skrev Marcel Holtmann:
> Hi Mats,
> =
> > > 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:
> > =
> > After that a single listening PAN daemon is receptive on both
> > usb-dongles.
> that is non-sense. The pand is not interacting with D-Bus at all. Some
> other changes must have made this working for you.
a harsh word to call it 'non-sense' (zum st=FCtzig machen!). True, pand
does not by itself call upon dbus, but the servicing daemon hcid does
depend on dbus and all the more does passkey-agent for the
authentications of pin codes depend in dbus. The standard code
passkey-agent.c even contains
if (use_default) {
path =3D "/org/bluez";
method =3D "RegisterDefaultPasskeyAgent";
} else {
path =3D "/org/bluez/hci0";
method =3D "RegisterPasskeyAgent";
}
and the corresponding part for unregistering. It seems to me that =
thus it is absolutely essential to use 'passkey-agent -d OpenUp'
to activate more than one dongle, since individual agents always
tie themselfs to hci0. I do not understand all details yet, but the
above code snippet shows that I will develop my own tailored
passkey-agent for my own application. That is the natural state of
affairs in our trade. Right! One always learn most by the mistakes
and by scrutinizing our source code. =
Regards Mats E A
-------------------------------------------------------------------------
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/
_______________________________________________
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-06 9:53 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 ` [Bluez-users] dbus problem, Was: " Mats Erik Andersson
2007-07-05 8:10 ` Marcel Holtmann
2007-07-06 9:53 ` Mats Erik Andersson [this message]
2007-07-11 9:54 ` [Bluez-users] dbus problem for pand service 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=1183715610.5288.22.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