* one question on BLE device authentication error
@ 2013-03-08 7:54 Huang, Christina
2013-03-08 13:59 ` Anderson Lizardo
0 siblings, 1 reply; 6+ messages in thread
From: Huang, Christina @ 2013-03-08 7:54 UTC (permalink / raw)
To: linux-bluetooth
Hi,
I'm trying to use bluez 5.2 release to connect with my LE device, which is one proximity alert device. It always reports "PIN or Key Missing" and then disconnect immediately.
Btmon logs and function calls is shown below:
Bluetooth monitor ver 5.3
= New Index: 00:1A:7D:DA:71:05 (BR/EDR,USB,hci0) [hci0] 0.777425
> HCI Event: LE Meta Event (0x3e) plen 26 [hci0] 1.866952
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Public (0x00)
Address: 80:CF:41:6D:0A:66 (OUI 80-CF-41)
Data length: 14
Name (complete): Lenovo S880i
RSSI: -75 dBm
@ Device Found: 80:CF:41:6D:0A:66 (1) rssi -75 flags 0x0000
0d 09 4c 65 6e 6f 76 6f 20 53 38 38 30 69 ..Lenovo S880i
> HCI Event: LE Meta Event (0x3e) plen 19 [hci0] 2.454951
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Public (0x00)
Address: 00:17:EA:91:8C:78 (OUI 00-17-EA)
Data length: 7
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
16-bit Service UUIDs (complete): 1 entry
Link Loss (0x1803)
RSSI: -69 dBm
@ Device Found: 00:17:EA:91:8C:78 (1) rssi -69 flags 0x0000
02 01 06 03 03 03 18 .......
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2 [hci0] 2.455206
Scanning: Disabled (0x00)
Filter duplicates: Disabled (0x00)
> HCI Event: LE Meta Event (0x3e) plen 30 [hci0] 2.456922
LE Advertising Report (0x02)
Num reports: 1
Event type: Scan response - SCAN_RSP (0x04)
Address type: Public (0x00)
Address: 00:17:EA:91:8C:78 (OUI 00-17-EA)
Data length: 18
Name (complete): UJuicer Alert
TX power: -6 dBm
RSSI: -69 dBm
@ Device Found: 00:17:EA:91:8C:78 (1) rssi -69 flags 0x0000
0e 09 55 4a 75 69 63 65 72 20 41 6c 65 72 74 02 ..UJuicer Alert.
0a fa ..
> HCI Event: Command Complete (0x0e) plen 4 [hci0] 2.461946
LE Set Scan Enable (0x08|0x000c) ncmd 1
Status: Success (0x00)
@ Discovering: 0x00 (6)
< HCI Command: LE Create Connection (0x08|0x000d) plen 25 [hci0] 2.499924
Scan interval: 60.000 msec (0x0060)
Scan window: 30.000 msec (0x0030)
Filter policy: White list is not used (0x00)
Peer address type: Public (0x00)
Address: 00:17:EA:91:8C:78 (OUI 00-17-EA)
Own address type: Public (0x00)
Min connection interval: 50.00 msec (0x0028)
Max connection interval: 70.00 msec (0x0038)
Connection latency: 0x0000
Supervision timeout: 420 msec (0x002a)
Min connection length: 0.000 msec (0x0000)
Max connection length: 0.000 msec (0x0000)
> HCI Event: Command Status (0x0f) plen 4 [hci0] 2.503950
LE Create Connection (0x08|0x000d) ncmd 1
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 19 [hci0] 5.723917
LE Connection Complete (0x01)
Status: Success (0x00)
Handle: 71
Role: Master (0x00)
Peer address type: Public (0x00)
Address: 00:17:EA:91:8C:78 (OUI 00-17-EA)
Connection interval: 70.00 msec (0x0038)
Connection latency: 0.00 msec (0x0000)
Supervision timeout: 420 msec (0x002a)
Master clock accuracy: 0x00
< HCI Command: LE Start Encryption (0x08|0x0019) plen 28 [hci0] 5.724000
Handle: 71
Random number: 8c126b665d2de279
Encryption diversifier: 0x3f55
Long term key: dcd74a1a07f653c0e27f65888debcbe5
@ Device Connected: 00:17:EA:91:8C:78 (1) flags 0x0000
> HCI Event: Command Status (0x0f) plen 4 [hci0] 5.733922
LE Start Encryption (0x08|0x0019) ncmd 1
Status: Success (0x00)
> ACL Data RX: Handle 71 flags 0x02 dlen 6 [hci0] 5.835521
SMP: Security Request (0x0b) len 1
Authentication requirement: Bonding - MITM (0x05)
> HCI Event: Encryption Change (0x08) plen 4 [hci0] 6.115911
Status: PIN or Key Missing (0x06)
Handle: 71
Encryption: Disabled (0x00)
< HCI Command: Disconnect (0x01|0x0006) plen 3 [hci0] 6.115942
Handle: 71
Reason: Authentication Failure (0x05)
> HCI Event: Command Status (0x0f) plen 4 [hci0] 6.117913
Disconnect (0x01|0x0006) ncmd 1
Status: Success (0x00)
> HCI Event: Disconnect Complete (0x05) plen 4 [hci0] 6.186914
Status: Success (0x00)
Handle: 71
Reason: Connection Terminated By Local Host (0x16)
@ Device Disconnected: 00:17:EA:91:8C:78 (1) reason 2
Some called function log:
received_data
event = 0x1, index = 0x0, length = 0x4
stop_passive_scanning_complete
device_connect_le
after bt_io_connect
received_data
event = 0x13, index = 0x0, length = 0x2
discovering_callback
received_data
event = 0xb, index = 0x0, length = 0xd
connected_callback
adapter_get_device
adapter_find_device
adapter_add_connection
device_add_connection
device_set_temporary
after adapter_add_connection
received_data
event = 0xc, index = 0x0, length = 0x8
dev_disconnected
adapter_find_device
bonding_complete
adapter_find_device
device_bonding_complete
att_connect_cb
att_error_cb
Thanks.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: one question on BLE device authentication error
2013-03-08 7:54 one question on BLE device authentication error Huang, Christina
@ 2013-03-08 13:59 ` Anderson Lizardo
2013-03-11 1:33 ` Huang, Christina
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Anderson Lizardo @ 2013-03-08 13:59 UTC (permalink / raw)
To: Huang, Christina; +Cc: linux-bluetooth
Hi Christina,
On Fri, Mar 8, 2013 at 3:54 AM, Huang, Christina
<christina.huang@intel.com> wrote:
> < HCI Command: LE Start Encryption (0x08|0x0019) plen 28 [hci0] 5.724000
> Handle: 71
> Random number: 8c126b665d2de279
> Encryption diversifier: 0x3f55
> Long term key: dcd74a1a07f653c0e27f65888debcbe5
> @ Device Connected: 00:17:EA:91:8C:78 (1) flags 0x0000
>> HCI Event: Command Status (0x0f) plen 4 [hci0] 5.733922
> LE Start Encryption (0x08|0x0019) ncmd 1
> Status: Success (0x00)
>> ACL Data RX: Handle 71 flags 0x02 dlen 6 [hci0] 5.835521
> SMP: Security Request (0x0b) len 1
> Authentication requirement: Bonding - MITM (0x05)
>> HCI Event: Encryption Change (0x08) plen 4 [hci0] 6.115911
> Status: PIN or Key Missing (0x06)
> Handle: 71
> Encryption: Disabled (0x00)
It looks like your LE device lost the bonding information (e.g. LTK)
and thus is not able to just encrypt the connection with the LTK BlueZ
is trying to use. You can try removing the bonding on BlueZ side (e.g.
"test-device remove <bdaddr>" or "remove <bdaddr>" on bluetoothctl)
and try again a complete pairing.
Best regards,
--
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: one question on BLE device authentication error
2013-03-08 13:59 ` Anderson Lizardo
@ 2013-03-11 1:33 ` Huang, Christina
2013-03-11 4:17 ` Huang, Christina
2013-04-07 6:23 ` Huang, Christina
2 siblings, 0 replies; 6+ messages in thread
From: Huang, Christina @ 2013-03-11 1:33 UTC (permalink / raw)
To: Anderson Lizardo; +Cc: linux-bluetooth
Hi, Anderson
Thanks for your quick reply, but it looks all same after I did "bluetoothctl remove", please see below log, I'm not sure if I did correct or not.
It's so strange that this LE device works well with my iphone4S, it connects well, and alert when the device is far away from my iphone.
~/bluez/client$ sudo ./bluetoothctl remove 00:17:EA:91:8C:78
[NEW] Controller 00:1A:7D:DA:71:05 christina-HP-Compaq-8200-Elite-SFF-PC-0 [default]
[NEW] Device 00:17:EA:91:8C:78 UJuicer Alert
[DEL] Device 00:17:EA:91:8C:78 UJuicer Alert
[CHG] Controller 00:1A:7D:DA:71:05 Powered: no
[CHG] Controller 00:1A:7D:DA:71:05 Discovering: no
[CHG] Controller 00:1A:7D:DA:71:05 Class: 0x000000
[DEL] Controller 00:1A:7D:DA:71:05 christina-HP-Compaq-8200-Elite-SFF-PC-0 [default]
[NEW] Controller 00:1A:7D:DA:71:05 christina-HP-Compaq-8200-Elite-SFF-PC-0 [default]
[NEW] Device 00:17:EA:91:8C:78 UJuicer Alert
[DEL] Device 00:17:EA:91:8C:78 UJuicer Alert
[DEL] Controller 00:1A:7D:DA:71:05 christina-HP-Compaq-8200-Elite-SFF-PC-0 [default]
[bluetooth]# remove 00:17:EA:91:8C:78
No default controller available
[bluetooth]# exit
~/bluez$ sudo bluetoothd
@ Device Connected: 00:17:EA:91:8C:78 (1) flags 0x0000
> HCI Event: Command Status (0x0f) plen 4 [hci0] 208.799845
LE Start Encryption (0x08|0x0019) ncmd 1
Status: Success (0x00)
> ACL Data RX: Handle 70 flags 0x02 dlen 6 [hci0] 208.801325
SMP: Security Request (0x0b) len 1
Authentication requirement: Bonding - MITM (0x05)
> HCI Event: Encryption Change (0x08) plen 4 [hci0] 209.081845
Status: PIN or Key Missing (0x06)
Handle: 70
Encryption: Disabled (0x00)
< HCI Command: Disconnect (0x01|0x0006) plen 3 [hci0] 209.081876
Handle: 70
Reason: Authentication Failure (0x05)
-----Original Message-----
From: Anderson Lizardo [mailto:anderson.lizardo@openbossa.org]
Sent: Friday, March 08, 2013 10:00 PM
To: Huang, Christina
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: one question on BLE device authentication error
Hi Christina,
On Fri, Mar 8, 2013 at 3:54 AM, Huang, Christina <christina.huang@intel.com> wrote:
> < HCI Command: LE Start Encryption (0x08|0x0019) plen 28 [hci0] 5.724000
> Handle: 71
> Random number: 8c126b665d2de279
> Encryption diversifier: 0x3f55
> Long term key: dcd74a1a07f653c0e27f65888debcbe5 @ Device
> Connected: 00:17:EA:91:8C:78 (1) flags 0x0000
>> HCI Event: Command Status (0x0f) plen 4 [hci0] 5.733922
> LE Start Encryption (0x08|0x0019) ncmd 1
> Status: Success (0x00)
>> ACL Data RX: Handle 71 flags 0x02 dlen 6 [hci0] 5.835521
> SMP: Security Request (0x0b) len 1
> Authentication requirement: Bonding - MITM (0x05)
>> HCI Event: Encryption Change (0x08) plen 4 [hci0] 6.115911
> Status: PIN or Key Missing (0x06)
> Handle: 71
> Encryption: Disabled (0x00)
It looks like your LE device lost the bonding information (e.g. LTK) and thus is not able to just encrypt the connection with the LTK BlueZ is trying to use. You can try removing the bonding on BlueZ side (e.g.
"test-device remove <bdaddr>" or "remove <bdaddr>" on bluetoothctl) and try again a complete pairing.
Best regards,
--
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: one question on BLE device authentication error
2013-03-08 13:59 ` Anderson Lizardo
2013-03-11 1:33 ` Huang, Christina
@ 2013-03-11 4:17 ` Huang, Christina
2013-04-07 6:23 ` Huang, Christina
2 siblings, 0 replies; 6+ messages in thread
From: Huang, Christina @ 2013-03-11 4:17 UTC (permalink / raw)
To: Anderson Lizardo; +Cc: linux-bluetooth
Hi, Anderson
Sorry to give wrong information, I tried several times with several commands with bluetoothctl and at last the connection succeeds after remove operation.
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1A:7D:DA:71:05 Discovering: yes
[NEW] Device 00:17:EA:91:8C:78 UJuicer Alert
[CHG] Device 00:17:EA:91:8C:78 RSSI: -42
[CHG] Device 00:17:EA:91:8C:78 RSSI: -52
[bluetooth]# scan off
Discovery stopped
[CHG] Device 00:17:EA:91:8C:78 RSSI is nil
[CHG] Controller 00:1A:7D:DA:71:05 Discovering: no
[bluetooth]# devices
Device 00:17:EA:91:8C:78 UJuicer Alert
[bluetooth]# connect 00:17:EA:91:8C:78
Attempting to connect to 00:17:EA:91:8C:78
Connection successful
[CHG] Device 00:17:EA:91:8C:78 Connected: yes
[CHG] Device 00:17:EA:91:8C:78 Paired: yes
[CHG] Device 00:17:EA:91:8C:78 UUIDs has unsupported type
[CHG] Device 00:17:EA:91:8C:78 Icon is nil
[CHG] Device 00:17:EA:91:8C:78 Appearance is nil
Thank you very much for the helpful reply.
Christina
-----Original Message-----
From: Huang, Christina
Sent: Monday, March 11, 2013 9:33 AM
To: 'Anderson Lizardo'
Cc: linux-bluetooth@vger.kernel.org
Subject: RE: one question on BLE device authentication error
Hi, Anderson
Thanks for your quick reply, but it looks all same after I did "bluetoothctl remove", please see below log, I'm not sure if I did correct or not.
It's so strange that this LE device works well with my iphone4S, it connects well, and alert when the device is far away from my iphone.
~/bluez/client$ sudo ./bluetoothctl remove 00:17:EA:91:8C:78 [NEW] Controller 00:1A:7D:DA:71:05 christina-HP-Compaq-8200-Elite-SFF-PC-0 [default] [NEW] Device 00:17:EA:91:8C:78 UJuicer Alert [DEL] Device 00:17:EA:91:8C:78 UJuicer Alert [CHG] Controller 00:1A:7D:DA:71:05 Powered: no [CHG] Controller 00:1A:7D:DA:71:05 Discovering: no [CHG] Controller 00:1A:7D:DA:71:05 Class: 0x000000 [DEL] Controller 00:1A:7D:DA:71:05 christina-HP-Compaq-8200-Elite-SFF-PC-0 [default] [NEW] Controller 00:1A:7D:DA:71:05 christina-HP-Compaq-8200-Elite-SFF-PC-0 [default] [NEW] Device 00:17:EA:91:8C:78 UJuicer Alert [DEL] Device 00:17:EA:91:8C:78 UJuicer Alert [DEL] Controller 00:1A:7D:DA:71:05 christina-HP-Compaq-8200-Elite-SFF-PC-0 [default] [bluetooth]# remove 00:17:EA:91:8C:78 No default controller available [bluetooth]# exit
~/bluez$ sudo bluetoothd
@ Device Connected: 00:17:EA:91:8C:78 (1) flags 0x0000
> HCI Event: Command Status (0x0f) plen 4 [hci0] 208.799845
LE Start Encryption (0x08|0x0019) ncmd 1
Status: Success (0x00)
> ACL Data RX: Handle 70 flags 0x02 dlen 6 [hci0] 208.801325
SMP: Security Request (0x0b) len 1
Authentication requirement: Bonding - MITM (0x05)
> HCI Event: Encryption Change (0x08) plen 4 [hci0] 209.081845
Status: PIN or Key Missing (0x06)
Handle: 70
Encryption: Disabled (0x00)
< HCI Command: Disconnect (0x01|0x0006) plen 3 [hci0] 209.081876
Handle: 70
Reason: Authentication Failure (0x05)
-----Original Message-----
From: Anderson Lizardo [mailto:anderson.lizardo@openbossa.org]
Sent: Friday, March 08, 2013 10:00 PM
To: Huang, Christina
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: one question on BLE device authentication error
Hi Christina,
On Fri, Mar 8, 2013 at 3:54 AM, Huang, Christina <christina.huang@intel.com> wrote:
> < HCI Command: LE Start Encryption (0x08|0x0019) plen 28 [hci0] 5.724000
> Handle: 71
> Random number: 8c126b665d2de279
> Encryption diversifier: 0x3f55
> Long term key: dcd74a1a07f653c0e27f65888debcbe5 @ Device
> Connected: 00:17:EA:91:8C:78 (1) flags 0x0000
>> HCI Event: Command Status (0x0f) plen 4 [hci0] 5.733922
> LE Start Encryption (0x08|0x0019) ncmd 1
> Status: Success (0x00)
>> ACL Data RX: Handle 71 flags 0x02 dlen 6 [hci0] 5.835521
> SMP: Security Request (0x0b) len 1
> Authentication requirement: Bonding - MITM (0x05)
>> HCI Event: Encryption Change (0x08) plen 4 [hci0] 6.115911
> Status: PIN or Key Missing (0x06)
> Handle: 71
> Encryption: Disabled (0x00)
It looks like your LE device lost the bonding information (e.g. LTK) and thus is not able to just encrypt the connection with the LTK BlueZ is trying to use. You can try removing the bonding on BlueZ side (e.g.
"test-device remove <bdaddr>" or "remove <bdaddr>" on bluetoothctl) and try again a complete pairing.
Best regards,
--
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: one question on BLE device authentication error
2013-03-08 13:59 ` Anderson Lizardo
2013-03-11 1:33 ` Huang, Christina
2013-03-11 4:17 ` Huang, Christina
@ 2013-04-07 6:23 ` Huang, Christina
2013-04-07 15:01 ` Anderson Lizardo
2 siblings, 1 reply; 6+ messages in thread
From: Huang, Christina @ 2013-04-07 6:23 UTC (permalink / raw)
To: Anderson Lizardo; +Cc: linux-bluetooth
Hi, Anderson
I met one more issue on connecting with Wahoo BlueSC BLE speed / cadence sensor device, it could be discovered successfully, while fails in connection and reports error " Command Disallowed ". Could you suggest what I could do to allow the "connect" command?
I found this same issue reported before but no available answer.
http://www.spinics.net/lists/linux-bluetooth/msg30681.html
Thank you very much.
Christina
@ Device Found: EF:CE:46:33:62:F6 (2) rssi -55 flags 0x0000
02 01 06 03 02 16 18 12 09 57 61 68 6f 6f 20 42 .........Wahoo B
6c 75 65 53 43 20 76 31 2e 34 lueSC v1.4
< HCI Command: LE Create Connection (0x08|0x000d) plen 25 [hci0] 6.358536
Scan interval: 60.000 msec (0x0060)
Scan window: 30.000 msec (0x0030)
Filter policy: White list is not used (0x00)
Peer address type: Random (0x01)
Address: EF:CE:46:33:62:F6 (Static)
Own address type: Public (0x00)
Min connection interval: 50.00 msec (0x0028)
Max connection interval: 70.00 msec (0x0038)
Connection latency: 0x0000
Supervision timeout: 420 msec (0x002a)
Min connection length: 0.000 msec (0x0000)
Max connection length: 0.000 msec (0x0000)
> HCI Event: Command Status (0x0f) plen 4 [hci0] 6.360646
LE Create Connection (0x08|0x000d) ncmd 1
Status: Command Disallowed (0x0c)
-----Original Message-----
From: Anderson Lizardo [mailto:anderson.lizardo@openbossa.org]
Sent: Friday, March 08, 2013 10:00 PM
To: Huang, Christina
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: one question on BLE device authentication error
Hi Christina,
On Fri, Mar 8, 2013 at 3:54 AM, Huang, Christina <christina.huang@intel.com> wrote:
> < HCI Command: LE Start Encryption (0x08|0x0019) plen 28 [hci0] 5.724000
> Handle: 71
> Random number: 8c126b665d2de279
> Encryption diversifier: 0x3f55
> Long term key: dcd74a1a07f653c0e27f65888debcbe5 @ Device
> Connected: 00:17:EA:91:8C:78 (1) flags 0x0000
>> HCI Event: Command Status (0x0f) plen 4 [hci0] 5.733922
> LE Start Encryption (0x08|0x0019) ncmd 1
> Status: Success (0x00)
>> ACL Data RX: Handle 71 flags 0x02 dlen 6 [hci0] 5.835521
> SMP: Security Request (0x0b) len 1
> Authentication requirement: Bonding - MITM (0x05)
>> HCI Event: Encryption Change (0x08) plen 4 [hci0] 6.115911
> Status: PIN or Key Missing (0x06)
> Handle: 71
> Encryption: Disabled (0x00)
It looks like your LE device lost the bonding information (e.g. LTK) and thus is not able to just encrypt the connection with the LTK BlueZ is trying to use. You can try removing the bonding on BlueZ side (e.g.
"test-device remove <bdaddr>" or "remove <bdaddr>" on bluetoothctl) and try again a complete pairing.
Best regards,
--
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: one question on BLE device authentication error
2013-04-07 6:23 ` Huang, Christina
@ 2013-04-07 15:01 ` Anderson Lizardo
0 siblings, 0 replies; 6+ messages in thread
From: Anderson Lizardo @ 2013-04-07 15:01 UTC (permalink / raw)
To: Huang, Christina; +Cc: linux-bluetooth
Hi Christina,
On Sun, Apr 7, 2013 at 2:23 AM, Huang, Christina
<christina.huang@intel.com> wrote:
>
> Hi, Anderson
>
> I met one more issue on connecting with Wahoo BlueSC BLE speed / cadence sensor device, it could be discovered successfully, while fails in connection and reports error " Command Disallowed ". Could you suggest what I could do to allow the "connect" command?
> I found this same issue reported before but no available answer.
> http://www.spinics.net/lists/linux-bluetooth/msg30681.html
How are you doing the device discovery? You should use the BlueZ D-Bus
API instead of "hcitool lescan", because some (most?) BLE controllers
do not allow connection creation while in LE scanning state. If I
remember correctly, If the D-Bus API is always used the LE scan is
always disabled prior to LE Create Connection.
Also make sure you are not in advertising state (i.e. you did not run
"hciconfig hci0 leadv").
Best Regards,
--
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-04-07 15:01 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-08 7:54 one question on BLE device authentication error Huang, Christina
2013-03-08 13:59 ` Anderson Lizardo
2013-03-11 1:33 ` Huang, Christina
2013-03-11 4:17 ` Huang, Christina
2013-04-07 6:23 ` Huang, Christina
2013-04-07 15:01 ` Anderson Lizardo
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.