From owner-freebsd-bluetooth@FreeBSD.ORG Thu Feb 5 21:18:25 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 AD726106564A for ; Thu, 5 Feb 2009 21:18:25 +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 2836D8FC16 for ; Thu, 5 Feb 2009 21:18:24 +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 233698669; Thu, 05 Feb 2009 23:18:23 +0200 Message-ID: <498B57A5.6080406@mavhome.dp.ua> Date: Thu, 05 Feb 2009 23:18:29 +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> <4989F6E3.9020702@mavhome.dp.ua> <498A0DDF.1050605@mavhome.dp.ua> <498A1966.4030600@mavhome.dp.ua> <498A8912.9050208@mavhome.dp.ua> <498B3EA9.1030403@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: Thu, 05 Feb 2009 21:18:25 -0000 Maksim Yevmenkin wrote: >> I would like to say about that we can: >> 1) or, as you have just said, set completely fake TAP address and never >> compress it, as it is never equal, >> 2) or, as I have told recently, get real BDADDR of any adapter present in >> system (preferably related) and use it's address for TAP, then for traffic >> passing via that adapter compression could be used, saving 6 bytes. For >> usual systems with one adapter it will make that all locally >> originated/terminated traffic will have compressed src/dst address. > > its not even interesting anymore :) imo, there is very little reason > to set tap interface to any radio's bd_addr. it makes perfect sense > (to me) to keep whatever mac address assigned to tap by default > because that is the interface on which traffic is flowing. radio is > just a transport. > > it is still possible to compress dst address in bnep header, so, like > i said, the overhead is only 6 bytes. that is 6/1500 = 0.4% (!), and, > i bet you won't even be able to measure it. oh, and keep in mind that > bnep _replaces_ original ethernet header, so even if you don't do > _any_ compression at all, you are not doing worse. > > this is a very reasonable price to pay to support multiple radios and > listening on wildcard address without adding extra complexity to the > code. plus, like you said, it only can compress src on only one radio > link anyway, so the more radios you have, the less "win" you will get. Ok, as you wish, simplicity is good, but if it sometimes would be not difficult to implement 2, it still would be not bad. The only thing should be tested is WM compatibility. Iain was written that there is some problems he noticed if addresses differs. -- Alexander Motin