Thank your Marcel for the clarification. As Luiz mentioned previously though, as random static addresses can be used by other devices, it may makes sense to avoid caching their name. Would you agree? On Thu, Jun 23, 2016 at 3:29 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > Hi Francois, > >> I have a bluetooth beacon device that advertises a name depending on >> its configuration (connectable or not). >> Sadly, in Bluez, the first time it sees it while advertising its name, >> it caches it which is nice for future discovery. >> Except it doesn't because I don't want to see this name while it >> advertises in non-connectable state as it is "not" the same device >> anymore (sort of). >> I guess what I'm asking is if we can make Device name aware of the >> connectable state and only use it if it matches state when it was >> cached. > > yikes, this is super tricky. If the device uses the same address, then it is the same device. If it is not the same device, then it should use two different addresses (sort of a dual personality). > > Please keep in mind that a lot of device identity is based around either the public address or the static random address. We even clarified that as identity address in the latest specification. The mode has nothing to do with it. It makes it even more complicated since a device can be in broadcaster and peripheral role at the same time. It is just a matter of instantiating a second link layer state machine. However even in that case my advise is two use two different addresses if they are independent. > > Regards > > Marcel > -- 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
