From nobody Sun Aug 20 21:01:36 2023 X-Original-To: bluetooth@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RTShd0RNWz4qjdg for ; Sun, 20 Aug 2023 21:01:37 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RTShc59QVz3dPQ for ; Sun, 20 Aug 2023 21:01:36 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1692565296; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=hZTdOFTATxQeKoV4jljGFt/nUDOsnqVNS+LY5yHecYo=; b=IWkiv8s12GJlC8Pfz+TPswcSs4cTW/+r2RMQqVLqeUNDtk2Me52vo9G7ozJLUSHpf15ffR 9v6XyXK5cj0JLaU+GPZNOd8vXmmgrfxwJoQrRiLfvOWcgR42jiO9+n3CCNrYshwGJVJmza WyJye4yoznvKJCjFVbOvyiOuk+KqqqRG9s6DIT+3nFeKYFHZes8rE/WfMu5DdbxiU2o2wp XYO81TvcG11RoBKO7Zfb4zzYz2V+cNs6TRhOeF1EbDkddGXMlngEDifeu5eo+aAehu+gI0 5BuN7znCSobt284dZP8WpTfJcnHoDb0ncFnoUcGDWVk87H0h/V2Zay2xy5l8QQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1692565296; a=rsa-sha256; cv=none; b=N4CFviVszHx7n1O4QnQo6K34S11sr2gsaPxFsc5nCiuP7XNjStC+04IGPBivFSvG7zA4ws /Cc5blsGVTsC5ZhnIhwWVlyQrKhi6Yipx6DrTXi0zb/YOS6zhHS1pLmA+wOd89f9gzVNSp 6xCFgFsSQ53PLLWFps4/oaSHVClMM7hPsvUBFdw+7xv+NL/XdZXunBlVhVdHhYpq6zxad8 fnfre2kQC8CdquNHIxYa76PfwW1/W58hwjGOzZlPEMzOquiTATl/jFy5ul7nBcqXx1ALT4 wxFfwjzUdArntyzMUdBEL9ujxMxt0ZVj+RzaiNOGNR9d2EgCnum5HRxINa/H4g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4RTShc4Gy5ztZ2 for ; Sun, 20 Aug 2023 21:01:36 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 37KL1aST000959 for ; Sun, 20 Aug 2023 21:01:36 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 37KL1aBM000958 for bluetooth@FreeBSD.org; Sun, 20 Aug 2023 21:01:36 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202308202101.37KL1aBM000958@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: bluetooth@FreeBSD.org Subject: Problem reports for bluetooth@FreeBSD.org that need special attention Date: Sun, 20 Aug 2023 21:01:36 +0000 List-Id: Using Bluetooth in FreeBSD environments List-Archive: https://lists.freebsd.org/archives/freebsd-bluetooth List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bluetooth@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="16925652965.Ee1Bfec8.96121" Content-Transfer-Encoding: 7bit --16925652965.Ee1Bfec8.96121 Date: Sun, 20 Aug 2023 21:01:36 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 265066 | ng_hci: Add support for Bluetooth secure simple p 1 problems total for which you should take action. --16925652965.Ee1Bfec8.96121 Date: Sun, 20 Aug 2023 21:01:36 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" 
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status      |    Bug Id | Description
------------+-----------+---------------------------------------------------
Open        |    265066 | ng_hci: Add support for Bluetooth secure simple p

1 problems total for which you should take action.
--16925652965.Ee1Bfec8.96121-- From nobody Mon Aug 21 17:22:40 2023 X-Original-To: freebsd-bluetooth@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RTznv0khbz4r4RJ for ; Mon, 21 Aug 2023 17:22:59 +0000 (UTC) (envelope-from dmitry.medvedev@gmail.com) Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RTznt1g8Jz3VjF for ; Mon, 21 Aug 2023 17:22:58 +0000 (UTC) (envelope-from dmitry.medvedev@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=Z2cTiydY; spf=pass (mx1.freebsd.org: domain of dmitry.medvedev@gmail.com designates 2607:f8b0:4864:20::533 as permitted sender) smtp.mailfrom=dmitry.medvedev@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pg1-x533.google.com with SMTP id 41be03b00d2f7-56a9c951aaaso781675a12.3 for ; Mon, 21 Aug 2023 10:22:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692638576; x=1693243376; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=jScrigqQJjv2/EOvO9U3bIHv9q+WuCn54fPG1Nv9AWU=; b=Z2cTiydYY/lQMUO+05CDy6hg1zlr8liLd8nG3/Ed+EbI23THWt0OH+J24ep86xiXb/ hrtyM5Nm9kvwALE/zhQ+xnSwoDFD6TXaddtu3NCZNIi0x1xIVxPa9t6V9zWic4BfvjbP QcyhvBoGEByYoUQw2JIGxpVXontt2UmpojKKSL9dlKK/5jFZRQ8tZOvAwo/T/INVOtjr jlUdXMv+gF8mQ/LDfEIbud4sC2df6hbcvutqdnIwzNS8h6n0DzoF+fZSdplqujbXtfwQ lQJTkEJYqm/7xNP4Hs8u3G5tayimEA4I2mvHNSv1AvfdoJ9Nqx25OcwKOl5/iIysTa15 yqVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692638576; x=1693243376; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=jScrigqQJjv2/EOvO9U3bIHv9q+WuCn54fPG1Nv9AWU=; b=cYU9tpttlMmTaSXS+I7K7Ei6/s6JCtMbeu6WyKNK2jiMOOtkDqULamkgOOqedtbn2p KGwIE61lP0rfRWL8qIa9ptBAo0eODVvNEIALL9PHoOSlOgDiWqmIBC7cyxSzA3ULq5C1 2TQYjA/3X33W9s9LsbKo6ECipoQrIvuBPLhtIowX9yj1opLmetQ9j3IYts/+E/0VRaOz nn3kaCL/mFOImQ297aGB6BXxPAozbc0rjkZfxe6ijs2Iq8ZXiEMFKDQCkWFMRZoJV2eg LfDpal/qBVNFwlB78he9FhCI87VAuM/pdifGBnK4ZPSRYjevW0YySom7d7EJFPWQuq7R U1tw== X-Gm-Message-State: AOJu0YzhwsWMs9ZWL9nz7U9wTQGWtEqk6UvuEAgT9JrSaIDSktCL37uE ed6yUlDmY6dzbC83q+82s24x2dltutVwJ6L5ychCHThadQg= X-Google-Smtp-Source: AGHT+IGOznGCCMi6srA0n75IYwEjcqHV/g8FlLdgAGcA4OV516CZK7vbWKgNqZLSuBZDpVvieafGrhRWDUt03dBP264= X-Received: by 2002:a17:90b:30c6:b0:268:352c:9d13 with SMTP id hi6-20020a17090b30c600b00268352c9d13mr4163129pjb.0.1692638576332; Mon, 21 Aug 2023 10:22:56 -0700 (PDT) List-Id: Using Bluetooth in FreeBSD environments List-Archive: https://lists.freebsd.org/archives/freebsd-bluetooth List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bluetooth@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: "Dmitry N. Medvedev" Date: Mon, 21 Aug 2023 19:22:40 +0200 Message-ID: Subject: Re: FreeBSD won't see a specific bluetooth device To: freebsd-bluetooth@freebsd.org Content-Type: multipart/alternative; boundary="0000000000001354670603722154" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-bluetooth@freebsd.org]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::533:from]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; TAGGED_FROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MLMMJ_DEST(0.00)[freebsd-bluetooth@freebsd.org] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4RTznt1g8Jz3VjF --0000000000001354670603722154 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable not resolved yet, but this is what a Kinesis employee said: the Advantage 360 Pro uses BLE. I have used the hccontrol to do le_ scan and I can clearly see the keyboard in the list, but I have no idea on how to make it connect to my freeBSD host. any help would be appreciated! best regards, Dmitry On Wed, Aug 16, 2023 at 2:24=E2=80=AFPM Dmitry N. Medvedev < dmitry.medvedev@gmail.com> wrote: > good morning! > > *the context*: > 1. there is an HP Z420 desktop with FreeBSD 13.2-RELEASE-p2 > 2. there is a dell laptop with windows > 3. there is a macbook pro > 4. there is a bluetooth apple keyboard > 5. there is an Advantage 360 Pro bluetooth keyboard > > *the problem*: > using the *hccontrol -n ubt0hci inquiry* command I can list all the > bluetooth devices, but the Advantage 360 Pro. > > This I cannot understand. How can the said keyboard avoid being listed? > > I am struggling to pair the Advantage 360 Pro to my FreeBSD desktop. > > Literally any help/ideas/thoughts are welcome! > > With kind regards, > Dmitry N. Medvedev > > Tel.: > +49 176 65213116 > --0000000000001354670603722154 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
not resolved=C2=A0yet, but this is what a Kinesis employee= said: the Advantage 360 Pro uses BLE.

I have used the h= ccontrol to do le_ scan and I can clearly see the keyboard in the list,
but I have no idea on how to make it connect to my freeBSD host.

any help would be appreciated!

best regards,
Dmitry


=
On Wed= , Aug 16, 2023 at 2:24=E2=80=AFPM Dmitry N. Medvedev <dmitry.medvedev@gmail.com> wrote:
g= ood morning!

the context:
1. ther= e is an HP Z420 desktop with FreeBSD 13.2-RELEASE-p2
2. there is = a dell laptop with windows
3. there is a macbook pro
4.= there is a bluetooth apple keyboard
5. there is an Advantage 360= Pro bluetooth keyboard

the problem:
<= div>using the hccontrol=C2=A0-n ubt0hci inquiry command I can list a= ll the bluetooth devices, but the Advantage 360 Pro.

This I cannot understand. How can the said keyboard avoid being listed?<= /div>

I am struggling to pair the Advantage 360 Pro to m= y FreeBSD desktop.

Literally any help/ideas/though= ts are welcome!

With kind regards,
Dmitry N. Medvedev

Tel.:
=C2=A0+49 176 65213116
--0000000000001354670603722154-- From nobody Mon Aug 21 17:55:00 2023 X-Original-To: freebsd-bluetooth@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RV0W60LDNz4r6y6 for ; Mon, 21 Aug 2023 17:55:14 +0000 (UTC) (envelope-from marc@bumblingdork.com) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RV0W50gztz4Cx5 for ; Mon, 21 Aug 2023 17:55:13 +0000 (UTC) (envelope-from marc@bumblingdork.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bumblingdork.com header.s=google header.b=dpsiYP+4; spf=pass (mx1.freebsd.org: domain of marc@bumblingdork.com designates 2a00:1450:4864:20::52b as permitted sender) smtp.mailfrom=marc@bumblingdork.com; dmarc=pass (policy=none) header.from=bumblingdork.com Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-5231410ab27so4602582a12.0 for ; Mon, 21 Aug 2023 10:55:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bumblingdork.com; s=google; t=1692640511; x=1693245311; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=e8JKd2b4SC4yxdNCQ8z8fdjULo5UBjRMyEGYYw5KwsU=; b=dpsiYP+4pl6RagyHNxSyOn5qh4oVSdQRvR5rduDW/9D9d+WKgcEvKbQRRWisC2fQYm g6exsk80G5OBiYpjuUigA2ehl+eBUgaJfkdoCPGmJx7v8hLI96iCPMzZXNOssqX36Q1y M4OInCk2qiHnKwxtgsueQNMCOHnxZ+0G1NDfqspwN2K0HLqSdKyeQXsGAjeVUMCdjMke s5dN26dzYSrb8zVVmmVo1BroQ8y4SaDayR6CMp6mbPFOyBlmJsUv/sGZvszam7PtO6n8 falm22T0YnDGgPjDisW4/5au0/JrCajA1pL4d9yNNXbhUGSEbiwrS3tkeNhPndrKCgrm BGuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692640511; x=1693245311; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=e8JKd2b4SC4yxdNCQ8z8fdjULo5UBjRMyEGYYw5KwsU=; b=klN4Mdhp8ON1BQ9aBnuYQqDO2IlRbcBF1pKMpTvR/1zr+BO93klW4RyeKRWqyZH9OK WY5vyVjWZXYqWKQcYcVbW3Chy10Prk0W+dOM68lWgxwXDVNsEE3brh1JVZ3qNRTkdOok OAXSwUJ1NBnF+bQyPdL3wKp/D2MPkiEH5ISa2iSr5efOXGYpwOU+YkaSc/80TYu/1zo0 gJaWvTcYmDZC4psscthJRaeNLu8c/OI+sogKrO+gKhG0oieSOMq44IzjNnQ86Btmweqz qw9lNUXeLFfBOffnPHgjFLa3fMm9/8GiVmdPx118BT+IUw2W3S5mgwtpyqnC/bIVI1bU wo2g== X-Gm-Message-State: AOJu0YyfkbmPpVAfBfxwaf/YsDE8iCeEY2SrJ4nX9Y+5bBY4WomUE857 mkw+bp6WeYdX22Gs0A/IUu3Bmw== X-Google-Smtp-Source: AGHT+IENENVDag9Ks4zRnAtKfncbtEIWWeNyupKNnZAwErlODRh7wOLfG3IT6lpZEGNWpuvfOPvtaA== X-Received: by 2002:a17:906:4d2:b0:988:8be0:3077 with SMTP id g18-20020a17090604d200b009888be03077mr5532559eja.31.1692640511282; Mon, 21 Aug 2023 10:55:11 -0700 (PDT) Received: from smtpclient.apple (2a02-a467-ec-1-dc8d-84b4-7757-8146.fixed6.kpn.net. [2a02:a467:ec:1:dc8d:84b4:7757:8146]) by smtp.gmail.com with ESMTPSA id u18-20020a170906125200b009920a690cd9sm6789486eja.59.2023.08.21.10.55.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Aug 2023 10:55:11 -0700 (PDT) Content-Type: text/plain; charset=utf-8 List-Id: Using Bluetooth in FreeBSD environments List-Archive: https://lists.freebsd.org/archives/freebsd-bluetooth List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bluetooth@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: FreeBSD won't see a specific bluetooth device From: Marc Veldman In-Reply-To: Date: Mon, 21 Aug 2023 19:55:00 +0200 Cc: freebsd-bluetooth@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0A093E3B-4F8F-4EB1-A1FD-461BF8293EAC@bumblingdork.com> References: To: "Dmitry N. Medvedev" X-Mailer: Apple Mail (2.3731.600.7) X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[bumblingdork.com,none]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[bumblingdork.com:s=google]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[marc]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52b:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-bluetooth@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TAGGED_RCPT(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-bluetooth@freebsd.org]; RCPT_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[bumblingdork.com:+]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4RV0W50gztz4Cx5 Hello Dmitry, I don=E2=80=99t think there is support for BLE keyboards in FreeBSD. Best regards, Marc Veldman > On 21 Aug 2023, at 19:22, Dmitry N. Medvedev = wrote: >=20 > not resolved yet, but this is what a Kinesis employee said: the = Advantage 360 Pro uses BLE. >=20 > I have used the hccontrol to do le_ scan and I can clearly see the = keyboard in the list, > but I have no idea on how to make it connect to my freeBSD host. >=20 > any help would be appreciated! >=20 > best regards, > Dmitry >=20 >=20 >=20 > On Wed, Aug 16, 2023 at 2:24=E2=80=AFPM Dmitry N. Medvedev = wrote: > good morning! >=20 > the context: > 1. there is an HP Z420 desktop with FreeBSD 13.2-RELEASE-p2 > 2. there is a dell laptop with windows > 3. there is a macbook pro > 4. there is a bluetooth apple keyboard > 5. there is an Advantage 360 Pro bluetooth keyboard >=20 > the problem: > using the hccontrol -n ubt0hci inquiry command I can list all the = bluetooth devices, but the Advantage 360 Pro. >=20 > This I cannot understand. How can the said keyboard avoid being = listed? >=20 > I am struggling to pair the Advantage 360 Pro to my FreeBSD desktop. >=20 > Literally any help/ideas/thoughts are welcome! >=20 > With kind regards, > Dmitry N. Medvedev >=20 > Tel.: > +49 176 65213116 From nobody Tue Aug 22 03:35:41 2023 X-Original-To: freebsd-bluetooth@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RVFP70Yxxz4Yt6m for ; Tue, 22 Aug 2023 03:35:55 +0000 (UTC) (envelope-from takawata@akatsuki.init-main.com) Received: from ns.init-main.com (104.194.138.210.bn.2iij.net [210.138.194.104]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "akatsuki", Issuer "akatsuki" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RVFP4744kz3fny for ; Tue, 22 Aug 2023 03:35:52 +0000 (UTC) (envelope-from takawata@akatsuki.init-main.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of takawata@akatsuki.init-main.com has no SPF policy when checking 210.138.194.104) smtp.mailfrom=takawata@akatsuki.init-main.com; dmarc=none Received: from akatsuki.init-main.com (localhost [127.0.0.1]) by ns.init-main.com (8.17.1/8.17.1) with ESMTPS id 37M3Zf7Q067147 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Tue, 22 Aug 2023 12:35:41 +0900 (JST) (envelope-from takawata@akatsuki.init-main.com) Received: (from takawata@localhost) by akatsuki.init-main.com (8.17.1/8.16.1/Submit) id 37M3ZfhY067146 for freebsd-bluetooth@freebsd.org; Tue, 22 Aug 2023 12:35:41 +0900 (JST) (envelope-from takawata) Date: Tue, 22 Aug 2023 12:35:41 +0900 From: Takanori Watanabe To: freebsd-bluetooth@freebsd.org Subject: Re: FreeBSD won't see a specific bluetooth device Message-ID: References: <0A093E3B-4F8F-4EB1-A1FD-461BF8293EAC@bumblingdork.com> List-Id: Using Bluetooth in FreeBSD environments List-Archive: https://lists.freebsd.org/archives/freebsd-bluetooth List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bluetooth@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0A093E3B-4F8F-4EB1-A1FD-461BF8293EAC@bumblingdork.com> X-Spamd-Result: default: False [-1.80 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_LONG(-1.00)[-0.998]; FORGED_SENDER(0.30)[takawata@init-main.com,takawata@akatsuki.init-main.com]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[init-main.com]; ASN(0.00)[asn:2497, ipnet:210.138.0.0/16, country:JP]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-bluetooth@freebsd.org]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[takawata]; ARC_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[takawata@init-main.com,takawata@akatsuki.init-main.com]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-bluetooth@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Spamd-Bar: - X-Rspamd-Queue-Id: 4RVFP4744kz3fny On Mon, Aug 21, 2023 at 07:22:40PM +0200, Dmitry N. Medvedev wrote: > not resolved yet, but this is what a Kinesis employee said: the Advantage > 360 Pro uses BLE. > > I have used the hccontrol to do le_ scan and I can clearly see the keyboard > in the list, > but I have no idea on how to make it connect to my freeBSD host. > > any help would be appreciated! > I have a tool for userland and work with Bluetooth LE mouse based on bthidd, but keyboard support is disabled. https://github.com/takawata/FreeBSD-BLE To recognize LE device. 1. scan LE device and think 2. invoke ./lepair ${BTHADDR} (-r option required if address is random address) 3. add hcsecd.conf in lesecd directory by copy-n-paste from lepair output. 4. ./lesecd 3. in lehid directory, lehid -s ${BTADDR} Then keyboard may be recoginzed, but will not do useful thing. > On Wed, Aug 16, 2023 at 2:24 PM Dmitry N. Medvedev < > dmitry.medvedev@gmail.com> wrote: > > > good morning! > > > > *the context*: > > 1. there is an HP Z420 desktop with FreeBSD 13.2-RELEASE-p2 > > 2. there is a dell laptop with windows > > 3. there is a macbook pro > > 4. there is a bluetooth apple keyboard > > 5. there is an Advantage 360 Pro bluetooth keyboard > > > > *the problem*: > > using the *hccontrol -n ubt0hci inquiry* command I can list all the > > bluetooth devices, but the Advantage 360 Pro. > > > > This I cannot understand. How can the said keyboard avoid being listed? > > > > I am struggling to pair the Advantage 360 Pro to my FreeBSD desktop. > > > > Literally any help/ideas/thoughts are welcome! > > > > With kind regards, > > Dmitry N. Medvedev > > > > Tel.: > > +49 176 65213116 > > From nobody Tue Aug 22 06:49:34 2023 X-Original-To: freebsd-bluetooth@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RVKhv6Z2nz4qSNQ for ; Tue, 22 Aug 2023 06:49:51 +0000 (UTC) (envelope-from dmitry.medvedev@gmail.com) Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RVKhv5tp8z4cmK for ; Tue, 22 Aug 2023 06:49:51 +0000 (UTC) (envelope-from dmitry.medvedev@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1031.google.com with SMTP id 98e67ed59e1d1-26f4bc74131so1359143a91.1 for ; Mon, 21 Aug 2023 23:49:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692686991; x=1693291791; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tZnVi6sjKl0d8TVrGjgX2FVsSbwWQ07aHJAjKErt708=; b=o7hW2b62h7HOg7NIGE0URYHEmL5ZUwLFWty2ZhVJkvPjEDev+YKeMkY9HFywEMwqs+ WYGd2iA4ZB/pHs5STsiEEHIH/TEy+6Kbv1wcDVV+m/z+xVoC9vA8DCtfeFsr4qZ3lLj5 1CppObH2w7s+ECmc2lRrZ3wwewFI1ICw+rm6HkiVhLqXBBfmkBKkmnaswq5lPbioM7Xd ICgqZMnQIecoBnE+Gp4/biwePsO3DG45i5i9fx3F9mzOwoJxSS6ZK2/jx8crOHSJHmdA wvy+WDoskzmYlQtFax0rPivFEQ89+FhLw3hYHuEH77uBx9IrAJNHLxupyLd3Jk16JO45 mxMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692686991; x=1693291791; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tZnVi6sjKl0d8TVrGjgX2FVsSbwWQ07aHJAjKErt708=; b=GFMjwpElRoIewI6rVTHK3eOlPKfiXlNobwbRvqXCr4ZYg2yqS5la73LE5YksEBOhuU o94lAhBiA3YZNffaz15QGuGLs+WisD7fYRv+MWyd1AL1yH/VrosSe8+xJgX7fwhMgrH0 jlIEgSywBESKLqMJpH6hfOZsgXdUbI1bEc7f/pspek3RQlbqWnfSFxGcCeQPJZw76ghv 9inA6XxRFXncWwPuV/3Vm7BYcGQW+fn0l8A8FLzqtHwm6sce2gCwg0a+ZPYkaolmRUvC lAm5BYAJSFmGqD+aJz5iFtPbT5O4YSIq6Tzd7oUN5FwEwh5YfLI8oaxQsLFVUTCrTYia 6OQw== X-Gm-Message-State: AOJu0Yz6DzTuXkvlYJcB6h5x+jWzFySz5niDRil9RuA3hXfcETo4Y3Ab l8QYJIZ15icjplKYWgfGQ9t6N9PCthSSOimlXjrLMmn6Ky0= X-Google-Smtp-Source: AGHT+IH6qQBl0XwLOWnrbfnNEjAfCKsJvcDjRIE70x8Z0bOHrCalW2mOnij9/rltIu0oLi82RbtmP+GrYq03mGcJvtk= X-Received: by 2002:a17:90b:1986:b0:268:798:a28b with SMTP id mv6-20020a17090b198600b002680798a28bmr12911309pjb.23.1692686990500; Mon, 21 Aug 2023 23:49:50 -0700 (PDT) List-Id: Using Bluetooth in FreeBSD environments List-Archive: https://lists.freebsd.org/archives/freebsd-bluetooth List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bluetooth@freebsd.org MIME-Version: 1.0 References: <0A093E3B-4F8F-4EB1-A1FD-461BF8293EAC@bumblingdork.com> In-Reply-To: From: "Dmitry N. Medvedev" Date: Tue, 22 Aug 2023 08:49:34 +0200 Message-ID: Subject: Re: FreeBSD won't see a specific bluetooth device To: Takanori Watanabe Cc: freebsd-bluetooth@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c8e8b106037d66ec" X-Rspamd-Queue-Id: 4RVKhv5tp8z4cmK X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[] --000000000000c8e8b106037d66ec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable hi, thank you for your reply! I have tried your FreeBSD-BLE already :) The question is: do you have plans to support keyboards? best regards, Dmitry On Tue, Aug 22, 2023 at 5:35=E2=80=AFAM Takanori Watanabe wrote: > > On Mon, Aug 21, 2023 at 07:22:40PM +0200, Dmitry N. Medvedev wrote: > > not resolved yet, but this is what a Kinesis employee said: the Advanta= ge > > 360 Pro uses BLE. > > > > I have used the hccontrol to do le_ scan and I can clearly see the > keyboard > > in the list, > > but I have no idea on how to make it connect to my freeBSD host. > > > > any help would be appreciated! > > > > I have a tool for userland and work with Bluetooth LE mouse based on > bthidd, > but keyboard support is disabled. > > https://github.com/takawata/FreeBSD-BLE > > To recognize LE device. > 1. scan LE device and think > 2. invoke ./lepair ${BTHADDR} (-r option required if address is random > address) > 3. add hcsecd.conf in lesecd directory by copy-n-paste from lepair output= . > 4. ./lesecd > 3. in lehid directory, lehid -s ${BTADDR} > > Then keyboard may be recoginzed, but will not do useful thing. > > > > > On Wed, Aug 16, 2023 at 2:24=E2=80=AFPM Dmitry N. Medvedev < > > dmitry.medvedev@gmail.com> wrote: > > > > > good morning! > > > > > > *the context*: > > > 1. there is an HP Z420 desktop with FreeBSD 13.2-RELEASE-p2 > > > 2. there is a dell laptop with windows > > > 3. there is a macbook pro > > > 4. there is a bluetooth apple keyboard > > > 5. there is an Advantage 360 Pro bluetooth keyboard > > > > > > *the problem*: > > > using the *hccontrol -n ubt0hci inquiry* command I can list all the > > > bluetooth devices, but the Advantage 360 Pro. > > > > > > This I cannot understand. How can the said keyboard avoid being liste= d? > > > > > > I am struggling to pair the Advantage 360 Pro to my FreeBSD desktop. > > > > > > Literally any help/ideas/thoughts are welcome! > > > > > > With kind regards, > > > Dmitry N. Medvedev > > > > > > Tel.: > > > +49 176 65213116 > > > > > > --000000000000c8e8b106037d66ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
hi,
thank you for your=C2=A0reply!

I have tried your FreeBSD-BLE already :)

The= question is: do you have plans to support keyboards?

<= div>best regards,
Dmitry

On Tue, Aug 22, 2023 at 5:35=E2=80= =AFAM Takanori Watanabe <takaw= ata@init-main.com> wrote:

On Mon, Aug 21, 2023 at 07:22:40PM +0200, Dmitry N. Medvedev wrote:
> not resolved yet, but this is what a Kinesis employee said: the Advant= age
> 360 Pro uses BLE.
>
> I have used the hccontrol to do le_ scan and I can clearly see the key= board
> in the list,
> but I have no idea on how to make it connect to my freeBSD host.
>
> any help would be appreciated!
>

I have a tool for userland and work with Bluetooth LE mouse based on bthidd= ,
but keyboard support is disabled.

https://github.com/takawata/FreeBSD-BLE

To recognize LE device.
1. scan LE device and think
2. invoke ./lepair ${BTHADDR} (-r option required if address is random addr= ess)
3. add hcsecd.conf in lesecd directory by copy-n-paste from lepair output.<= br> 4. ./lesecd
3. in lehid directory, lehid -s ${BTADDR}

Then keyboard may be recoginzed, but will not do useful thing.



> On Wed, Aug 16, 2023 at 2:24=E2=80=AFPM Dmitry N. Medvedev <
> dmitry.= medvedev@gmail.com> wrote:
>
> > good morning!
> >
> > *the context*:
> > 1. there is an HP Z420 desktop with FreeBSD 13.2-RELEASE-p2
> > 2. there is a dell laptop with windows
> > 3. there is a macbook pro
> > 4. there is a bluetooth apple keyboard
> > 5. there is an Advantage 360 Pro bluetooth keyboard
> >
> > *the problem*:
> > using the *hccontrol -n ubt0hci inquiry* command I can list all t= he
> > bluetooth devices, but the Advantage 360 Pro.
> >
> > This I cannot understand. How can the said keyboard avoid being l= isted?
> >
> > I am struggling to pair the Advantage 360 Pro to my FreeBSD deskt= op.
> >
> > Literally any help/ideas/thoughts are welcome!
> >
> > With kind regards,
> > Dmitry N. Medvedev
> >
> > Tel.:
> >=C2=A0 +49 176 65213116
> >


--000000000000c8e8b106037d66ec-- From nobody Tue Aug 22 07:15:17 2023 X-Original-To: freebsd-bluetooth@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RVLGP1v7nz4qV1V for ; Tue, 22 Aug 2023 07:15:25 +0000 (UTC) (envelope-from takawata@akatsuki.init-main.com) Received: from ns.init-main.com (104.194.138.210.bn.2iij.net [210.138.194.104]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "akatsuki", Issuer "akatsuki" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RVLGL4cMJz4h6n for ; Tue, 22 Aug 2023 07:15:21 +0000 (UTC) (envelope-from takawata@akatsuki.init-main.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of takawata@akatsuki.init-main.com designates 210.138.194.104 as permitted sender) smtp.mailfrom=takawata@akatsuki.init-main.com; dmarc=none Received: from akatsuki.init-main.com (localhost [127.0.0.1]) by ns.init-main.com (8.17.1/8.17.1) with ESMTPS id 37M7FHR5067920 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 22 Aug 2023 16:15:17 +0900 (JST) (envelope-from takawata@akatsuki.init-main.com) Received: (from takawata@localhost) by akatsuki.init-main.com (8.17.1/8.16.1/Submit) id 37M7FHFB067919; Tue, 22 Aug 2023 16:15:17 +0900 (JST) (envelope-from takawata) Date: Tue, 22 Aug 2023 16:15:17 +0900 From: Takanori Watanabe To: "Dmitry N. Medvedev" Cc: freebsd-bluetooth@freebsd.org Subject: Re: FreeBSD won't see a specific bluetooth device Message-ID: References: <0A093E3B-4F8F-4EB1-A1FD-461BF8293EAC@bumblingdork.com> List-Id: Using Bluetooth in FreeBSD environments List-Archive: https://lists.freebsd.org/archives/freebsd-bluetooth List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bluetooth@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-2.45 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.45)[-0.447]; FORGED_SENDER(0.30)[takawata@init-main.com,takawata@akatsuki.init-main.com]; R_SPF_ALLOW(-0.20)[+ip4:210.138.194.104]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:2497, ipnet:210.138.0.0/16, country:JP]; MLMMJ_DEST(0.00)[freebsd-bluetooth@freebsd.org]; R_DKIM_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FREEFALL_USER(0.00)[takawata]; ARC_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[takawata@init-main.com,takawata@akatsuki.init-main.com]; FROM_HAS_DN(0.00)[]; TAGGED_RCPT(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[init-main.com]; RCVD_COUNT_TWO(0.00)[2] X-Spamd-Bar: -- X-Rspamd-Queue-Id: 4RVLGL4cMJz4h6n On Tue, Aug 22, 2023 at 08:49:34AM +0200, Dmitry N. Medvedev wrote: > hi, > thank you for your reply! > > I have tried your FreeBSD-BLE already :) > > The question is: do you have plans to support keyboards? > Then, do you connect the application and get some debug message? Like "Key value %d\n"