Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4060061pxf; Tue, 6 Apr 2021 07:06:37 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxcrBkG3EIvYAXsonlg1ncpBfUwp3NM06eSjXsBeTjsS7UEo5x5vWNl50Eqt1cnbE627EeF X-Received: by 2002:a05:6e02:80a:: with SMTP id u10mr23986882ilm.221.1617717997236; Tue, 06 Apr 2021 07:06:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617717997; cv=none; d=google.com; s=arc-20160816; b=HB+DFNNzAwmC2W6YtI6XMOC/ceWBoOCHAfDNWz42prZTv8k3jJFp3Ai0ItygHvYrSJ BlP4MLNXNrImCWPj6BHPOqPG+0/4IXZDALg5bWgfjqWDlKCQh4yPTjs/jdJXlaD8AeER Z4Keyt+cMg5pQI2F9kYXAt1aaXg5B1vPIpo2te9uH4kk3fMiYgaSRpUPlmw4OQ1mU055 gYKEnGKT9kWhPAHijqMyznHOVALfhqvoqo4HzeG8jgTKnn+X0IvcSeYGuhPGhfFcdTuG dLvhOhysQNnaZfK7S3S4BJgi4mzNLD5z0dMES3RH8u5nqgD+sFiRpgItXpwLyM/4DIa8 hScw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=gznEs5OoLLR5aDgrIqLRLNuunkVR7yBU8hJK1R5w1zA=; b=itvqn8EYEexrlkM2JWEjBqUdh0rIlBBxYN/mCETThFYMxosX0a4ru57sPPEI9p1ZCa I+WRsxDQfiIbMHX3Ac6gJhR/IhnGoErl5hM8dx6eYQ6MzxwSZv6ObkB51To63x0QQaXP 0l1ljqUyAO+LC/SyfQU4yLmKQMHyXngg/n6+k/ahx31TyLnu24MSTKHaim+mCA78zq7k GbhMmuFa4sDJP4IeIERgYxFrmy7Sx5n2EpkSNRVyMNWkymwMQxSusEqHdOxQp9k+4pdE FnTsjHH4e+vX6I2APjTogufr3HjiHis4IHapzxSQ0CfFS0UBXqUEVTM5BSPU7bm/vj5L lVmQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n6si17618638jaj.81.2021.04.06.07.06.08; Tue, 06 Apr 2021 07:06:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235757AbhDFIBI convert rfc822-to-8bit (ORCPT + 99 others); Tue, 6 Apr 2021 04:01:08 -0400 Received: from coyote.holtmann.net ([212.227.132.17]:40858 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233608AbhDFIBH (ORCPT ); Tue, 6 Apr 2021 04:01:07 -0400 Received: from mac-pro.holtmann.net (p4ff9fed5.dip0.t-ipconnect.de [79.249.254.213]) by mail.holtmann.org (Postfix) with ESMTPSA id 81144CED1C; Tue, 6 Apr 2021 10:08:39 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Subject: Re: [Bluez PATCH] btmgmt: Add support to enable LL privacy From: Marcel Holtmann In-Reply-To: Date: Tue, 6 Apr 2021 10:00:56 +0200 Cc: Sathish Narasimman , "linux-bluetooth@vger.kernel.org" , Chethan T N , "Srivatsa, Ravishankar" Content-Transfer-Encoding: 8BIT Message-Id: <588F99C8-E5B4-47D3-84C3-72F9E6FCC9EC@holtmann.org> References: <20210405145802.27317-1-sathish.narasimman@intel.com> To: Luiz Augusto von Dentz X-Mailer: Apple Mail (2.3654.60.0.2.21) Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Luiz, >> If the Bluetooth controller supports LL privacy this command will be >> used to test the same. >> "sudo btmgmt power off" >> "sudo btmgmt llprivacy on" >> "sudo btmgmt power on" >> >> Signed-off-by: Sathish Narasimman >> --- >> tools/btmgmt.c | 38 ++++++++++++++++++++++++++++++++++++++ >> 1 file changed, 38 insertions(+) >> >> diff --git a/tools/btmgmt.c b/tools/btmgmt.c >> index 93d244ff8ec8..4a53c3768fe9 100644 >> --- a/tools/btmgmt.c >> +++ b/tools/btmgmt.c >> @@ -2261,6 +2261,42 @@ static void cmd_bredr(int argc, char **argv) >> cmd_setting(MGMT_OP_SET_BREDR, argc, argv); >> } >> >> +static void ll_rpa_resoln_rsp(uint8_t status, uint16_t len, const void *param, >> + void *user_data) >> +{ >> + if (status != 0) >> + error("Could not set LL RPA resolution with status 0x%02x (%s)", >> + status, mgmt_errstr(status)); >> + else >> + print("LL RPA Resolution successfully set"); >> + >> + bt_shell_noninteractive_quit(EXIT_SUCCESS); >> +} >> + >> +static void cmd_set_ll_rpa_resoln(int argc, char **argv) >> +{ >> + /* 15c0a148-c273-11ea-b3de-0242ac130004 */ >> + static const uint8_t rpa_resolution_uuid[16] = { >> + 0x04, 0x00, 0x13, 0xac, 0x42, 0x02, 0xde, 0xb3, >> + 0xea, 0x11, 0x73, 0xc2, 0x48, 0xa1, 0xc0, 0x15, >> + }; >> + struct mgmt_cp_set_exp_feature cp; >> + uint16_t index; >> + >> + memset(&cp, 0, sizeof(cp)); >> + memcpy(cp.uuid, rpa_resolution_uuid, 16); >> + >> + index = mgmt_index; >> + if (index == MGMT_INDEX_NONE) >> + index = 0; >> + >> + if (parse_setting(argc, argv, &cp.action) == false) >> + return bt_shell_noninteractive_quit(EXIT_FAILURE); >> + >> + mgmt_send(mgmt, MGMT_OP_SET_EXP_FEATURE, index, >> + sizeof(cp), &cp, ll_rpa_resoln_rsp, NULL, NULL); >> +} >> + >> static void cmd_privacy(int argc, char **argv) >> { >> struct mgmt_cp_set_privacy cp; >> @@ -5243,6 +5279,8 @@ static const struct bt_shell_menu main_menu = { >> cmd_bredr, "Toggle BR/EDR support", }, >> { "privacy", "", >> cmd_privacy, "Toggle privacy support" }, >> + { "llprivacy", "", >> + cmd_set_ll_rpa_resoln, "Toggle LL privacy support" }, > > Let's have it as a parameter of privacy command so when a > user enters ll it enables link-layer privacy. please don’t. The privacy setting means that we start using RPAs. Also what is wrong with exp-privacy command that I already added. Regards Marcel