From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BlueZ: Accepting incoming traffic
Date: Sun, 01 May 2005 16:56:04 +0200 [thread overview]
Message-ID: <1114959364.21785.18.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.30.0505011025590.18702-100000@stealth.kirenet.com>
Hi Joshua,
> This is an impossibility? I know that using hciconfigure and hcid I can
> set what name my computer uses to respond to probes. Something on my
> computer is thus hearing these probes. Is this just taking place in the
> kernel?
it is taking place inside the Bluetooth chip itself. No further
interaction with the host stack is needed.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-01 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 13:38 [Bluez-devel] BlueZ: Accepting incoming traffic Joshua Davis
2005-05-01 13:51 ` Marcel Holtmann
2005-05-01 14:26 ` Joshua Davis
2005-05-01 14:56 ` Marcel Holtmann [this message]
2005-05-01 15:13 ` Joshua Davis
2005-05-01 15:23 ` Marcel Holtmann
2005-05-01 15:41 ` Joshua Davis
2005-05-01 15:48 ` Marcel Holtmann
2005-05-01 20:10 ` [Bluez-devel] authentication problem - link_key prevents from pairing Ruben Jenster
2005-05-01 23:19 ` Marcel Holtmann
2005-05-02 11:27 ` Ruben Jenster
2005-05-02 12:05 ` Marcel Holtmann
2005-05-02 14:57 ` Ruben Jenster
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=1114959364.21785.18.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox