From: Mats Erik Andersson <mats.andersson64@comhem.se>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Only one pand-daemon?
Date: Tue, 03 Jul 2007 13:39:23 +0200 [thread overview]
Message-ID: <1183462763.4335.17.camel@localhost> (raw)
In-Reply-To: <1183433596.6351.25.camel@aeonflux.holtmann.net>
Dear Marcel and all other fellows,
tis 2007-07-03 klockan 05:33 +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.
> > The second call with 'pand --listen -e bdaddr ...' immediately
> > ends with return value zero and no traces in any log file.
> > I am running Bluez-utils 3.7 on Debiif test "$PAND_ENABLED" != "0"; then
> an Etch. Slowly I am
> > 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 have no idea why you actually need two pand, but you can call pand
> with -i hciX to bind it to a specific adapter.
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.
To that end I made an alteration to /etc/init.d/bluetooth to
contain (within start_pand()) essentially
HCIDEVICES="0 1"
HCIBDADDR=(bdaddr0 bdaddr1) # in numerical values!
if test "$PAND_ENABLED" != "0"; then
for nr in $HCIDEVICES; do
start-stop-daemon --start --quiet --exec $PAND_DAEMON -- \
$PAND_OPTIONS --devup /etc/bluetooth/pan/dev-up \
--ethernet "bnep$nr%d" --device ${HCIBDADDR[$nr]} \
--pidfile /var/run/pand.${nr}.pid
/usr/local/sbin/passkey-agent Buhh ${HCIBDADDR[$nr]} &
done
log_progress_msg "pand"
fi
The outcome is that only hci0 is serviced by pand and that it
configures bnep00 at first call. There is no trace of a service
for hci1, neither in the process list, in syslog, nor does it
respond to "pand --connect bdadd1" from a remote machine.
Do you disagree to a need of servicing more than one piconet
from a single machine, or is this not even implemented in the
present day BlueZ-stack? Again, my server runs kernel 2.6.18
with Debian Etch and hence Bluez-utils 3.7. Have the later
issues of Bluez-utils diversified in the above respect?
Best 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-03 11:39 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 [this message]
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 ` [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=1183462763.4335.17.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