From owner-freebsd-bluetooth@FreeBSD.ORG Mon Sep 9 20:50:20 2013 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 15EB3187 for ; Mon, 9 Sep 2013 20:50:20 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 00CA62381 for ; Mon, 9 Sep 2013 20:50:19 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id r89KoCEq087720; Mon, 9 Sep 2013 13:50:13 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <522E3484.1070705@rawbw.com> Date: Mon, 09 Sep 2013 13:50:12 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130822 Thunderbird/17.0.8 MIME-Version: 1.0 To: Maksim Yevmenkin Subject: Re: Can ubt0 be a slave or a passive listener, and not a master? References: <522DEFD9.1030608@rawbw.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-bluetooth@freebsd.org" X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Sep 2013 20:50:20 -0000 On 09/09/2013 10:59, Maksim Yevmenkin wrote: > the lowest communication interface between host and device is HCI. > there are HCI commands, HCI responses and HCI events. as far as > discovery (inquiry) goes, one device initiates discovery (inquiry) in > response to HCI command received from its host. the device responds > (back to its host) with zero or more HCI events with information about > other devices in RF proximity, followed by HCI response to indicate > completion of discovery (inquiry). near by devices that are being > discovered do not send anything back to their hosts. > > i hope that helps So what you are saying is that there is no link-level sniffing using this kind of configuration. And the only thing I can see with hcidump are HCI commands coming back and forth between the host (BSD in this case) and device (dongle). Nothing like "promiscuous" mode for network interfaces. In other words, dongle does processing and only shows higher level information and not the link level packets. My original motivation for this is that I have a camera GPS device (master) and Android App that is supposed to work as a slave. But this link doesn't work at all for some reason. I was hoping to use BSD to troubleshoot. But it looks like this wasn't a realistic expectation. Thank you for this information, Yuri