From owner-freebsd-bluetooth@FreeBSD.ORG Wed Feb 4 15:58:34 2009 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 AE29D106566B for ; Wed, 4 Feb 2009 15:58:34 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp02.one2one.net (smtp02.one2one.net [149.254.192.174]) by mx1.freebsd.org (Postfix) with ESMTP id 4ACBB8FC16 for ; Wed, 4 Feb 2009 15:58:34 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from [127.0.0.1] (helo=localhost) by localhost.localdomain with esmtp (Exim 4.50) id 1LUjpH-0007Na-Uh; Wed, 04 Feb 2009 15:38:08 +0000 Received: from localhost.t-mobile.co.uk ([127.0.0.1]) by localhost (smtpbeckt01 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28252-05; Wed, 4 Feb 2009 15:38:07 +0000 (GMT) Received: from [10.35.255.231] (helo=rya-online.net) by localhost.localdomain with smtp (Exim 4.50) id 1LUjpD-0007Ms-Tt; Wed, 04 Feb 2009 15:38:07 +0000 Received: (nullmailer pid 530 invoked by uid 1000); Wed, 04 Feb 2009 14:57:43 -0000 Date: Wed, 4 Feb 2009 14:57:43 +0000 (GMT) To: Alexander Motin In-Reply-To: <4988F857.5080407@mavhome.dp.ua> References: <1233365217.00068654.1233354838@10.7.7.3> <4988DCCC.80201@mavhome.dp.ua> <4988EBAC.3080202@mavhome.dp.ua> <4988F857.5080407@mavhome.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1233759463.493208.401.nullmailer@galant.ukfsn.org> From: Iain Hibbert X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at example.com X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: plunky@rya-online.net X-SA-Exim-Scanned: No (on localhost.localdomain); SAEximRunCond expanded to false Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: pan profile support in freebsd 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: Wed, 04 Feb 2009 15:58:35 -0000 On Wed, 4 Feb 2009, Alexander Motin wrote: [relating to -d device] > Does actually this binding really necessary? rfcomm somehow works without it. This binding is used (in original version) to set the tap interface address to be the same as the bdaddr. I did consider allowing to use it without setting that but then ethernet packets are being transmitted with a source address that is not the bdaddr. Now, IIRC it would seem that the spec allows this, but my windows mobile device (for instance) fails to route packets back to the computer. there are a couple of ways around this I could see 1. skip the bdaddr_any(local_bdaddr) check while validating the command line options, but add something to set it if it is unset. That would be the easiest option I guess but you need to be able to find the device with the best route to remote (could be first device, could be we already have a connection to remote device - I don't know what FreeBSD provides here?) 2. perform 'address rewriting' on ethernet packets. Actually this is not that difficult to do and I had it going during testing (when receiving packets, if the source address is the same as the remote bdaddr, or the ethernet tap address, set it to NULL. When sending, if the source is NULL, use the local bdaddr or ethernet tap address.) This also allows a single btpand instance to straddle multiple controllers but I thought it might be better to keep it simple in the beginning. the fact of it requiring the commandline argument at first I prefer - because its always possible to relax a requirement but not to tighten one up :) iain