Bluez Firmware Mac Address Issue

Bug #1712211 reported by Logan Gunthorpe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Raspbian
New
Undecided
Unassigned

Bug Description

With bluez-firmware version 1.2-3+rpi2 the bluetooth adapter gets a seemingly bogus mac address of 43:43:A1:12:1F:AC. For most purposes, this will likely go unnoticed. However, when creating a PAN the address is considered invalid because the multicast bit is set (bit 0 in the first octet). It also appears to be constant across installations based on the fact that I've found it referenced in [1].

Version 1.2-3+rpi1 does not have this issue and gets a proper mac address starting with B8:27:EB:

Thus, downgrading to rpi1 fixes my issues and rpi2 is broken. I noticed this when upgrading from Jessie to Stretch. Jessie works fine but Stretch does not until the bluez-firmware package is downgraded.

Thanks,

Logan

[1] https://www.raspberrypi.org/forums/viewtopic.php?t=148305&start=100

Revision history for this message
Logan Gunthorpe (lsgunthorpe) wrote :

Oh, I spoke too soon: the old rpi1 firmware gives the correct mac address but seems to break when trying to setup a PAN/NAP connection. It just hangs and doesn't give any hints in terms of logs. The new firmware goes through the NAP setup but breaks because the MAC address is invalid.

Everything worked fine on Jessie though.

I can only assume the new firmware has a bug fix I need but the old firmware has the MAC address bug. I can't find any information on where the firmware originally came from so I can't really find any newer versions to try.

Thanks,

Logan

Revision history for this message
Logan Gunthorpe (lsgunthorpe) wrote :

I've submitted this issue to raspberrypi/firmware as well:

https://github.com/raspberrypi/firmware/issues/860

Revision history for this message
Logan Gunthorpe (lsgunthorpe) wrote :

Per the github issue there's a work around with an updated btuart script. It would be good to get that packaged in raspbian.

Thanks,

Logan

Revision history for this message
Logan Gunthorpe (lsgunthorpe) wrote :

Looks like this was fixed in pi-bluetooth 0.1.6. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.