From: Luca Pizzamiglio <pizzamiglio@cefriel.it>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Permission problems, Bluetooth Headset
Date: Wed, 20 Jul 2005 16:07:56 +0200 [thread overview]
Message-ID: <42DE5ABC.8010802@cefriel.it> (raw)
In-Reply-To: <42DE3EAA.30705@toughguy.net>
Hi Ola,
Ola Benderius wrote:
> Hi,
> got a problem when trying to connect my Bluetooth headset (it's a
> Plantronics 2500) with Linux.
>
> I follow this guide and this is my hcid.conf:
>
> #
> # HCI daemon configuration file.
> #
> # $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $
> #
>
> # HCId options
> options {
> # Automatically initialize new devices
> autoinit yes;
>
> # Security Manager mode
> # none - Security manager disabled
> # auto - Use local PIN for incoming connections
> # user - Always ask user for a PIN
> #
> security auto;
>
> # Pairing mode
> # none - Pairing disabled
> # multi - Allow pairing with already paired devices
> # once - Pair once and deny successive attempts
> pairing multi;
>
> # PIN helper
> # pin_helper /usr/bin/bluepin;
> pin_helper /etc/bluetooth/pin-helper;
>
> # D-Bus PIN helper
> #dbus_pin_helper;
> }
>
> But the PIN is set to '0000' since that the PIN of the headset.
> (according to the manual)
>
> / echo "0000" > /etc/bluetooth/pin/
>
what's pin-helper?
It's your script?
If yes, it must echo "PIN:0000", not only "0000".
typically:
#!/bin/bash
echo "PIN:0000"
Cheers,
Pizza
-------------------------------------------
Luca Pizzamiglio
CEFRIEL - Embedded Systems Design Unit
Via Fucini, 2 - 20133 MILANO (ITALY)
Phone: +39 02 23954 343
e-mail: pizzamiglio@cefriel.it
ICQ: 5046978
-------------------------------------------
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-07-20 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 12:08 [Bluez-users] Permission problems, Bluetooth Headset Ola Benderius
2005-07-20 13:14 ` Bruno Abinader
2005-07-20 14:07 ` Luca Pizzamiglio [this message]
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=42DE5ABC.8010802@cefriel.it \
--to=pizzamiglio@cefriel.it \
--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