From: Alec <bluez@cormack.org>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Bluez NAP refuses connection if PANU clent has deleted pairing.
Date: Mon, 19 Jun 2006 18:11:57 +0100 [thread overview]
Message-ID: <4496DADD.5050208@cormack.org> (raw)
Hi,
I am using openslug 2.7 linux on Linksys NSLU2 server to create a
Bluetooth NAP.
The packages are a bit out of date but they are the latest available for
the NSLU2.
bluez-utils-nodbus - 2.21-r0 -
kernel-module-bluetooth - 2.6.12.2-r17.4 -
libbluetooth1 - 2.21-r0 -
The NAP works perfectly allowing clients to connect, enter the PIN and
gain internet access via tle Bluez NAP. Once clients have paired once
they can re-connect without a PIN.
The problem I get is if a client deletes its pairing but the server
still has its pairing in /var/lib/bluetooth/{ADDR}/linkkeys. Under
these circumstances the client is refused access until I delete the
pairing on the server - at which point the client is prompted to re-pair
and everything then works fine again.
I assumed there was some combination of settings in hcid.conf that would
overcome this (pairing multi looked promising! but made no difference)
and I have tried every variation of settings I can think of.
Please can anyone help?
Thanks in advance
Alec
[hcid.conf]
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.4 2004/04/29 20:14:21 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; ## /etc/bluetooth/pin
#security user; ## calls helper application
# 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 /bin/bluepin;
pin_helper /etc/bluetooth/feed-pin.sh;
# D-Bus PIN helper
# dbus_pin_helper;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h";
# Local device class
class 0x820100;
# 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
auth enable;
encrypt enable;
}
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2006-06-19 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 17:11 Alec [this message]
2006-06-20 9:55 ` [Bluez-users] Bluez NAP refuses connection if PANU clent has deleted pairing Marcel Holtmann
[not found] ` <4497E167.3020205@cormack.org>
2006-06-20 13:56 ` Marcel Holtmann
2006-06-20 15:02 ` Alec
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=4496DADD.5050208@cormack.org \
--to=bluez@cormack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).