From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 10 23:28:36 2014 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4444C7B for ; Mon, 10 Nov 2014 23:28:36 +0000 (UTC) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 64B3CC77 for ; Mon, 10 Nov 2014 23:28:36 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id b13so10111218wgh.25 for ; Mon, 10 Nov 2014 15:28:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zbq0qX6fRZwJv4mBQFXPOPmEG9x9TkwRE/k0GBtohxs=; b=OLfhh5Gw8+4PN1OWPTQeoti/N1bxoxhGtUtONs/AwKCYG3lz6BWTHbqOh13Go2nPJ5 gJ70rbfxU5+7w8uwQz+WnScv7W2caKB+WFhAXSrO2bm2f51dIUBmHthmsm1gjdjp/8j8 HXmQ1UxWEA7xNUD/2SC3kUhtaTRwx1q12WeCL28QcZbjC5ow/eknES4wKZNxq1K5i0ZW nEmUC6jZZJH6CPuMvo7DKmrga6Ufw6OXuL1O6kfybjvPOgtdsglUHoKnBo4CpuzTalxR sEEgZp1qzPZvF+DDkD0GcBmnWHM5KxBKZGSx77sLjc8gUWoETNqEn7cs/OXBTAKQVg4N +KhA== MIME-Version: 1.0 X-Received: by 10.180.101.102 with SMTP id ff6mr35642428wib.0.1415662114739; Mon, 10 Nov 2014 15:28:34 -0800 (PST) Received: by 10.27.170.2 with HTTP; Mon, 10 Nov 2014 15:28:34 -0800 (PST) In-Reply-To: References: Date: Mon, 10 Nov 2014 15:28:34 -0800 Message-ID: Subject: Re: Logitech K810 Bluetooth keyboard From: Maksim Yevmenkin To: Iain Hibbert Content-Type: text/plain; charset=UTF-8 Cc: george ember , "freebsd-bluetooth@freebsd.org" X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2014 23:28:37 -0000 On Mon, Nov 10, 2014 at 1:20 PM, Iain Hibbert wrote: > On Fri, 7 Nov 2014, george ember wrote: > >> After reboot my hcibump -x >> >> ember@FreeBSD ~ $ sudo hcidump -x >> Password: >> HCIDump - HCI packet analyzer ver 1.5 >> device: any snap_len: 65535 filter: 0xffffffffffffffff >> > HCI Event: Connect Request(0x04) plen 10 >> C5 F2 4D 20 1F 00 40 05 00 01 >> < HCI Command: Accept Connection Request(0x01|0x0009) plen 7 >> C5 F2 4D 20 1F 00 00 >> > HCI Event: Command Status(0x0f) plen 4 >> 00 01 09 04 >> > HCI Event: Role Change(0x12) plen 8 >> 00 C5 F2 4D 20 1F 00 00 >> > HCI Event: Connect Complete(0x03) plen 11 >> 00 0B 00 C5 F2 4D 20 1F 00 01 00 >> < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 >> 0B 00 05 00 >> > HCI Event: Command Complete(0x0e) plen 6 >> 01 0D 08 00 0B 00 >> > HCI Event: Link Key Request(0x17) plen 6 >> C5 F2 4D 20 1F 00 >> < HCI Command: Link Key Request Negative Reply(0x01|0x000c) plen 6 >> C5 F2 4D 20 1F 00 >> > HCI Event: Command Complete(0x0e) plen 10 >> 01 0C 04 00 C5 F2 4D 20 1F 00 >> > HCI Event: Disconn Complete(0x05) plen 4 >> 00 0B 00 13 > > This seems consistent with the fact that you put "nokey" in the config > file.. the FreeBSD host states that it does not have a key but presumably > the keyboard is expecting one (if it has one stored for this host), so the > connection is refused, with the reason given "Remote User Terminated > Connection" (0x13 at the end) yes :) so, i _think_ the keyboard is expecting link key because it was paired with this particular host device before. since the keyboard is initiating request, then, it makes me think that the keyboard is _not_ in the pairing mode. the questions is: why is the keyboard expecting the key, and, why is it not getting it. i vaguely recall (from the previous conversation) that the same two devices, i.e. host device and the keyboard were paired under another OS, i.e. windows. obviously, generated link key is _not_ available to other OS, i.e. freebsd. thus the keyboard must be re-paired under freebsd. now, if you boot into windows again, link keys would not match and re-pair would be needed again. i've asked the question about dual booting, and, it it does not seem to be the case. so, was the keyboard re-paired? or same pair of devices used with another OS? last time i suggested to pair devices under freebsd. obtain link key from bthid.keys file and program it directly into the host device. this way, device will use it and re-pair would not be needed. another suggestion is to use different dongle with different OS. this was link keys would not clash. > can you show a hcidump of the pairing process, when a PIN is given? also, > after the keyboard is paired and the key is known (if you can get that > far) what about the dump that time? yes, so basically, i think, all is needed is to re-pair keyboard under freebsd. and then make sure to never re-pair it with the same devices on another OS. then it will "just work" thanks max