From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 19 03:23:56 2007 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7021216A418 for ; Mon, 19 Nov 2007 03:23:56 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 00D8013C481 for ; Mon, 19 Nov 2007 03:23:55 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1284194nfb for ; Sun, 18 Nov 2007 19:23:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=lULz+/lBqJuIhVB9pEz8gGtkzPfqvqsdzQulfxUP0Ww=; b=nGtjY9oO6QKi5jw4gFWEpH6DMAiyKbUL4QQm6gZHtKAco2dlP+t9mgdzg7RR9RQPrzuKCFsU3e4jlc9/woth3xBFwiI3R6Vz/Q4ECoXP09SQQGeqzhixN8CePIMU77Zfoxa2xEK+fZ0a2T2m0mpVVZ9l3KmKJL4Hrj9HqrrSNNw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Yb4HcVW0S4YaiiYlRA6MuatJZwVI2/jMjJ6y7oaQqbjPBS761I4R2Zs4PJAddMLIfwt8feEByu7ajObgaJqztE//VmmCqhIQJtD92GJiejcR0Ad9iTq+FBVeJ3zmAv3ptj+w/9ZllMFg046OxWxnmKQij5QWIqXn9wjvJUGbKgA= Received: by 10.86.53.8 with SMTP id b8mr4591483fga.1195442634646; Sun, 18 Nov 2007 19:23:54 -0800 (PST) Received: by 10.86.83.12 with HTTP; Sun, 18 Nov 2007 19:23:54 -0800 (PST) Message-ID: Date: Sun, 18 Nov 2007 19:23:54 -0800 From: "Maksim Yevmenkin" To: "Marten Vijn" In-Reply-To: <1195423486.915.13.camel@workstation.martenvijn.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1195343297.995.5.camel@workstation.martenvijn.nl> <1195423486.915.13.camel@workstation.martenvijn.nl> Cc: freebsd-bluetooth@freebsd.org Subject: Re: ubt0 macaddress cloning X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2007 03:23:56 -0000 Hello, On Nov 18, 2007 2:04 PM, Marten Vijn wrote: > On Sat, 2007-11-17 at 18:10 -0800, Maksim Yevmenkin wrote: > > Marten, > > > > > Is there a way to change the macaddress of a ubt (ng_ubt) device? > > > > short answer is no. not with the standard hci interface. > > > > aye thanks, > > Actually I have more general a question, > > If I am rolling out a grid of embedded systems with bluetooth, > > Say 5 nodes, I would like to configure my client device (GSM) only once > to have a pairing with will be valid for all nodes. it depends. basically the result of pairing is a link key. as long as the link key is the same on both ends, the connection can be established. now, lets say your gsm device has bd_addr_gsm and your embedded systems have bd_addr_embed1...n. assuming you have a total control over bluetooth stack on your embedded nodes, you can assign the same link key for bd_addr_gsm on each embedded node. assuming you are running freebsd on your embedded nodes, all you need to do it to make sure all the embedded nodes have the same /etc/bluetooth/hcsecd.conf file which assigns the same link key to bd_addr_gsm. the trick part is the gsm device. the problem here is that you have to make sure that gsm device is using the same link key when it tries to talk to your embedded nodes. if your gsm device is a phone, then you need to somehow program the same link key into the phone's database for bd_addr_embed1..n. another alternative is to program link keys into bluetooth device themselves, however this assumes that you have complete control over bluetooth devices on both ends and amount of nodes in your embedded network is less than amount of keys bluetooth device can store in its internal memory. > Would there be a way to share this pairing for al nodes? Assuming there > way to distribution method between the nodes? like i said, you can share link keys, but you need to control both ends of connection to pre-share link keys. thanks, max > > Marten > > > > > > > >