[Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Lutz Pressler]

Hello,

searching through the archives gave me no clue.

In contrast to Nokia 6310i, I'm not able to pair my Nokia 6230 (firmware
3.15) and bluez (two 2.4 systems tried, one beeing SuSE 9.0 with
kernel 2.5.21-251 and bluez-utils-2.3-57, bluez-libs-2.4-31).

After entering the correct pin (giving the wrong one yields other error)
in the phone's pairing dialogue, the 6230 only aborts with
"pairing and conn. rejected for security reasons".

hcid.conf is more or less default, works with 6310i and can be sent on
request.

Acer USB adapter (vend/prod 0xb7a/0x7d0).

Any idea? Thanks a lot,
  Lutz

-- 
  _              |  Lutz Pressler          |  Tel: ++49-551-3700002
 |_     |\ |     |  Service Network GmbH   |  FAX: ++49-551-3700009
 ._|ER  | \|ET   |  Bahnhofsallee 1b       |   mailto:lp@SerNet.DE
Service Network  |  D-37081 Goettingen     |  http://www.SerNet.DE/



-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Marcel Holtmann]

Hi Lutz,

> In contrast to Nokia 6310i, I'm not able to pair my Nokia 6230 (firmware
> 3.15) and bluez (two 2.4 systems tried, one beeing SuSE 9.0 with
> kernel 2.5.21-251 and bluez-utils-2.3-57, bluez-libs-2.4-31).

please run "hcitool info <bdaddr-6230>" for me, so I can put this phone
on my list.

> After entering the correct pin (giving the wrong one yields other error)
> in the phone's pairing dialogue, the 6230 only aborts with
> "pairing and conn. rejected for security reasons".

Run "hcidump -x" as root and show us the part of connection creation and
the request for the link key.

> hcid.conf is more or less default, works with 6310i and can be sent on
> request.

If it is not default then show it to us.

> Acer USB adapter (vend/prod 0xb7a/0x7d0).

What is the output of "hciconfig -a". What version of the Acer dongle is
this?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Lutz Pressler]

Hi Marcel and all,
On Tue, 18 May 2004, Marcel Holtmann wrote:
>
> > In contrast to Nokia 6310i, I'm not able to pair my Nokia 6230 (firmware
> > 3.15) and bluez (two 2.4 systems tried, one beeing SuSE 9.0 with
> > kernel 2.5.21-251 and bluez-utils-2.3-57, bluez-libs-2.4-31).
>
> please run "hcitool info <bdaddr-6230>" for me, so I can put this phone
> on my list.
>
Requesting information ...
        BD Address:  00:E0:03:39:C9:AB
        Device Name: Nokia 6230 LP
        LMP Version: 1.1 (0x1) LMP Subversion: 0x380
        Manufacturer: Cambridge Silicon Radio (10)
        Features: 0xbf 0xee 0x00 0x09
                <3-slot packets> <5-slot packets> <encryption> <slot offset>
                <timing accuracy> <role switch> <sniff mode> <RSSI>
                <channel quality> <SCO link> <HV3 packets> <u-law log>
                <A-law log>

> > After entering the correct pin (giving the wrong one yields other error)
> > in the phone's pairing dialogue, the 6230 only aborts with
> > "pairing and conn. rejected for security reasons".
>
> Run "hcidump -x" as root and show us the part of connection creation and
> the request for the link key.
HCIDump - HCI packet analyzer ver 1.8
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Connect Request(0x04) plen 10
  AB C9 39 03 E0 00 04 02 52 01
< HCI Command: Accept Connection Request(0x01|0x0009) plen 7
  AB C9 39 03 E0 00 01
> HCI Event: Command Status(0x0f) plen 4
  00 01 09 04
> HCI Event: PIN Code Request(0x16) plen 6
  AB C9 39 03 E0 00
< HCI Command: PIN Code Request Reply(0x01|0x000d) plen 23
  AB C9 39 03 E0 00 05 38 34 37 37 31 00 00 00 00 00 00 00 00
  00 00 00
> HCI Event: Command Complete(0x0e) plen 10
  01 0D 04 00 AB C9 39 03 E0 00
> HCI Event: Link Key Notification(0x18) plen 23
  AB C9 39 03 E0 00 0F B5 F9 09 4B CC 34 47 B7 91 18 71 5F 0B
  D8 A3 01
> HCI Event: Connect Complete(0x03) plen 11
  00 00 00 AB C9 39 03 E0 00 01 00
< HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
  00 00 0F 00
> HCI Event: Command Complete(0x0e) plen 6
  01 0D 08 00 00 00
< HCI Command: Change Connection Packet Type(0x01|0x000f) plen 4
  00 00 18 CC
> HCI Event: Command Status(0x0f) plen 4
  00 01 0F 04
> HCI Event: Connection Packet Type Changed(0x1d) plen 5
  00 00 00 18 CC
> HCI Event: Command Complete(0x0e) plen 3
  01 00 00
> HCI Event: Disconn Complete(0x05) plen 4
  00 00 00 29

>
> > hcid.conf is more or less default, works with 6310i and can be sent on
> > request.
>
> If it is not default then show it to us.
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
        # if you want a interactiv query of your pin use /bin/bluepin
        # /bin/bluepincat is using the pin in the /etc/bluetooth/pin file
        # pin_helper /bin/bluepin;
        pin_helper /bin/bluepincat;
}

# Default settings for HCI devices
device {
        # Local device name
        #   %d - device id
        #   %h - host name
        # name "BlueZ (%d)";
        name "tux";

        # 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,rswitch;

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


>
> > Acer USB adapter (vend/prod 0xb7a/0x7d0).
>
> What is the output of "hciconfig -a". What version of the Acer dongle is
> this?
hci0:   Type: USB
        BD Address: 00:04:3E:C0:6D:93 ACL MTU: 1356:5  SCO MTU: 48:1
        UP RUNNING PSCAN ISCAN
        RX bytes:7294 acl:0 sco:0 events:342 errors:0
        TX bytes:2754 acl:0 sco:0 commands:143 errors:0
        Features: 0xff 0x07 0x04 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'tux'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0x86 LMP Ver: 1.1 (0x1) LMP Subver: 0x86
        Manufacturer: Telencomm Inc. (18)


Acer "BT-510".


Thanks,
  Lutz


-- 
  _              |  Lutz Pressler          |  Tel: ++49-551-3700002
 |_     |\ |     |  Service Network GmbH   |  FAX: ++49-551-3700009
 ._|ER  | \|ET   |  Bahnhofsallee 1b       |   mailto:lp@SerNet.DE
Service Network  |  D-37081 Goettingen     |  http://www.SerNet.DE/



-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Marcel Holtmann]

Hi Lutz,

> Requesting information ...
>         BD Address:  00:E0:03:39:C9:AB
>         Device Name: Nokia 6230 LP
>         LMP Version: 1.1 (0x1) LMP Subversion: 0x380
>         Manufacturer: Cambridge Silicon Radio (10)
>         Features: 0xbf 0xee 0x00 0x09
>                 <3-slot packets> <5-slot packets> <encryption> <slot offset>
>                 <timing accuracy> <role switch> <sniff mode> <RSSI>
>                 <channel quality> <SCO link> <HV3 packets> <u-law log>
>                 <A-law log>

please install bluez-libs-2.7 and bluez-utils-2.7, because it looks like
that this phone already contains some Bluetooth 1.2 features and I need
to know the full 8 bytes of the remote features.

> HCIDump - HCI packet analyzer ver 1.8
> device: hci0 snap_len: 1028 filter: 0xffffffff
> > HCI Event: Connect Request(0x04) plen 10
>   AB C9 39 03 E0 00 04 02 52 01
> < HCI Command: Accept Connection Request(0x01|0x0009) plen 7
>   AB C9 39 03 E0 00 01
> > HCI Event: Command Status(0x0f) plen 4
>   00 01 09 04
> > HCI Event: PIN Code Request(0x16) plen 6
>   AB C9 39 03 E0 00
> < HCI Command: PIN Code Request Reply(0x01|0x000d) plen 23
>   AB C9 39 03 E0 00 05 38 34 37 37 31 00 00 00 00 00 00 00 00
>   00 00 00
> > HCI Event: Command Complete(0x0e) plen 10
>   01 0D 04 00 AB C9 39 03 E0 00
> > HCI Event: Link Key Notification(0x18) plen 23
>   AB C9 39 03 E0 00 0F B5 F9 09 4B CC 34 47 B7 91 18 71 5F 0B
>   D8 A3 01
> > HCI Event: Connect Complete(0x03) plen 11
>   00 00 00 AB C9 39 03 E0 00 01 00

You made a connection from the phone to your PC, right? And it looks
like that you are in security mode 3. From your hcid.conf I saw that you
haven't activated auth and encrypt so this is not you, but I can't think
of that your phone uses security mode 3. This is not normal.

> < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
>   00 00 0F 00
> > HCI Event: Command Complete(0x0e) plen 6
>   01 0D 08 00 00 00
> < HCI Command: Change Connection Packet Type(0x01|0x000f) plen 4
>   00 00 18 CC
> > HCI Event: Command Status(0x0f) plen 4
>   00 01 0F 04
> > HCI Event: Connection Packet Type Changed(0x1d) plen 5
>   00 00 00 18 CC
> > HCI Event: Command Complete(0x0e) plen 3
>   01 00 00
> > HCI Event: Disconn Complete(0x05) plen 4
>   00 00 00 29

It disconnects with "Pairing With Unit Key Not Supported" error (0x29)
and I haven't seen this error before. I am no link manager expert, but I
really think that one implementation is acting very bad here. And I
guess it is your Acer dongle with the Zeevo/Telencomm chip, because it
has caused troubles in the past. Do you own another dongle (preferable
CSR based) to check this?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Peter Stephenson]

Marcel Holtmann wrote:
> > Requesting information ...
> >         BD Address:  00:E0:03:39:C9:AB
> >         Device Name: Nokia 6230 LP
> >         LMP Version: 1.1 (0x1) LMP Subversion: 0x380
> >         Manufacturer: Cambridge Silicon Radio (10)
> >         Features: 0xbf 0xee 0x00 0x09
> >                 <3-slot packets> <5-slot packets> <encryption> <slot offset
> >
> >                 <timing accuracy> <role switch> <sniff mode> <RSSI>
> >                 <channel quality> <SCO link> <HV3 packets> <u-law log>
> >                 <A-law log>
>
> please install bluez-libs-2.7 and bluez-utils-2.7, because it looks like
> that this phone already contains some Bluetooth 1.2 features and I need
> to know the full 8 bytes of the remote features.

Below HCI, at least, it's 1.1 only.  I'm surprised you're not seeing
at least CVSD and almost certainly power control --- could the third and
fourth bytes be scrambled somehow?

pws


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************



-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Marcel Holtmann]

Hi Peter,

> > > Requesting information ...
> > >         BD Address:  00:E0:03:39:C9:AB
> > >         Device Name: Nokia 6230 LP
> > >         LMP Version: 1.1 (0x1) LMP Subversion: 0x380
> > >         Manufacturer: Cambridge Silicon Radio (10)
> > >         Features: 0xbf 0xee 0x00 0x09
> > >                 <3-slot packets> <5-slot packets> <encryption> <slot offset
> > >
> > >                 <timing accuracy> <role switch> <sniff mode> <RSSI>
> > >                 <channel quality> <SCO link> <HV3 packets> <u-law log>
> > >                 <A-law log>
> >
> > please install bluez-libs-2.7 and bluez-utils-2.7, because it looks like
> > that this phone already contains some Bluetooth 1.2 features and I need
> > to know the full 8 bytes of the remote features.
> 
> Below HCI, at least, it's 1.1 only.  I'm surprised you're not seeing
> at least CVSD and almost certainly power control --- could the third and
> fourth bytes be scrambled somehow?

please show us "hcidump -x" while requesting the remote information. We
can decode the information by hand and you don't have to install new
BlueZ packages.

Maybe a guy at Nokia set the PS key for the features wrong ;)

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Lutz Pressler]

> > > > Requesting information ...
> > > >         BD Address:  00:E0:03:39:C9:AB
> > > >         Device Name: Nokia 6230 LP
> > > >         LMP Version: 1.1 (0x1) LMP Subversion: 0x380
> > > >         Manufacturer: Cambridge Silicon Radio (10)
> > > >         Features: 0xbf 0xee 0x00 0x09
> > > >                 <3-slot packets> <5-slot packets> <encryption> <slot offset
> > > >
> > > >                 <timing accuracy> <role switch> <sniff mode> <RSSI>
> > > >                 <channel quality> <SCO link> <HV3 packets> <u-law log>
> > > >                 <A-law log>
> > >
> > > please install bluez-libs-2.7 and bluez-utils-2.7, because it looks like
> > > that this phone already contains some Bluetooth 1.2 features and I need
> > > to know the full 8 bytes of the remote features.
> >
> > Below HCI, at least, it's 1.1 only.  I'm surprised you're not seeing
> > at least CVSD and almost certainly power control --- could the third and
> > fourth bytes be scrambled somehow?
>
> please show us "hcidump -x" while requesting the remote information. We
> can decode the information by hand and you don't have to install new
> BlueZ packages.

HCIDump - HCI packet analyzer ver 1.8
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection(0x01|0x0005) plen 13
  AB C9 39 03 E0 00 18 00 00 00 00 00 00
> HCI Event: Command Status(0x0f) plen 4
  00 01 05 04
> HCI Event: Connect Complete(0x03) plen 11
  00 00 00 AB C9 39 03 E0 00 01 00
< HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
  00 00 0F 00
> HCI Event: Command Complete(0x0e) plen 3
  01 00 00
< HCI Command: Remote Name Request(0x01|0x0019) plen 10
  AB C9 39 03 E0 00 00 00 00 00
> HCI Event: Command Complete(0x0e) plen 6
  01 0D 08 00 00 00
> HCI Event: Command Status(0x0f) plen 4
  00 01 19 04
> HCI Event: Remote Name Req Complete(0x07) plen 255
  00 AB C9 39 03 E0 00 4E 6F 6B 69 61 20 36 32 33 30 20 4C 50
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
< HCI Command: Read Remote Version Information(0x01|0x001d) plen 2
  00 00
> HCI Event: Command Complete(0x0e) plen 3
  01 00 00
> HCI Event: Command Status(0x0f) plen 4
  00 01 1D 04
> HCI Event: Read Remote Ver Info Complete(0x0c) plen 8
  00 00 00 01 0A 00 80 03
> HCI Event: Command Complete(0x0e) plen 3
  01 00 00
< HCI Command: Read Remote Supported Features(0x01|0x001b) plen 2
  00 00
> HCI Event: Command Status(0x0f) plen 4
  00 01 1B 04
> HCI Event: Read Remote Supported Features(0x0b) plen 11
  00 00 00 BF EE 00 00 00 00 00 00
> HCI Event: Command Complete(0x0e) plen 3
  01 00 00
< HCI Command: Disconnect(0x01|0x0006) plen 3
  00 00 13
> HCI Event: Command Status(0x0f) plen 4
  00 01 06 04
> HCI Event: Disconn Complete(0x05) plen 4
  00 00 00 16
> HCI Event: Command Complete(0x0e) plen 3
  01 00 00


-- 
  _              |  Lutz Pressler          |  Tel: ++49-551-3700002
 |_     |\ |     |  Service Network GmbH   |  FAX: ++49-551-3700009
 ._|ER  | \|ET   |  Bahnhofsallee 1b       |   mailto:lp@SerNet.DE
Service Network  |  D-37081 Goettingen     |  http://www.SerNet.DE/

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Marcel Holtmann]

Hi Lutz,

> > please show us "hcidump -x" while requesting the remote information. We
> > can decode the information by hand and you don't have to install new
> > BlueZ packages.
> 
> > HCI Event: Read Remote Ver Info Complete(0x0c) plen 8
>   00 00 00 01 0A 00 80 03
> > HCI Event: Command Complete(0x0e) plen 3
>   01 00 00
> < HCI Command: Read Remote Supported Features(0x01|0x001b) plen 2
>   00 00
> > HCI Event: Command Status(0x0f) plen 4
>   00 01 1B 04
> > HCI Event: Read Remote Supported Features(0x0b) plen 11
>   00 00 00 BF EE 00 00 00 00 00 00

looks like something is really screwed up here. Please check this with
another USB dongle to make sure that your phone is not broken.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Lutz Pressler]

Hi,
On Tue, 18 May 2004, Marcel Holtmann wrote:
> looks like something is really screwed up here. Please check this with
> another USB dongle to make sure that your phone is not broken.
>
I borrowed a CSR based Allnet 1575.

hciconfig -a
hci0:   Type: USB
        BD Address: 00:0C:55:FF:DE:7F ACL MTU: 192:8  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:99 acl:0 sco:0 events:13 errors:0
        TX bytes:296 acl:0 sco:0 commands:12 errors:0
        Features: 0xff 0xff 0x0f 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'tux'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d
        Manufacturer: Cambridge Silicon Radio (10)

Pairing and RFCOM usage of the Nokia 6230 (PPP via GPRS) does work with
that one.

hcitool info 00:E0:03:39:C9:AB   now looks different:

Requesting information ...
        BD Address:  00:E0:03:39:C9:AB
        Device Name: Nokia 6230 LP
        LMP Version: 1.1 (0x1) LMP Subversion: 0x380
        Manufacturer: Cambridge Silicon Radio (10)
        Features: 0xbf 0xee 0x0f 0x00
                <3-slot packets> <5-slot packets> <encryption> <slot offset>
                <timing accuracy> <role switch> <sniff mode> <RSSI>
                <channel quality> <SCO link> <HV3 packets> <u-law log>
                <A-law log> <CVSD> <paging scheme> <power control>
                <transparent SCO>

Any further tests/dums to (re)do with that phone?

Thanks!
  Lutz

-- 
  _              |  Lutz Pressler          |  Tel: ++49-551-3700002
 |_     |\ |     |  Service Network GmbH   |  FAX: ++49-551-3700009
 ._|ER  | \|ET   |  Bahnhofsallee 1b       |   mailto:lp@SerNet.DE
Service Network  |  D-37081 Goettingen     |  http://www.SerNet.DE/

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Marcel Holtmann]

Hi Lutz,

> I borrowed a CSR based Allnet 1575.
> 
> hciconfig -a
> hci0:   Type: USB
>         BD Address: 00:0C:55:FF:DE:7F ACL MTU: 192:8  SCO MTU: 64:8
>         UP RUNNING PSCAN ISCAN
>         RX bytes:99 acl:0 sco:0 events:13 errors:0
>         TX bytes:296 acl:0 sco:0 commands:12 errors:0
>         Features: 0xff 0xff 0x0f 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: RSWITCH HOLD SNIFF PARK
>         Link mode: SLAVE ACCEPT
>         Name: 'tux'
>         Class: 0x000100
>         Service Classes: Unspecified
>         Device Class: Computer, Uncategorized
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d
>         Manufacturer: Cambridge Silicon Radio (10)
> 
> Pairing and RFCOM usage of the Nokia 6230 (PPP via GPRS) does work with
> that one.
> 
> hcitool info 00:E0:03:39:C9:AB   now looks different:
> 
> Requesting information ...
>         BD Address:  00:E0:03:39:C9:AB
>         Device Name: Nokia 6230 LP
>         LMP Version: 1.1 (0x1) LMP Subversion: 0x380
>         Manufacturer: Cambridge Silicon Radio (10)
>         Features: 0xbf 0xee 0x0f 0x00
>                 <3-slot packets> <5-slot packets> <encryption> <slot offset>
>                 <timing accuracy> <role switch> <sniff mode> <RSSI>
>                 <channel quality> <SCO link> <HV3 packets> <u-law log>
>                 <A-law log> <CVSD> <paging scheme> <power control>
>                 <transparent SCO>
> 
> Any further tests/dums to (re)do with that phone?

this all looks correct and so its again the dongle with the stupid Zeevo
TC2001 Bluetooth chip. This is one of the chips that should never made
it into any end user product. But some chip manufacturers don't care and
this makes Bluetooth looking bad :(

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Lutz Pressler]

On Tue, 18 May 2004, Marcel Holtmann wrote:

> please install bluez-libs-2.7 and bluez-utils-2.7, because it looks like
> that this phone already contains some Bluetooth 1.2 features and I need
> to know the full 8 bytes of the remote features.
later (work to do here :)) - probably not today.
>
>
> You made a connection from the phone to your PC, right? And it looks
Yes, but I tested both (at least I think so).
> like that you are in security mode 3. From your hcid.conf I saw that you
> haven't activated auth and encrypt so this is not you, but I can't think
tried with and without "auth enable; encrypt enable;" and with
"lm accept;" and "lm accept,master;". No difference.
> of that your phone uses security mode 3. This is not normal.
>
[...]
>
> It disconnects with "Pairing With Unit Key Not Supported" error (0x29)
> and I haven't seen this error before. I am no link manager expert, but I
> really think that one implementation is acting very bad here. And I
> guess it is your Acer dongle with the Zeevo/Telencomm chip, because it
> has caused troubles in the past. Do you own another dongle (preferable
> CSR based) to check this?
At the moment I don't think so. We also have a physically bigger Acer
dongle (that may be "100m" variant?), but that's on the road at the
moment. Should I order some specific model?

Lutz

-- 
  _              |  Lutz Pressler          |  Tel: ++49-551-3700002
 |_     |\ |     |  Service Network GmbH   |  FAX: ++49-551-3700009
 ._|ER  | \|ET   |  Bahnhofsallee 1b       |   mailto:lp@SerNet.DE
Service Network  |  D-37081 Goettingen     |  http://www.SerNet.DE/

Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"

[Marcel Holtmann]

Hi Lutz,

> > please install bluez-libs-2.7 and bluez-utils-2.7, because it looks like
> > that this phone already contains some Bluetooth 1.2 features and I need
> > to know the full 8 bytes of the remote features.
> later (work to do here :)) - probably not today.

not really needed anymore, because it looks like a bug in one of the
link managers or maybe the hardware itself.

> > like that you are in security mode 3. From your hcid.conf I saw that you
> > haven't activated auth and encrypt so this is not you, but I can't think
> tried with and without "auth enable; encrypt enable;" and with
> "lm accept;" and "lm accept,master;". No difference.

Keep auth and encrypt always off unless you really wanna activate
security mode 3.

> > It disconnects with "Pairing With Unit Key Not Supported" error (0x29)
> > and I haven't seen this error before. I am no link manager expert, but I
> > really think that one implementation is acting very bad here. And I
> > guess it is your Acer dongle with the Zeevo/Telencomm chip, because it
> > has caused troubles in the past. Do you own another dongle (preferable
> > CSR based) to check this?
> At the moment I don't think so. We also have a physically bigger Acer
> dongle (that may be "100m" variant?), but that's on the road at the
> moment. Should I order some specific model?

The best is you buy yourself a CSR based dongle with a least HCI 16.4
firmware. If you still get problems with a CSR based dongle you have to
return your phone. For specific dongle information check our hardware
lists at http://www.bluez.org/hardware.html

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

[Bluez-devel] Nokia 6230 info

[Andreas Gaufer]

On Tue, 18 May 2004 10:51:37 +0200 (CEST)
Lutz Pressler <Lutz.Pressler@SerNet.DE> wrote (on BlueZ-Users):
> > please run "hcitool info <bdaddr-6230>" for me, so I can put this phone
> > on my list.
> >
> Requesting information ...
>         BD Address:  00:E0:03:39:C9:AB
>         Device Name: Nokia 6230 LP
>         LMP Version: 1.1 (0x1) LMP Subversion: 0x380
>         Manufacturer: Cambridge Silicon Radio (10)
>         Features: 0xbf 0xee 0x00 0x09
>                 <3-slot packets> <5-slot packets> <encryption> <slot offset>
>                 <timing accuracy> <role switch> <sniff mode> <RSSI>
>                 <channel quality> <SCO link> <HV3 packets> <u-law log>
>                 <A-law log>
> 

Hi Marcel,

just looked into the data from our field tests. We saw something that had the 
Device Name "Nokia 6230 Ir" and it had a diffrent feature list. Just thought 
this might be intresting for you :

1080041406|dn|Nokia 6230 iR
1080041406|fea|0xbf 0xee 0x0f 0x00
1080041406|lmpsv|0x380
1080041406|lmpv|1.1 (0x1)
1080041406|mf|NokiaDanmarkAS

Since the Mac-Adress was 00:02:EE:x:x:x this was maby a prototype of that 
phone. We spotted it in March in Hannover ;)

Greetings

Andy


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Nokia 6230 info

[Marcel Holtmann]

Hi Andreas,

> just looked into the data from our field tests. We saw something that had the 
> Device Name "Nokia 6230 Ir" and it had a diffrent feature list. Just thought 
> this might be intresting for you :
> 
> 1080041406|dn|Nokia 6230 iR
> 1080041406|fea|0xbf 0xee 0x0f 0x00
> 1080041406|lmpsv|0x380
> 1080041406|lmpv|1.1 (0x1)
> 1080041406|mf|NokiaDanmarkAS
> 
> Since the Mac-Adress was 00:02:EE:x:x:x this was maby a prototype of that 
> phone. We spotted it in March in Hannover ;)

this feature list looks more correct to me.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel