From: Rainer Dorsch <rdorsch@web.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] pand seem to ignore any pin configurations
Date: Sat, 7 May 2005 22:03:44 +0200 [thread overview]
Message-ID: <200505072203.45598.rdorsch@web.de> (raw)
Hello,
I have setup a PAN network with a NAP (bluez-utils 2.15/kernel 2.6.7) and a
PANU (bluez-utils/kernel-2.6.8). Each has an usb bt dongle and runs Debian
sarge. Surprisingly, they seem to ignore any pin configuration. If there is
good documentation on this somewhere, I would be happy with a pointer.
My assumption is that the PANU provides a PIN and NAP needs to confirm it.
My first problem is that I do not understand, where to provide a PIN on the
PANU.
NAP has this configuration:
silverboxy:~# cat /etc/bluetooth/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 user;
# 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/bluez-pin;
pin_helper /usr/local/bin/pin-helper;
# D-Bus PIN helper
#dbus_pin_helper;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";
# Local device class
class 0x3e0100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
# 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;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# Authentication and Encryption (Security Mode 3)
#auth enable;
#encrypt enable;
}
silverboxy:~#
and the pin is provided by
silverboxy:~# cat /usr/local/bin/pin-helper
#!/bin/sh
echo "PIN:1234"
silverboxy:~#
No mattter which pin is there the connection setup works.
What is strange here is that auth is commented out in hcid.conf. If I enable
that, I get
May 7 21:48:36 topsi pand[9586]: Failed to connect to the SDP server.
Function not implemented(38)
on the PANU side.
Any ideas are welcome.
Thanks,
Rainer
--
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-05-07 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 20:03 Rainer Dorsch [this message]
2005-05-07 20:35 ` [Bluez-users] pand seem to ignore any pin configurations Marcel Holtmann
2005-05-07 21:39 ` Rainer Dorsch
2005-05-07 22:02 ` Marcel Holtmann
2005-05-08 13:08 ` Rainer Dorsch
2005-05-08 13:36 ` Marcel Holtmann
2005-05-08 15:27 ` Rainer Dorsch
2005-05-08 15:46 ` Marcel Holtmann
2005-05-08 16:24 ` Rainer Dorsch
2005-05-08 16:31 ` 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=200505072203.45598.rdorsch@web.de \
--to=rdorsch@web.de \
--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