Re: Security block and Bluez 5.47

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Luiz,

On Wed, Nov 15, 2017, Luiz Augusto von Dentz wrote:
> > Frequently when I connect my Android phone to my bluez 5.47 device I
> > see (btmon):
> >
> >  > HCI Event: Number of Completed Packets (0x13) plen 5
> >
> >                                                             #36 [hci0]
> > 5.709020
> >          Num handles: 1
> >          Handle: 1
> >          Count: 1
> >  < ACL Data TX: Handle 1 flags 0x00 dlen 16
> >
> >                                                             #37 [hci0]
> > 5.714589
> >        L2CAP: Connection Response (0x03) ident 4 len 8
> >          Destination CID: 64
> >          Source CID: 81
> >          Result: Connection refused - security block (0x0003)
> >          Status: No further information available (0x0000)
> >
> > This is using connecting from Android 7 to Bluez 5.47.
> 
> I think this might be due to not having a default agent set which is
> needed if the devices is not trusted so it would require agent
> authorization.

It could also be the USB HCI race between ACL data and HCI events. It's
hard to say for sure though since the complete HCI log was not provided.

Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux