From owner-freebsd-net@FreeBSD.ORG  Thu Jul 22 06:38:23 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3996F16A4CE
	for <freebsd-net@freebsd.org>; Thu, 22 Jul 2004 06:38:23 +0000 (GMT)
Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.245])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2290C43D45
	for <freebsd-net@freebsd.org>; Thu, 22 Jul 2004 06:38:23 +0000 (GMT)
	(envelope-from maksim.yevmenkin@gmail.com)
Received: by mproxy.gmail.com with SMTP id w29so968000cwb
        for <freebsd-net@freebsd.org>; Wed, 21 Jul 2004 23:38:22 -0700 (PDT)
Received: by 10.11.116.69 with SMTP id o69mr29514cwc;
        Wed, 21 Jul 2004 23:38:22 -0700 (PDT)
Message-ID: <bb4a86c7040721233847c46bdc@mail.gmail.com>
Date: Wed, 21 Jul 2004 23:38:22 -0700
From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com>
To: Anil Madhavapeddy <anil@recoil.org>
In-Reply-To: <40FEC892.9030801@cw.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <40FEC892.9030801@cw.com>
cc: freebsd-net@freebsd.org
Subject: Re: Set device BD_ADDR via ng_bluetooth
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2004 06:38:23 -0000

> This is a long shot, but is it possible to set a Bluetooth device's
> BD_ADDR to a custom value using ng_bluetooth?  I couldn't spot anything
> in the ng_btsocket(4) man page, or in the Bluez stack on Linux.

bluetooth spec v1.1 does not define a way to set device's bd_addr.

i guess it *might* be possible via vendor specific command. of course
you would need to know the vendor command opcode and the parameters
for the specific bluetooth chip. good luck finding them out. vendor
commands on some chips do not even return any events back, so it makes
it hard to just probe all possible opcodes to see what device does.

device's bd_addr is the only way to identify bluetooth device. you are
not supposed to change it. everything else is tied to the bd_add, i.e.
security etc. why do you want to change it anyway?

max