2015-09-08 08:24:03

by Zheng, Wu

Subject: "SMP security requested but not available" when BT_6lowpan connection

Hi all,

When I use kernel 4.1.6 to test BT 6lowpan, the error of "SMP security requested but not available" is shown.

1. I use bluetoothctl power on

2. echo 1 > 6lowpan_enable

3. echo "connect 00:XX:XX:XX:XX:XX:XX 1" > 6lowpan_control.

Then "SMP security requested but not available".

I test kernel 4.1.3 and BT 6lowpan works well.

Any suggestion? Thanks.

Best Regards
Zheng Wu

2015-09-09 06:46:27

by Zheng, Wu

Subject: RE: "SMP security requested but not available" when BT_6lowpan connection

Hi Marcel,

I will try it. Thanks.

Best Regards
Zheng Wu

-----Original Message-----
From: Marcel Holtmann [mailto:[email protected]]=20
Sent: Wednesday, September 9, 2015 1:59 PM
To: Zheng, Wu
Cc: [email protected]
Subject: Re: "SMP security requested but not available" when BT_6lowpan con=
nection

Hi Wu,

> When I use kernel 4.1.6 to test BT 6lowpan, the error of "SMP security re=
quested but not available" is shown.
>=20
> 1. I use bluetoothctl power on
>=20
> 2. echo 1 > 6lowpan_enable
>=20
> 3. echo "connect 00:XX:XX:XX:XX:XX:XX 1" > 6lowpan_control.
>=20
> Then "SMP security requested but not available".
>=20
> I test kernel 4.1.3 and BT 6lowpan works well.
>=20
> Any suggestion? Thanks.

can try to boot a bluetooth-next kernel and see if the error is still prese=
nt. We included a fix for the warning.

Regards

Marcel

2015-09-09 05:58:30

by Marcel Holtmann

Subject: Re: "SMP security requested but not available" when BT_6lowpan connection

Hi Wu,

> When I use kernel 4.1.6 to test BT 6lowpan, the error of "SMP security requested but not available" is shown.
>
> 1. I use bluetoothctl power on
>
> 2. echo 1 > 6lowpan_enable
>
> 3. echo "connect 00:XX:XX:XX:XX:XX:XX 1" > 6lowpan_control.
>
> Then "SMP security requested but not available".
>
> I test kernel 4.1.3 and BT 6lowpan works well.
>
> Any suggestion? Thanks.

can try to boot a bluetooth-next kernel and see if the error is still present. We included a fix for the warning.

Regards

Marcel