linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bluez-devel] Authentication failure
@ 2005-11-21  7:44 Pragya Gupta
  2005-11-22 11:07 ` Marcel Holtmann
  0 siblings, 1 reply; 2+ messages in thread
From: Pragya Gupta @ 2005-11-21  7:44 UTC (permalink / raw)
  To: bluez-devel

[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]


Hi,

I have enabled authentication on BlueZ and I try to issue connection 
from another bluetooth device. I am seeing random behaviour with 
respect to authentication. Sometimes the authentication procedure 
goes through and a file "link_key" is created in /etc/bluetooth/.

But most of the times, I see a link key request and no response from BlueZ.
I am attaching the hcid.conf being used by me and also some logs (see 
below) collected using hcidump.

Please help me to understand if I am doing something incorrect.

Thanks and Regards
Pragya

-------------------------------------------------
[root@localhost bluetooth]# hcidump -X
HCIDump - HCI packet analyzer ver 1.11
device: hci0 snap_len: 1028 filter: 0xffffffff

 > HCI Event: Connect Request (0x04) plen 10

   0000: 0e b3 5f 3e 04 00 1c 04 28 01                     .._>....(.
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
   0000: 0e b3 5f 3e 04 00 01                              .._>...

 > HCI Event: Command Status (0x0f) plen 4

   0000: 00 01 09 04                                       ....

 > HCI Event: Link Key Request (0x17) plen 6

   0000: 0e b3 5f 3e 04 00                                 .._>..

 > HCI Event: Connect Complete (0x03) plen 11

   0000: 10 2a 00 0e b3 5f 3e 04 00 01 00                  .*..._>....

 > HCI Event: Connect Request (0x04) plen 10

   0000: 0e b3 5f 3e 04 00 1c 04 28 01                     .._>....(.
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
   0000: 0e b3 5f 3e 04 00 01                              .._>...

 > HCI Event: Command Status (0x0f) plen 4

   0000: 00 01 09 04                                       ....

 > HCI Event: Link Key Request (0x17) plen 6

   0000: 0e b3 5f 3e 04 00
-------------------------------------------------


[root@localhost bluetooth]# hcidump -R
HCIDump - HCI packet analyzer ver 1.11
device: hci0 snap_len: 1028 filter: 0xffffffff

 > 04 04 0A 0E B3 5F 3E 04 00 1C 04 28 01

< 01 09 04 07 0E B3 5F 3E 04 00 01

 > 04 0F 04 00 01 09 04
 > 04 17 06 0E B3 5F 3E 04 00
-------------------------------------------------

[-- Attachment #2: hcid.conf --]
[-- Type: application/octet-stream, Size: 1484 bytes --]

#
# 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/bluepin;
	pin_helper /etc/bluetooth/givepin;

	# 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 0x120104;
	class 0x240400

	# 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;
}

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Bluez-devel] Authentication failure
  2005-11-21  7:44 [Bluez-devel] Authentication failure Pragya Gupta
@ 2005-11-22 11:07 ` Marcel Holtmann
  0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2005-11-22 11:07 UTC (permalink / raw)
  To: bluez-devel

Hi Pragya,

> I have enabled authentication on BlueZ and I try to issue connection 
> from another bluetooth device. I am seeing random behaviour with 
> respect to authentication. Sometimes the authentication procedure 
> goes through and a file "link_key" is created in /etc/bluetooth/.
> 
> But most of the times, I see a link key request and no response from BlueZ.
> I am attaching the hcid.conf being used by me and also some logs (see 
> below) collected using hcidump.

when using hcidump then use it with -X -V and as root. Nobody wants to
decode the HCI commands and events by themself.

If the link key requests are not answered, I suspect that hcid is not
running. If it runs make sure only one instance is running.

At some point we moved the link key storage to /var/lib/bluetooth and it
is also a text file now.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-11-22 11:07 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-21  7:44 [Bluez-devel] Authentication failure Pragya Gupta
2005-11-22 11:07 ` Marcel Holtmann

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