From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jun 20 21:41:43 2005 Return-Path: X-Original-To: bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C60716A41F for ; Mon, 20 Jun 2005 21:41:43 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF79E43D53 for ; Mon, 20 Jun 2005 21:41:42 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 6D6A53C0B0; Mon, 20 Jun 2005 16:41:42 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01260-01-79; Mon, 20 Jun 2005 16:41:42 -0500 (CDT) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mailgate1b.savvis.net (Postfix) with ESMTP id 2FB473BF1A; Mon, 20 Jun 2005 16:41:42 -0500 (CDT) Received: from s228130hz1ew171.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 20 Jun 2005 16:41:28 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew171.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 20 Jun 2005 16:41:24 -0500 Message-ID: <42B73802.80509@savvis.net> Date: Mon, 20 Jun 2005 14:41:22 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Darren Pilgrim References: <001d01c575de$2c821800$0b2a15ac@SMILEY> In-Reply-To: <001d01c575de$2c821800$0b2a15ac@SMILEY> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Jun 2005 21:41:24.0697 (UTC) FILETIME=[CE773490:01C575E0] X-Virus-Scanned: amavisd-new at savvis.net Cc: vova@fbsd.ru, 'bluetooth' Subject: Re: Problem with Logitech Mx900 again 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, 20 Jun 2005 21:41:43 -0000 Darren, >>>It does not work in bot WinXP and FreeBSD (works for both >>>before), but it still works with native cradle. >> >>what do you mean with native cradle? is it some sort of wired >>interface? bluetooth usb receiver? or bluetooth usb receiver >>which os detects as usb mouse (i.e. bluetooth usb receiver with >>hid proxy feature activated)? > > He would be talking about the bluetooth receiver charging base that > comes with the MX900. It proxies Logitech bluetooth mice and keyboards > as usb devices. ah, ok. so it is bluetooth usb receiver with 'hid-proxy' feature activated. >>from what i can see, it looks like the mouse does not like new host. >>most hid devices will "lock" on the first device that contacted it. >>that is why you need to "reset" the mouse to make sure it "forgets" >>about previous host. > > I use my MX900 and Targus mice in both FreeBSD and Windows XP. > Rebooting back an forth doesn't break the connection to either. I would > guess that the MX900 is sensitive only to the hardware address, since > both OSes use my notebook's internal bluetooth receiver. that is what i said, didn't i :) ? let me re-phrase it. bluetooth hid devices "remembers" the bd_addr of the first remote bluetooth device that contacted it. the subsequent connections will only be accepted from (or initiated to) "known" host. > I have found, however, that something does get broken if use bthidd with > Windows XP hibernated. When I bring Windows XP back out of hibernation, > I have to have the machine search for devices to clear the stale > connection, then push the connect button on the mouse, search again and > manually reconnect the mouse. i think its fine. its probably because bluetooth receiver gets powered down and thus looses its state. the software however, does not reset its state and still thinks it has active connection. >>another thing you could try to do is to force paring between >>the mouse and pc. you need to know default pin-code for the mouse. >>check the manual to see if its there, if not - try "0000" - four >>zeros. > > The MX900 doesn't support pin-based pairing AFAIK. It "auto-pairs" by > remembering the last host to which it was connected and restores the > connection whenever the host shows up. actually, i'm pretty sure it does. here is the quote from the bluetooth hid spec 5.4 Link Level Requirements 5.4.1 Authentication, Pairing, Bonding Support for authentication, pairing, and bonding routines in hosts and applications of Bluetooth Human Interface Devices is optional, although authentication is strongly encouraged and encryption is recommended for host application programs requiring users to enter sensitive information on a Bluetooth keyboard or keypad. It is normally the responsibility of the host to initiate security procedures, however HIDs are optionally allowed to initiate authentication (after initial pairing, initiated by the host, has been completed) to prevent host spoofing. Hosts shall by default try the zero PIN code first (0x00, one byte) when requesting authentication to a HID. If the device has not been preprogrammed to a zero PIN, the authentication will fail, at which time the host can prompt the user for the non-zero device PIN code. thanks, max