From owner-freebsd-bluetooth@FreeBSD.ORG Wed Feb 4 19:27:44 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 9234D1065670 for ; Wed, 4 Feb 2009 19:27:44 +0000 (UTC) (envelope-from mav@mavhome.dp.ua) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 0FBBE8FC1D for ; Wed, 4 Feb 2009 19:27:43 +0000 (UTC) (envelope-from mav@mavhome.dp.ua) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 233557231; Wed, 04 Feb 2009 21:27:43 +0200 Message-ID: <4989EC35.80502@mavhome.dp.ua> Date: Wed, 04 Feb 2009 21:27:49 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.19 (X11/20090118) MIME-Version: 1.0 To: Maksim Yevmenkin References: <1233365217.00068654.1233354838@10.7.7.3> <4988DCCC.80201@mavhome.dp.ua> <4988EBAC.3080202@mavhome.dp.ua> <4988F857.5080407@mavhome.dp.ua> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 19:27:44 -0000 Maksim Yevmenkin wrote: >> Does actually this binding really necessary? rfcomm somehow works without >> it. > > please see Iain's response :) i knew he would chime in :) thanks Iain! > > and, yes, i suspected that it would be something related to mac > addresses on virtual ethernet interface. i do not have a copy of spec > handy, but i recall something about setting mac address to be the same > as radio's bd_addr. dont remember if it was a requirement or more of a > guideline. > > in any case, i like Iain's suggestion to rewrite mac addresses on the > fly. i would have done it this way. also, i think, nap server should > just act as ethernet hub, i.e. forward everything everywhere. after > all, nap is supposed to be like local ethernet network :) Hmm. Working like an Ethernet hub also means that every single hub port (in our case every single point-to-point BT link) may transmit packets from different source MAC addresses, that can't be equal to BT adapter address. So or I don't understand your example, or something is wrong here. >>> btw, obtaining bdaddr is really easy. in 99.9% cases (where there is >>> only one bluetooth device connected to the system) 'hccontrol >>> read_bd_addr' will do the trick :) >> Indeed. But general number of BT tools, daemons and their options just >> making me sad. > > i'm not sure how to read that :) there is, like, less than 10 > bluetooth related daemons in total. each has, like, may be 10 options. > compare this to the number of options ls(1) has :) not sure what could > possibly make you sad here. if you feel that the documentation is not > adequate, please feel free to fix it :) 10 daemons is understood, as BT is not that simple and IP stack also have many different tools. But anyway having about 70 defined and undocumented arguments of hccontrol alone, one of which should be used for such basic thing as getting local btaddr, are not looking so funny for anybody who are not BT guru. May be writing of some man page with some BT basics to cross reference that basic tools could help. Or just better cross reference existing pages. -- Alexander Motin