* [Bluez-devel] New HCI-USB device, no MAC?
@ 2006-03-09 10:52 Nils Faerber
2006-03-09 13:51 ` Marcel Holtmann
0 siblings, 1 reply; 16+ messages in thread
From: Nils Faerber @ 2006-03-09 10:52 UTC (permalink / raw)
To: bluez-devel
-----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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] New HCI-USB device, no MAC?
2006-03-09 10:52 [Bluez-devel] New HCI-USB device, no MAC? Nils Faerber
@ 2006-03-09 13:51 ` Marcel Holtmann
2006-03-09 15:46 ` Nils Faerber
0 siblings, 1 reply; 16+ messages in thread
From: Marcel Holtmann @ 2006-03-09 13:51 UTC (permalink / raw)
To: 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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] New HCI-USB device, no MAC?
2006-03-09 13:51 ` Marcel Holtmann
@ 2006-03-09 15:46 ` Nils Faerber
2006-03-09 16:56 ` Marcel Holtmann
0 siblings, 1 reply; 16+ messages in thread
From: Nils Faerber @ 2006-03-09 15:46 UTC (permalink / raw)
To: 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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] New HCI-USB device, no MAC?
2006-03-09 15:46 ` Nils Faerber
@ 2006-03-09 16:56 ` Marcel Holtmann
2006-04-12 20:00 ` [Bluez-devel] " Evan Paul Fletcher
0 siblings, 1 reply; 16+ messages in thread
From: Marcel Holtmann @ 2006-03-09 16:56 UTC (permalink / raw)
To: 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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bluez-devel] Re: New HCI-USB device, no MAC?
2006-03-09 16:56 ` Marcel Holtmann
@ 2006-04-12 20:00 ` Evan Paul Fletcher
2006-04-12 20:09 ` Marcel Holtmann
2006-04-24 10:54 ` Nils Faerber
0 siblings, 2 replies; 16+ messages in thread
From: Evan Paul Fletcher @ 2006-04-12 20:00 UTC (permalink / raw)
To: bluez-devel
Marcel Holtmann <marcel <at> holtmann.org> writes:
>
> 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
>
Hi Marcel,
Did anyone ever find a solution/workaround for these ISSC-based dongles? I seem
to have acquired two dongles with a BD_ADDR of 11:11:11:11:11:11 and from
searching Google, it seems that a lot of other people are in the same boat.
Cheers,
Evan Paul Fletcher
-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] Re: New HCI-USB device, no MAC?
2006-04-12 20:00 ` [Bluez-devel] " Evan Paul Fletcher
@ 2006-04-12 20:09 ` Marcel Holtmann
2006-04-13 6:02 ` Sowmya Gattupalli
2006-04-24 10:54 ` Nils Faerber
1 sibling, 1 reply; 16+ messages in thread
From: Marcel Holtmann @ 2006-04-12 20:09 UTC (permalink / raw)
To: bluez-devel
Hi Evan,
> Did anyone ever find a solution/workaround for these ISSC-based dongles? I seem
> to have acquired two dongles with a BD_ADDR of 11:11:11:11:11:11 and from
> searching Google, it seems that a lot of other people are in the same boat.
no idea. The ISSC guys need to contact me and they haven't so far. From
my point I am no longer running after the manufacturers. Simply buy a
device with a CSR chip and you are happy.
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] Re: New HCI-USB device, no MAC?
2006-04-12 20:09 ` Marcel Holtmann
@ 2006-04-13 6:02 ` Sowmya Gattupalli
2006-04-13 6:30 ` Mayank Batra
0 siblings, 1 reply; 16+ messages in thread
From: Sowmya Gattupalli @ 2006-04-13 6:02 UTC (permalink / raw)
To: bluez-devel
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
Hi Marcel...
Even I was facing similar problems with the ISSC dongles... but I guess in
India there is a shortage of CSR chipset based dongles.........
Indians anyone who have CSR bluetooth dongle please let me know whr u can
find it...,,,,,,,,,,, this is a SOS message....
i have one CSR one which is bought 4 yrs back but not able to find the
sources of the manufacturer.... I hope someone staying in India will help me
out in this....
On 4/13/06, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Evan,
>
> > Did anyone ever find a solution/workaround for these ISSC-based
> dongles? I seem
> > to have acquired two dongles with a BD_ADDR of 11:11:11:11:11:11 and
> from
> > searching Google, it seems that a lot of other people are in the same
> boat.
>
> no idea. The ISSC guys need to contact me and they haven't so far. From
> my point I am no longer running after the manufacturers. Simply buy a
> device with a CSR chip and you are happy.
>
> 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
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
[-- Attachment #2: Type: text/html, Size: 2114 bytes --]
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] Re: New HCI-USB device, no MAC?
2006-04-13 6:02 ` Sowmya Gattupalli
@ 2006-04-13 6:30 ` Mayank Batra
0 siblings, 0 replies; 16+ messages in thread
From: Mayank Batra @ 2006-04-13 6:30 UTC (permalink / raw)
To: bluez-devel
[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]
Sowmya,
I have not heard of any shortage of CSR Dongles in India.
You'll find them all over. (and pretty cheap as well)
But why do you need CSR dongles only...there are a number of other
manufacturer as well (I'm using Silicon Wave's dongle)
Mayank
On 4/13/06, Sowmya Gattupalli <sowmya.gattupalli@gmail.com> wrote:
>
> Hi Marcel...
> Even I was facing similar problems with the ISSC dongles... but I guess in
> India there is a shortage of CSR chipset based dongles.........
>
> Indians anyone who have CSR bluetooth dongle please let me know whr u can
> find it...,,,,,,,,,,, this is a SOS message....
> i have one CSR one which is bought 4 yrs back but not able to find the
> sources of the manufacturer.... I hope someone staying in India will help me
> out in this....
>
>
> On 4/13/06, Marcel Holtmann <marcel@holtmann.org> wrote:
> >
> > Hi Evan,
> >
> > > Did anyone ever find a solution/workaround for these ISSC-based
> > dongles? I seem
> > > to have acquired two dongles with a BD_ADDR of 11:11:11:11:11:11 and
> > from
> > > searching Google, it seems that a lot of other people are in the same
> > boat.
> >
> > no idea. The ISSC guys need to contact me and they haven't so far. From
> > my point I am no longer running after the manufacturers. Simply buy a
> > device with a CSR chip and you are happy.
> >
> > 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
> > Bluez-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-devel
> >
>
>
[-- Attachment #2: Type: text/html, Size: 3218 bytes --]
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] Re: New HCI-USB device, no MAC?
2006-04-12 20:00 ` [Bluez-devel] " Evan Paul Fletcher
2006-04-12 20:09 ` Marcel Holtmann
@ 2006-04-24 10:54 ` Nils Faerber
2006-04-24 11:04 ` Marcel Holtmann
1 sibling, 1 reply; 16+ messages in thread
From: Nils Faerber @ 2006-04-24 10:54 UTC (permalink / raw)
To: bluez-devel
Evan Paul Fletcher schrieb:
> Marcel Holtmann <marcel <at> holtmann.org> writes:
>> 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
> Hi Marcel,
>
> Did anyone ever find a solution/workaround for these ISSC-based dongles? I seem
> to have acquired two dongles with a BD_ADDR of 11:11:11:11:11:11 and from
> searching Google, it seems that a lot of other people are in the same boat.
I have contacted ISSC about that issue.
Hopefully the will reply and send the HCI or whatever commands
necessary... I have two of those dongles which renders at least one
useless (I guess two times the same BDADDR will not work in a piconet ;)
> Cheers,
> Evan Paul Fletcher
Cheers
nils faerber
--
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
--
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] Re: New HCI-USB device, no MAC?
2006-04-24 10:54 ` Nils Faerber
@ 2006-04-24 11:04 ` Marcel Holtmann
2006-04-28 10:54 ` Nils Faerber
0 siblings, 1 reply; 16+ messages in thread
From: Marcel Holtmann @ 2006-04-24 11:04 UTC (permalink / raw)
To: bluez-devel
Hi Nils,
> > Did anyone ever find a solution/workaround for these ISSC-based dongles? I seem
> > to have acquired two dongles with a BD_ADDR of 11:11:11:11:11:11 and from
> > searching Google, it seems that a lot of other people are in the same boat.
>
> I have contacted ISSC about that issue.
>
> Hopefully the will reply and send the HCI or whatever commands
> necessary... I have two of those dongles which renders at least one
> useless (I guess two times the same BDADDR will not work in a piconet ;)
actually it should work, but at the moment BlueZ is blocking this. You
can't connect to yourself.
Regards
Marcel
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] Re: New HCI-USB device, no MAC?
2006-04-24 11:04 ` Marcel Holtmann
@ 2006-04-28 10:54 ` Nils Faerber
2006-11-15 13:08 ` [Bluez-devel] " Nils Faerber
0 siblings, 1 reply; 16+ messages in thread
From: Nils Faerber @ 2006-04-28 10:54 UTC (permalink / raw)
To: bluez-devel
Hi!
In case anyone else is interested in this issue too, as I said I
contacted ISSC about missing MAC addresses and after some mail ping-pong
got the following response. They really seem to care about the issue
now. I just still wonder what will happen.
So, here come the emails, starting with the last reply from one of their
managers:
"Dear Nils:
Thank you very much for your comment. First of all, ISSC is the one of
important BT IC provider. We also provide one robust reference board design
solution for our system customers. This reference design had passed BQB
certification to our system customers for class 2 dongle. In the reference
design, BT Address will be saved in the on board EEPROM. It's the unique BT
address with legal IVT software without exception. For products shipped with
EEPROM, BT_Addr can be changed through HCI command. However, for dongles
shipped without EEPROM, there is no place to store the new BT_addr. Anyway,
ISSC also believe this is a very serious issue, and we have also contacted
Bluetooth SIG to ask for their advise of this specific problems.
Unfortunately, we have not receive any response from them yet. As stated in
our previous email response to you, ISSC "ALWAYS" ship our IC with a legal
IVT software without exceptions. Unfortunately, some manufacturers went for
the extreme to save manufacturing cost at the expense of BT quality. I'm
including this message to Mike Foley so that he is more aware of this
problem. ISSC will do whatever it takes to solve this problems. By the way,
it is because ISSC's products has a very large market share, hence you see
most problems with our products. I can assure you that this problem is not
ISSC isolated instance. It is a problem that we will like to resolve as much
as you do, if no more than you do. For, this will hurt our BT industry as a
whole more than anything else. Regarding to your recommandation, if we can
change the BT Address through the HCI interface. Because IVT software is the
only one software interface between the User and USB BT Dongle. ISSC will
discuss with IVT to check if any solution for it soon.
Thank you very much for your understanding, and let's see if we can come
out with a solution to resolve this issue.
Sincerely yours,
I.S.S.C./Sales Division
2006/4/28"
----- Original Message -----
From: "ISSC Sales" <Sales@issc.com.tw>
To: "Nils Faerber" <nils.faerber@kernelconcepts.de>
Sent: Friday, April 28, 2006 10:36 AM
Subject: Re: Inquiry Form[BT Dongle issue]
> > Dear Sir:
> >
> > Very thank you for your kindly and useful reponds and suggestion.
> > We will pass your mail to our manager seriously.
> >
> > Thank you very much again!!
> >
> > Sincerely yours,
> > I.S.S.C./W
> > 2006/4/28
> >
> >
> >
> > ----- Original Message -----
> > From: "Nils Faerber" <nils.faerber@kernelconcepts.de>
> > To: "ISSC Sales" <Sales@issc.com.tw>
> > Sent: Thursday, April 27, 2006 6:58 PM
> > Subject: Re: Inquiry Form[BT Dongle issue]
> >
> >
>> > > ISSC Sales schrieb:
>>> > > > Dear Sir:
>> > > Hello!
>> > >
>> > > Thanks for your quick response!
>> > >
>>> > > > I.S.S.C. is a IC Vendor.
>>> > > > We offer BT IC with IVT sw together only.
>>> > > > We do not manufacture or sell any end product.
>> > >
>> > > Yes, I know.
>> > > But the described issue does not only occur with a specific
product but
>> > > with *most* ISSC based products.
>> > >
>>> > > > Therefor,Your bluetooth dongle is not I.S.S.C.'s product.
>>> > > > They just use I.S.S.C.'s chip and solution.
>> > >
>> > > Yes, correct.
>> > >
>>> > > > Your dongle should be NG product, please contact your original
>>> > > > seller/manufactur to solve end product issue for more
>>> > > > support.[ From the item "KY-BT100 ", here help you to find their
> > original
>>> > > > web-site
>>> > > >
> >
http://www.made-in-china.com/showroom/yagudo/product-list/catalog-1.html.
>>> > > > Hope it will be much helpful to you. Thank you very much! ]
>> > >
>> > > Frankly, no, it was not helpful.
>> > >
>> > > You are the manufatcurer of the chipset and baseband software,
i.e. you
>> > > have the knowledge of the verdor specific HCI commands of your chips.
>> > > Most manufacturers will not deal with such details and just implement
>> > > your provided solution.
>> > >
>> > > But even if, I still think that it is your responsibility to get your
>> > > product based end user products right. ISSC is currently the only
>> > > chipset manufacturer with the problem of not providing correct
Bluetooth
>> > > addresses. So this must be also your problem not only the
integrator's.
>> > >
>> > > The only simple thing I am asking you for is the single simple HCI
>> > > command to set a correct Bluetooth MAC address.
>> > >
>> > > Please have a look on the market today and test-buy some products
that
>> > > implement your ISSC Bluetooth chipset. I would bet that more than
50% do
>> > > not carry a valid Bluetooth address which is a violation of the
>> > > Bluetooth specification.
>> > >
>> > > So please rethink your position and provide the HCI command or at
least
>> > > a ready made tool (e.g. for Windows-OS) to set the Bluetooth address.
>> > > Also please get in contact with your customers so that they pay
closer
>> > > attention to this issue! There are numerous reports about e.g.
Bluetooth
>> > > headsets that all have the same Bluetooth address (i.e.
>> > > 11:11:11:11:11:11). In such a situation it would be impossible to
have
>> > > more than one of those in the same piconet. An unacceptable
situation.
>> > > This has never been reported with chipsets e.g. from CSR.
>> > >
>>> > > > Sincerely yours,
>>> > > > I.S.S.C./W.
>>> > > > 2006/4/27
>> > > Best regards
>> > > nils faerber
>> > >
>> > >
>>> > > > ----- Original Message -----
>>> > > > From: "Nils Faerber" <nils.faerber@kernelconcepts.de>
>>> > > > To: <sales@issc.com.tw>
>>> > > > Sent: Wednesday, April 26, 2006 5:35 PM
>>> > > > Subject: Inquiry Form
>>> > > >
>>> > > >
>>>> > > >> Interested in=Bluetooth Product
>>>> > > >> Solution=USB Dongle
>>>> > > >> Product=
>>>> > > >> Enquiry for=FAE
>>>> > > >> Company=kernel concepts
>>>> > > >> product=Operating software development
>>>> > > >> URL=http://www.kernelconcepts.de
>>>> > > >> Country=DE
>>>> > > >> Address=Dreisbachstr. 24, D-57250 Netphen
>>>> > > >> person=Nils Faerber
>>>> > > >> job=CTO
>>>> > > >> email=nils.faerber@kernelconcepts.de
>>>> > > >> Tel=+49-271-77109112
>>>> > > >> Fax=+49-271-77109119
>>>> > > >> Description=Dear ladies an gentlemen!
>>>> > > >> We are a software development company concentrated on Linux
kernel
and
>>>> > > >> system development. We are member of the Bluetooth SIG since
2000
> > (early
>>>> > > >> adopter) and have been part in the Linux Bluetooth stack
development
>>>> > > >> from the very early beginning.
>>>> > > >>
>>>> > > >> A customer of ours wants to deploy a device that uses your
Bluetooth
> > USB
>>>> > > >> chipset:
>>>> > > >>
>>>> > > >> ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth
> > Adapter
>>>> > > >>
>>>> > > >> The problem we currently have with those devices is that
they do not
>>>> > > >> contain a valid Bluetooth MAC address, they come with a
default of
>>>> > > >> 11:11:11:11:11:11. We have seen this with all ISSC dongles.
We have
>>>> > > >> USB-HCI description for CSR based modules to change the MAC
address
to
> > a
>>>> > > >> correct value but not for your modules.
>>>> > > >>
>>>> > > >> So we would like to ask for your kind assistance! We just
need to
know
>>>> > > >> the HCI command to set the MAC (Bluetooth) address of thode
dongles.
>>>> > > >>
>>>> > > >> This would help us a lot and our customer can continue to
use your
fine
>>>> > > >> chips.
>>>> > > >>
>>>> > > >> Many thanks in advance for any information you can provide!
>>>> > > >>
>>>> > > >> Kind regards
>>>> > > >> nils faerber
>>>> > > >>
>>>> > > >> PS: If we need to sign an NDA to get this information I
would gladly
do
>>> > > > so.
>>>> > > >> Result=Send
>>>> > > >>
>>>> > > >> --
>>>> > > >> kernel concepts Tel: +49-271-771091-12
>>>> > > >> Dreisbachstr. 24 Fax: +49-271-771091-19
>>>> > > >> D-57250 Netphen Mob: +49-176-21024535
>>>> > > >> --
>>>> > > >>
>>>> > > >>
>>> > > >
>> > >
>> > > --
>> > > kernel concepts Tel: +49-271-771091-12
>> > > Dreisbachstr. 24 Fax: +49-271-771091-19
>> > > D-57250 Netphen Mob: +49-176-21024535
>> > > --
>> > >
> >
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] New HCI-USB device, no MAC?
2006-04-28 10:54 ` Nils Faerber
@ 2006-11-15 13:08 ` Nils Faerber
2006-11-15 13:47 ` Marcel Holtmann
0 siblings, 1 reply; 16+ messages in thread
From: Nils Faerber @ 2006-11-15 13:08 UTC (permalink / raw)
To: bluez-devel
[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]
Hello all!
Maybe some of you still remember this thread...
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.
I have attached a tarball of my udev rule and script to this post which
works quite nicely for me. If anyone else finds it useful I would be
happy to receive comments ;)
And finally I would like to ask, how can we try to get this into
distributions? Shall I change anything in the scripts? Can we get it
into some bluez package?
Thanks!
Cheers
nils
--
kernel concepts GbR Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
--
[-- Attachment #2: hcibdaddrhack.tar.gz --]
[-- Type: application/x-gzip, Size: 1004 bytes --]
[-- Attachment #3: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] New HCI-USB device, no MAC?
2006-11-15 13:08 ` [Bluez-devel] " Nils Faerber
@ 2006-11-15 13:47 ` Marcel Holtmann
2006-11-15 14:50 ` Nils Faerber
2006-11-15 15:05 ` Stefan Seyfried
0 siblings, 2 replies; 16+ messages in thread
From: Marcel Holtmann @ 2006-11-15 13:47 UTC (permalink / raw)
To: BlueZ development
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] New HCI-USB device, no MAC?
2006-11-15 13:47 ` Marcel Holtmann
@ 2006-11-15 14:50 ` Nils Faerber
2006-11-15 15:05 ` Stefan Seyfried
1 sibling, 0 replies; 16+ messages in thread
From: Nils Faerber @ 2006-11-15 14:50 UTC (permalink / raw)
To: BlueZ development
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] New HCI-USB device, no MAC?
2006-11-15 13:47 ` Marcel Holtmann
2006-11-15 14:50 ` Nils Faerber
@ 2006-11-15 15:05 ` Stefan Seyfried
2006-11-16 10:35 ` Marcel Holtmann
1 sibling, 1 reply; 16+ messages in thread
From: Stefan Seyfried @ 2006-11-15 15:05 UTC (permalink / raw)
To: BlueZ development
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Bluez-devel] New HCI-USB device, no MAC?
2006-11-15 15:05 ` Stefan Seyfried
@ 2006-11-16 10:35 ` Marcel Holtmann
0 siblings, 0 replies; 16+ messages in thread
From: Marcel Holtmann @ 2006-11-16 10:35 UTC (permalink / raw)
To: BlueZ development
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2006-11-16 10:35 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-09 10:52 [Bluez-devel] New HCI-USB device, no MAC? Nils Faerber
2006-03-09 13:51 ` Marcel Holtmann
2006-03-09 15:46 ` Nils Faerber
2006-03-09 16:56 ` Marcel Holtmann
2006-04-12 20:00 ` [Bluez-devel] " Evan Paul Fletcher
2006-04-12 20:09 ` Marcel Holtmann
2006-04-13 6:02 ` Sowmya Gattupalli
2006-04-13 6:30 ` Mayank Batra
2006-04-24 10:54 ` Nils Faerber
2006-04-24 11:04 ` Marcel Holtmann
2006-04-28 10:54 ` Nils Faerber
2006-11-15 13:08 ` [Bluez-devel] " Nils Faerber
2006-11-15 13:47 ` Marcel Holtmann
2006-11-15 14:50 ` Nils Faerber
2006-11-15 15:05 ` Stefan Seyfried
2006-11-16 10:35 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).