linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: bluez and dbus
Date: Fri, 10 Feb 2006 01:59:40 +0100	[thread overview]
Message-ID: <1139533180.17280.38.camel@localhost> (raw)
In-Reply-To: <d8545cc00602091209qdbbbc14oee676e900fa75ece@mail.gmail.com>

Hi Doug,

> Installing dbus-0.35 worked as far as that problem goes. Now on to my
> other problem's. :)
> 
> $hidd --search
> Searching ...
>         Connecting to device 00:50:F2:E6:FF:46
> this is the microsoft keyboard.
> no pin required, just connected
> 
> #
> # HCI daemon configuration file.
> #
> 
> # 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/bluepin;
>         pin_helper /opt/kde/lib/kdebluetooth/kbluepin
> 	# D-Bus PIN helper
> 	#dbus_pin_helper;
> }
> 
> # Default settings for HCI devices
> device {
> 	# Local device name
> 	#   %d - device id
> 	#   %h - host name
> 	name "BlueZ (%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;
> 
> 	# 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;
> }
> 
> $hciconfig hci0 reset
> $hciconfig hci0 auth
> nothing changes, mic$ keyboard still work's.
> 
> why does it not ask me for a pin?

use "hcidump -X -V" to check what is going on.

> let me get this authentication stuff straight. With security
> user;:When a device first
> connect's it will need a pin to pair with my dongle correct? after it
> is paired can't
> something like "hciconfig hci0 putkey xx:xx:xx:xx:xx:xx" be done so it
> won't ask for a pin again?

This will store the link key on the chip. However you need a link key
first and in general you only wanna do this if your Bluetooth adapter is
built in.

> I have three bluetooth devices here, but let me get this all figured
> out before I move on from the
> keyboard problem's.
> 
> With the way everything is working right now, I can't reboot and
> regain the connection without "hidd --search"

You connect the keyboard only once. After that the keyboard will
reconnect to you. So you need to run "hidd --server".

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-02-10  0:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09 20:09 [Bluez-users] Re: bluez and dbus Doug Chalmers
2006-02-10  0:59 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-10  2:19 nix4me
2006-02-10  2:32 ` Marcel Holtmann
2006-02-10  6:31 nix4me
2006-02-10  7:12 ` Marcel Holtmann
2006-02-10 20:44 nix4me
2006-02-11  3:47 ` 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=1139533180.17280.38.camel@localhost \
    --to=marcel@holtmann.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).