-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
I just acquired a new USB Bluetooth dongle.
Upon attachment it is correctly recognised as USB HCI but strangely it
does not carry any valid MAC address:
Requesting information ...
BD Address: 11:11:11:11:11:11
Device Name: piwi-1
LMP Version: 1.2 (0x2) LMP Subversion: 0x1fe
Manufacturer: Integrated System Solution Corp. (57)
Features: 0xbf 0xfe 0x8d 0x78 0x08 0x18 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot
offset>
<timing accuracy> <role switch> <sniff mode> <RSSI>
<channel quality> <SCO link> <HV2 packets> <HV3 packets>
<u-law log> <A-law log> <CVSD> <power control>
<transparent SCO> <broadcast encrypt> <enhanced iscan>
<interlaced iscan> <interlaced pscan> <inquiry with RSSI>
<AFH cap. slave> <AFH cap. master> <AFH class. master>
Is this a known issue for that chipset?
In fact I bought two dongles with the same chipset (but different
casing) and both start with the above default MAC.
Is there a tool to set a valid MAC?
And if so, to which MAC should I set it?
Or would probably the Windows driver program an initial MAC if first
connected to Windows?
Hints are welcome ;)
Thanks!
Cheers
nils faerber
- --
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEEAkKJXeIURG1qHgRAoIeAJoCna5G3toHCDfhsGi3xhaIB6x4HwCeORIk
2Rt4C7bs4ud3spOILcNu1nQ=
=dOEv
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Nils,
> Windows did not change it :(
> Also the tools that com eon the CDROM seem not to be able to change it.
>
> Have you contacted ISSC about that issue already?
>
> It should be forbidden to release hardware without valid BDADDR into the
> market... That is kind of stupid and dangerous.
I think it isn't really the fault of ISSC. It is a stupid module
manufacturer that has not clue that an BD_ADDR suppose to be unique.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marcel Holtmann schrieb:
> Hi Nils,
Hi Marcel!
>>And if so, to which MAC should I set it?
>>Or would probably the Windows driver program an initial MAC if first
>>connected to Windows?
> I need information from ISSC on this, but you might wanna stick it into
> a Windows machine and see if the address changes and you see a different
> address from a Linux machine. Maybe it is kinda ROM version of the chip.
Windows did not change it :(
Also the tools that com eon the CDROM seem not to be able to change it.
Have you contacted ISSC about that issue already?
It should be forbidden to release hardware without valid BDADDR into the
market... That is kind of stupid and dangerous.
> Regards
> Marcel
Cheers
nils faerber
- --
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEEE3VJXeIURG1qHgRAqWMAJ9bBpHbiyzFZQ10ry6U7wAXm38AtgCdHxy6
Sm8wZlsijK6My6SUg4bM5fs=
=WHe6
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Nils,
> I just acquired a new USB Bluetooth dongle.
> Upon attachment it is correctly recognised as USB HCI but strangely it
> does not carry any valid MAC address:
>
> Requesting information ...
> BD Address: 11:11:11:11:11:11
> Device Name: piwi-1
> LMP Version: 1.2 (0x2) LMP Subversion: 0x1fe
> Manufacturer: Integrated System Solution Corp. (57)
> Features: 0xbf 0xfe 0x8d 0x78 0x08 0x18 0x00 0x00
> <3-slot packets> <5-slot packets> <encryption> <slot
> offset>
> <timing accuracy> <role switch> <sniff mode> <RSSI>
> <channel quality> <SCO link> <HV2 packets> <HV3 packets>
> <u-law log> <A-law log> <CVSD> <power control>
> <transparent SCO> <broadcast encrypt> <enhanced iscan>
> <interlaced iscan> <interlaced pscan> <inquiry with RSSI>
> <AFH cap. slave> <AFH cap. master> <AFH class. master>
>
> Is this a known issue for that chipset?
I have another one from this manufacturer that shows 22:22:22:22:22:22.
Dig up the archive and check for my posting of it.
> In fact I bought two dongles with the same chipset (but different
> casing) and both start with the above default MAC.
> Is there a tool to set a valid MAC?
Yes, but it doesn't support ISSC chips at the moment.
> And if so, to which MAC should I set it?
> Or would probably the Windows driver program an initial MAC if first
> connected to Windows?
I need information from ISSC on this, but you might wanna stick it into
a Windows machine and see if the address changes and you see a different
address from a Linux machine. Maybe it is kinda ROM version of the chip.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Stefan,
> > > Then I created a small shell script which sets a "more correct" address
> > > than the default 11:11:11:11:11:11. I assume in this script that an
> > > ethernet device is present in the system as eth0 and use its MAC for the
> > > Bluetooth dongle too.
> > >
> > > I did this for two reasons:
> > > 1. On the same machine I always want to have the same BDADDR, so random
> > > was no choice.
> > > 2. The ethernet addresses also have to follow the same rules as
> > > Bluetooth MAC addresses, i.e. they have to be unique. So the probability
> > > of a collision is very low.
> >
> > and now PAN will stop working, because the eth0 and bnep0 will have the
> > same MAC address. Not a good idea.
>
> Well, after reading http://en.wikipedia.org/wiki/MAC_address i guess that
> we just could set bit 1 of the 6th byte to signal "locally administered"
> _and_ distinguish that address from the ethernet MAC address.
>
> Or is this totally wrong?
>
> But then, what happens if you plug two of those adapters into one machine?
the problem is that this address suppose to be unique and these guys
screwed it up. Period. Whatever you try to solve this will have its
downside somewhere. However using the hostid and actually storing the
value for later use after reboot could maybe a valid solution.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi,
On Wed, Nov 15, 2006 at 02:47:13PM +0100, Marcel Holtmann wrote:
> Hi Nils,
> =
> > Then I created a small shell script which sets a "more correct" address
> > than the default 11:11:11:11:11:11. I assume in this script that an
> > ethernet device is present in the system as eth0 and use its MAC for the
> > Bluetooth dongle too.
> > =
> > I did this for two reasons:
> > 1. On the same machine I always want to have the same BDADDR, so random
> > was no choice.
> > 2. The ethernet addresses also have to follow the same rules as
> > Bluetooth MAC addresses, i.e. they have to be unique. So the probability
> > of a collision is very low.
> =
> and now PAN will stop working, because the eth0 and bnep0 will have the
> same MAC address. Not a good idea.
Well, after reading http://en.wikipedia.org/wiki/MAC_address i guess that
we just could set bit 1 of the 6th byte to signal "locally administered"
_and_ distinguish that address from the ethernet MAC address.
Or is this totally wrong?
But then, what happens if you plug two of those adapters into one machine?
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Marcel Holtmann schrieb:
> Hi Nils,
Hi!
>> Then I created a small shell script which sets a "more correct" address
>> than the default 11:11:11:11:11:11. I assume in this script that an
>> ethernet device is present in the system as eth0 and use its MAC for the
>> Bluetooth dongle too.
>>
>> I did this for two reasons:
>> 1. On the same machine I always want to have the same BDADDR, so random
>> was no choice.
>> 2. The ethernet addresses also have to follow the same rules as
>> Bluetooth MAC addresses, i.e. they have to be unique. So the probability
>> of a collision is very low.
>
> and now PAN will stop working, because the eth0 and bnep0 will have the
> same MAC address. Not a good idea.
Oh... I was not aware of this potential problem since I assumed that the
different network technologies do not share the same MAC space.
OK.
Proposals?
I could probably increment/decrement the MSB or LSB of the ethernet MAC?
> Regards
> Marcel
Cheers
nils faerber
--
kernel concepts GbR Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
--
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Nils,
> The issue was that some Bluetooth dongles do not contain a valid
> Bluetooth MAC address. Well, this is against the spec and so the dongles
> are bad but sometimes users cannot avoid to get such. So I still see the
> need that we do as good as we can to help those users and get those bad
> dongles working.
>
> Long story short, Marcel's bdaddr application contained in the latest
> release of bluez-utils works, at least for the two dongles I have with
> ISS chipsets. So the BDADDR can be set now.
>
> I wanted an automatic solution so that when I plug the dongle in it is
> automatically assigned "an" address. So first I created an udev rule
> that calls an application when the specific USB device with the
> vendorid:deviceid I know to be bad is inserted - in my case 1131:1001
> (plaease let me know more!).
>
> Then I created a small shell script which sets a "more correct" address
> than the default 11:11:11:11:11:11. I assume in this script that an
> ethernet device is present in the system as eth0 and use its MAC for the
> Bluetooth dongle too.
>
> I did this for two reasons:
> 1. On the same machine I always want to have the same BDADDR, so random
> was no choice.
> 2. The ethernet addresses also have to follow the same rules as
> Bluetooth MAC addresses, i.e. they have to be unique. So the probability
> of a collision is very low.
and now PAN will stop working, because the eth0 and bnep0 will have the
same MAC address. Not a good idea.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel