From: Marcel Holtmann <marcel@holtmann.org>
To: Jessica Huang <jessieh@MIT.EDU>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bd_addr question
Date: Tue, 09 Mar 2004 22:24:11 +0100 [thread overview]
Message-ID: <1078867451.10671.73.camel@pegasus> (raw)
In-Reply-To: <5.2.1.1.2.20040309150546.02e414a0@po14.mit.edu>
Hi Jessica,
> I'm not sure if this is the right place to ask, but I had a question about
> the Bluetooth Device Address. From my understanding, the BD_ADDR is stored
> on the Bluetooth transmitter. I was wondering if it is possible to
> intercept that address and provide some arbitrary one. Could someone
> please explain how this address is accessed and by what modules?
what do you mean with intercept? I don't get any idea of what you are
trying to achieve.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-03-09 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 20:12 [Bluez-devel] bd_addr question Jessica Huang
2004-03-09 21:24 ` Marcel Holtmann [this message]
[not found] ` <5.2.1.1.2.20040309190444.02e6e250@po14.mit.edu>
2004-03-10 0:23 ` Marcel Holtmann
2004-03-10 9:46 ` Collin R. Mulliner
-- strict thread matches above, loose matches on Subject: below --
2004-03-10 7:45 Michael Schmidt
2004-03-10 11:22 ` Steven Singer
2004-03-10 16:04 Mark RISON
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=1078867451.10671.73.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jessieh@MIT.EDU \
/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