Subject: From: Date:

Re: [ecs] a more general bluetooth question (clarification) Mark Gilmore Sat, 15 Apr 2006 08:59:19 -0400

---

If a BT had an IP address, my work would be all but completed.
But they seem to use different addressing:
http://www.securityfocus.com/infocus/1830 :
The Bluetooth address itself is a unique 48bit device identifier, 
where the first 3 bytes of the address are assigned to a specific 
manufacturer by the IEEE (www.ieee.org/), and the last 3 bytes are 
freely allocated by the manufacturer. For example, the hexadecimal 
representation of a Sony Ericsson P900 phone's Bluetooth address may 
look like 00:0A:D9:EB:66:C7, where the first 3 bytes of this address 
(00:0A:D9) are registered to Sony Ericsson by the IEEE, meaning that 
all P900 phones will have their Bluetooth address starting with same 
3 bytes. The last 3 bytes (EB:66:C7) of the sample address are 
assigned to this device by Sony Ericsson and should be different for 
each P900 phone -- but is not always, unfortunately.

An inventory *is* possible with VC++:
http://windowssdk.msdn.microsoft.com/library/default.asp?url=/library/en-us/bluetooth/bluetooth/bluetooth_and_wsalookupservicebegin_for_device_inquiry.asp
But my 2003 version of VC++ apparently lacks this support
(as the required "NS_BTH" constant is not found in any of my MSVC inc files).

I have yet to find an executable that does it (other than 
"BTExplorer", which is apparently very expensive - you have to email 
them for a price).

So I'm now looking into a JAVA solution "JSR 82: JavaTM APIs for Bluetooth":
         http://www.jcp.org/en/jsr/detail?id=82
I downloaded this package, but it has no library (only source code 
function templates).
So I'm now trying to find the *complete* installation ...

At 08:45 AM 4/15/2006, you wrote:

>Mark Gilmore wrote:
>
>>this is the goal and possible solutions that i envision:
>>goal:
>>to know when *any desired* BT device is within the area (for 
>>proximity detection)
>
>ok, than at the moment it could be about "any" kind of device.
>
>>possible solutions (best to worst):
>>1) OS system calls (or a sys utility) could periodically discover 
>>all active BT devices
>>I'm looking into this now:
>>http://windowssdk.msdn.microsoft.com/library/default.asp?url=/library/en-us/bluetooth/bluetooth/discovering_bluetooth_devices_and_services.asp

>>
>
>this looks fine, I didn't know about it.
>
>>2) Commercial utility pgm could do same as above (some cost to customer)
>>3) Adapter/software combo would do same (more cost to customer)
>
>In this case I guess that "ipconfig /all" could be used to show 
>network adapters (if you enable that service on your bluetooth) and 
>parsing its output would provide info. Or even pinging the address.
>
>
>--
>Ciao, Dario
>
>
>
>
>--
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.385 / Virus Database: 268.4.1/312 - Release Date: 4/14/2006
>
>
>
>
>--
>No virus found in this incoming message.
>Checked by AVG Anti-Virus.
>Version: 7.1.385 / Virus Database: 268.4.1/312 - Release Date: 4/14/2006

Mark Gilmore
http://OmnipotenceSoftware.com 


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.1.385 / Virus Database: 268.4.1/312 - Release Date: 4/14/2006

---