public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Pizzamiglio <pizzamiglio@cefriel.it>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Pairing problem
Date: Fri, 15 Jul 2005 15:32:14 +0200	[thread overview]
Message-ID: <42D7BADE.80706@cefriel.it> (raw)
In-Reply-To: <1121433701.29806.14.camel@viskulan.tigerhost.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thx for your answer. Now it works!
When I installed new version of Bluez, I lost hcid.conf.
Now I've some trouble on write and reading with the phone, but this is
not the right place to send my question.

Cheers,
Pizza


bc90021 wrote:
> Luca,
> 
> You may want to try setting the security to "auto" in
> the /etc/bluetooth/hcid.conf.  I had a similar problem, and forcing the
> machine to use the phone's pin solved my problem.
> 
> On Fri, 2005-07-15 at 13:02 +0200, Luca Pizzamiglio wrote:
> 
> Hi to hall.
> 
> I'm using a Slackware Linux box with Linux 2.6.12 and Bluez patch.
> I'm using the latest 2.18 Bluez libs and utils.
> I want to develop a hands-free phone profile with BlueZ stack.
> 
> I create a RFCOMM interface with the command
> 
> 
>>rfcomm bind 0 00:00:00:00:00:00 1
> 
> with the right baddr.
> After that, I try to send an AT command:
> 
> 
>>echo ATA > /dev/rfcomm0
> 
> Then, the phone claim a pin to establish a connection.
> My pin_helper application is:
> 
> #!/bin/bash
> echo "PIN:0000"
> 
> so, I enter a 0000 PIN, but the phone tell me the PIN is wrong.
> 
> Maybe I've a misconfigured pin-helper application?
> 
> Thx in advance!
> 
> 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
- -------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC17reAoUy56ORfbERApVuAJ40b0WbvcDTexvgQ4Q+T3zrRde0CgCfaXRK
ifrzRYOHzA3Fs638M5RrJzI=
=rkKa
-----END PGP SIGNATURE-----


-------------------------------------------------------
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

  reply	other threads:[~2005-07-15 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-15 11:02 [Bluez-users] Pairing problem Luca Pizzamiglio
2005-07-15 13:21 ` bc90021
2005-07-15 13:32   ` Luca Pizzamiglio [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-26  3:09 [Bluez-users] pairing problem radha krishna
2007-04-16 11:14 [Bluez-users] Pairing problem Sumeet VERMA
2007-04-16 13:44 ` Marcel Holtmann
2007-04-17  7:16   ` Sumeet VERMA
2007-04-18 23:43     ` Marcel Holtmann
2007-04-17 11:23 Sumeet VERMA

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=42D7BADE.80706@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