From: Chris Searle <usenet@chrissearle.org>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: hcid config
Date: Fri, 23 Jul 2004 11:14:40 +0200 [thread overview]
Message-ID: <lgzn5rf5kv.fsf@montgomery.empolis.no> (raw)
In-Reply-To: 1090573758.4791.1.camel@pegasus
>>>>> "Marcel" == Marcel Holtmann <marcel@holtmann.org> writes:
Marcel> these devices are not brought up by hcid. Activate
Marcel> "autoinit" in hcid.conf and restart the hcid.
Not sure here - here's the hcid.conf file (as it is - the only change
I have made (ages back) is to pin_helper - this is redirected to a
script that returns a fixed PIN). autoinit appears to be set already.
#
# 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;
# 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 /etc/bluetooth/bluepin
# 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 0x100;
# 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;
#
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
#
#lp hold,sniff;
#
lp rswitch,hold,sniff,park;
# Authentication and Encryption
#auth enable;
#encrypt enable;
}
--
Chris Searle
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-07-23 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 7:01 [Bluez-users] hcid config Chris Searle
2004-07-23 8:41 ` Marcel Holtmann
2004-07-23 8:44 ` [Bluez-users] " Chris Searle
2004-07-23 8:51 ` Marcel Holtmann
2004-07-23 8:59 ` Chris Searle
2004-07-23 9:09 ` Marcel Holtmann
2004-07-23 9:14 ` Chris Searle [this message]
2004-07-25 11:47 ` Chris Searle
2004-07-25 12:23 ` 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=lgzn5rf5kv.fsf@montgomery.empolis.no \
--to=usenet@chrissearle.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