From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Piconet problems
Date: Thu, 13 Jan 2005 11:46:53 +0100 [thread overview]
Message-ID: <1105613213.7961.158.camel@pegasus> (raw)
In-Reply-To: <IA90PC$632BFAAAF7249FD9F21D4DC661567C69@libero.it>
Hi Jers,
> > > # Default link mode
> > > # none - no specific policy
> > > # accept - always accept incoming connections
> > > # master - become master on incoming connections,
> > > # deny role switch on outgoing connections
> > > #
> > > lm accept,master;
> > > #
> > > #lm accept;
> >
> > you changed this. Why? There can't be two device with a master role in
> > the same a piconet.
>
> I know that. Maybe I wasn't accurate in the description of my problem. I'm
> sorry...
> The above script is the hcid.conf file of the master. For slaves I have "lm
> accept".
this is not needed, because you use "pand --master ..." and this is
enought to force the role switch.
> I want to create a piconet with a single master and two slaves.
> In a previous corrispondance, you suggested me:
> - to upgrade my bluez packages. I did that.
> - to check the limitation for firmware pre HCI 16.4. I did that.
>
> - to check the link policy because the "hciconfig -a" command showed it no
> set for any device. This is my current problem.
>
> "hciconfig -a" still shows me that there is no link policy set for any
> device but, for all dongles, in the hcid.conf I have
Is hcid running?
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-13 10:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 9:22 [Bluez-users] Piconet problems jers
2005-01-13 10:46 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-18 18:27 Arlen Nascimento
2005-07-18 18:36 ` Marcel Holtmann
2005-01-24 11:14 jers
2005-01-24 12:25 ` Marcel Holtmann
2005-01-20 15:49 jers
2005-01-21 0:42 ` Marcel Holtmann
2005-01-20 11:33 jers
2005-01-20 12:52 ` Marcel Holtmann
2005-01-17 8:36 jers
2005-01-17 11:21 ` Marcel Holtmann
2005-01-14 10:21 jers
2005-01-14 21:18 ` Marcel Holtmann
2005-01-13 13:13 jers
2005-01-13 14:39 ` Marcel Holtmann
2005-01-11 11:19 jers
2005-01-11 10:40 jers
2005-01-11 10:52 ` Benoit Panizzon
2005-01-11 12:06 ` Marcel Holtmann
2004-12-21 13:28 jers
2004-12-21 13:56 ` Marcel Holtmann
2004-12-21 11:02 jers
2004-12-21 11:16 ` Marcel Holtmann
2004-12-21 20:21 ` blookk -
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=1105613213.7961.158.camel@pegasus \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.