2004-02-25 00:54:18

by wim delvaux

[permalink] [raw]
Subject: [Bluez-users] link_key_request problems

HI all,

I am setting up a pan connection between my Ipaq/Linux and my Linux/2.6
server.

When I try to connect I see in the logfile that hcid tries to authenticate by
using a stored link key. This does not seem to work since the connection is
not established.

When I remove the link_key file and use the pin it works.

What might be the problem here ?

W



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users


2004-02-25 13:28:34

by Marcel Holtmann

[permalink] [raw]
Subject: Re: [Bluez-users] link_key_request problems

Hi Wim,

> > what are your hcid.conf settings? Set the pairing mode to "multi".
>
> Pairing is in both MULTI

then show us the binary hcidump of a connection. BTW using "auth enable"
is security mode 3.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

2004-02-25 02:51:06

by wim delvaux

[permalink] [raw]
Subject: Re: [Bluez-users] link_key_request problems

>
> what are your hcid.conf settings? Set the pairing mode to "multi".

Pairing is in both MULTI

HCID.conf of IPAQ

# 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 /bin/bluepin;
#dbus_pin_helper;
}device {
# Local device name
# %d - device id
# %h - host name
name "%h (%d)";

# Local device class
class 0x120112;

# 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 hold,sniff,park;

# Authentication and Encryption
auth enable;
#encrypt enable;
}

Hcid for the SERVER :

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

# 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 hold,sniff,park;

# Authentication and Encryption
auth enable;
# encrypt enable;
}




>
> Regards
>
> Marcel

2004-02-25 01:27:10

by Marcel Holtmann

[permalink] [raw]
Subject: Re: [Bluez-users] link_key_request problems

Hi Wim,

> I am setting up a pan connection between my Ipaq/Linux and my Linux/2.6
> server.
>
> When I try to connect I see in the logfile that hcid tries to authenticate by
> using a stored link key. This does not seem to work since the connection is
> not established.
>
> When I remove the link_key file and use the pin it works.
>
> What might be the problem here ?

what are your hcid.conf settings? Set the pairing mode to "multi".

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

2004-03-03 14:46:06

by Marcel Holtmann

[permalink] [raw]
Subject: Re: [Bluez-users] link_key_request problems

Hi Wim,

write a binary version do disk (with -w) and post it or use -x.

Regards

Marcel

> hcidump attached :
>
> > HCI Event: Connect Request(0x04) plen 10
> . . . . . . . . . .
> < HCI Command: Accept Connection Request(0x01|0x0009) plen 7
> . . . . . . .
> > HCI Event: Command Status(0x0f) plen 4
> . . . .
> > HCI Event: Link Key Request(0x17) plen 6
> . . . . . .
> < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22
> . . . . . . . B . . 3 . . . . i . c . .
> . b
> > HCI Event: Role Change(0x12) plen 8
> . . . . . . . .
> > HCI Event: Command Complete(0x0e) plen 10
> . . . . . . . . . .
> > HCI Event: Connect Complete(0x03) plen 11
> . ( . . . . . . . . .
>
> or RAW
>
> > 04 04 0A 96 85 0D C7 02 00 12 01 12 01
> < 01 09 04 07 96 85 0D C7 02 00 00
> > 04 0F 04 00 01 09 04
> > 04 17 06 96 85 0D C7 02 00
> < 01 0B 04 16 96 85 0D C7 02 00 F5 42 F5 95 33 1E 18 AF B9 69
> 87 63 F4 EA DA 62
> > 04 12 08 00 96 85 0D C7 02 00 00
> > 04 0E 0A 01 0B 04 00 96 85 0D C7 02 00
> > 04 03 0B 05 28 00 96 85 0D C7 02 00 01 00
>
> In the syslog I see ...
>
> Mar 3 15:09:05 localhost hcid[10515]: link_key_request
> (sba=00:60:57:02:71:A2, dba=00:02:C7:0D:85:96)
>
> On the Ipaq (3800) I see similar messages but the ascii content of the message
> is different
>
> Raw output there is ...
>
> HCIDump - HCI packet analyzer ver 1.5
> device: hci0 snap_len: 1028 filter: 0xffffffff
> > 04 12 08 00 A2 71 02 57 60 00 01
> > 04 17 06 A2 71 02 57 60 00
> < 01 0B 04 16 A2 71 02 57 60 00 16 66 2E EB B9 33 32 1B EE A8
> 15 F7 11 CA B1 CF
> > 04 0E 0A 01 0B 04 00 A2 71 02 57 60 00
> > 04 03 0B 05 28 00 A2 71 02 57 60 00 01 00
>
> The only solution is still to remove the link_key file




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

2004-03-03 14:16:12

by wim delvaux

[permalink] [raw]
Subject: Re: [Bluez-users] link_key_request problems

hcidump attached :

> HCI Event: Connect Request(0x04) plen 10
. . . . . . . . . .
< HCI Command: Accept Connection Request(0x01|0x0009) plen 7
. . . . . . .
> HCI Event: Command Status(0x0f) plen 4
. . . .
> HCI Event: Link Key Request(0x17) plen 6
. . . . . .
< HCI Command: Link Key Request Reply(0x01|0x000b) plen 22
. . . . . . . B . . 3 . . . . i . c . .
. b
> HCI Event: Role Change(0x12) plen 8
. . . . . . . .
> HCI Event: Command Complete(0x0e) plen 10
. . . . . . . . . .
> HCI Event: Connect Complete(0x03) plen 11
. ( . . . . . . . . .

or RAW

> 04 04 0A 96 85 0D C7 02 00 12 01 12 01
< 01 09 04 07 96 85 0D C7 02 00 00
> 04 0F 04 00 01 09 04
> 04 17 06 96 85 0D C7 02 00
< 01 0B 04 16 96 85 0D C7 02 00 F5 42 F5 95 33 1E 18 AF B9 69
87 63 F4 EA DA 62
> 04 12 08 00 96 85 0D C7 02 00 00
> 04 0E 0A 01 0B 04 00 96 85 0D C7 02 00
> 04 03 0B 05 28 00 96 85 0D C7 02 00 01 00

In the syslog I see ...

Mar 3 15:09:05 localhost hcid[10515]: link_key_request
(sba=00:60:57:02:71:A2, dba=00:02:C7:0D:85:96)

On the Ipaq (3800) I see similar messages but the ascii content of the message
is different

Raw output there is ...

HCIDump - HCI packet analyzer ver 1.5
device: hci0 snap_len: 1028 filter: 0xffffffff
> 04 12 08 00 A2 71 02 57 60 00 01
> 04 17 06 A2 71 02 57 60 00
< 01 0B 04 16 A2 71 02 57 60 00 16 66 2E EB B9 33 32 1B EE A8
15 F7 11 CA B1 CF
> 04 0E 0A 01 0B 04 00 A2 71 02 57 60 00
> 04 03 0B 05 28 00 A2 71 02 57 60 00 01 00

The only solution is still to remove the link_key file