Bug#385019: [Pkg-bluetooth-maintainers] Bug#385019: bluez-utils: dbaddr for EEPROMless devices

Marcel Holtmann marcel at holtmann.org
Mon Aug 28 19:10:14 UTC 2006

Hi Alexander,

> Package: bluez-utils
> Version: 3.1-4
> Severity: wishlist
> Whilst trying to configure a BNEP network I found my friends USB dongle had a wierd hardware address of 
> 11:11:11:11:11:11.  Reading around it turns out this is what happens when the device has no onboard EEPROM 
> and you need to change the address with the 'bdaddr' util found in the 'test' directory in the bluez-utils 
> package.  Unfortunately the Debian package does not ship this binary.
> The Makefile in the 'test' directory does not work too well once made but if you could compile the dbaddr 
> tool with:
> $ cc -g bdaddr.c -Wall -O2 -D_FORTIFY_SOURCE=2 -o bdaddr -I ../common/ -lbluetooth -L ../common/ -lhelper
> And then ship it in a newer release that would be great.

if a binary in bluez-utils is marked as noinst and no configure option
exists, then this is for a reason. The bdaddr utility is too dangerous
to be installed on non-developer systems. And in this case the term
developer means someone who really knows what he is doing.

It is sad you get a dongle with such an address, but the better choice
is too simply return it, because it is broken.

And there is nothing wrong with the Makefile.am in bluez-utils.



More information about the Pkg-bluetooth-maintainers mailing list