All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Singer <steven.singer@csr.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] passive inquiry
Date: Fri, 17 Dec 2004 14:53:15 +0000	[thread overview]
Message-ID: <41C2F2DB.5010204@csr.com> (raw)
In-Reply-To: <200412171534.03946.bluez-user@schaettgen.de>

Fred Schaettgen wrote:
> On Friday 17 December 2004 15:18, Paolino paperino wrote:
>> Hi,
>> i want to know if it is possible to make a "passive
>> inquiry", i explain better, a device A do an inquiry
>> no find their neighbours, it is possible for a device
>> B (in the reachability field) to know that was
>> inquiried by device A? The applican can receive an
>> event each time the device is inquiried?
> 
> No, that is not possible in general. 
> The bluetooth chip responds to the inquiry without generating any HCI events. 
> You can see SDP requests, since those are handled by the Bluetooth stack, but 
> that won't help you much I guess. Maybe there are vendor-specific commands to 
> make that possible, but I don't know about any.

No, even vendor specific commands don't help. In the inquiry procedure
at the baseband no identity information flows from the inquirer to the
scanner. The only thing the scanner can tell is that somebody has
inquired.

As an analogy, inquiry works like this. The inquirer sends out a
message which means "Can anybody who can hear me identify themselves"
and gets responses like "I heard you, I'm 0x123456789abc and I'm a
headset". Hence, the inquirer knows the identity of the devices that
have responded but the scanners gets nothing from the inquirer.

Future changes to the inquiry spec might allow extra information to
be passed from the scanner to the inquirer, but not from the inquirer
to the scanner.

If the scanner responds to the inquirer and then the inquirer follows
it up with a remote name request or an HCI level connection then at that
point the inquirer reveals its address. In the former case, the
information is available at the baseband, but is not passed up to the
host. In the latter case, the host is informed of the address of the
device that has connected.

However, completely passive identification, as you describe, is not
possible.

	- Steven



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-12-17 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 13:48 [Bluez-users] l2cap retransmission Manjunath Prabhu
2004-12-17 14:18 ` [Bluez-users] passive inquiry Paolino paperino
2004-12-17 14:24   ` Marcel Holtmann
2004-12-17 14:30   ` Peter Stephenson
2004-12-17 14:34   ` Fred Schaettgen
2004-12-17 14:53     ` Steven Singer [this message]
2005-03-02 13:57       ` Paolino paperino
2005-03-02 16:21         ` Stephen Crane
2004-12-17 14:26 ` [Bluez-users] l2cap retransmission Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41C2F2DB.5010204@csr.com \
    --to=steven.singer@csr.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.