Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp66291ybg; Mon, 27 Jul 2020 15:48:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz72GK/tHYMlAF6K1rgMBRS5XTlpGQmgVqry+O6r8iOhaV4HT2CjxJstWTqRsT/CeLRyXnB X-Received: by 2002:a17:906:65b:: with SMTP id t27mr24078466ejb.457.1595890118836; Mon, 27 Jul 2020 15:48:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595890118; cv=none; d=google.com; s=arc-20160816; b=itx1fi5NnIA7TYgvIhn8pb2TzdNP+7V+zHnlz0ruO5R0yvDgPGgD8k5fM80ZrKbODB CchQNmjF+HgN/+s4WkBTcEh6n0eu+tfkrhUv3tYhYzb9MrUowDhdOn29uoz5/P5LYbe4 WWHm3rwL5GyoFabEa/8do/pTuYLSzS3To/1CGBpuO53mevSFPlYBoGud8MLNU3PP9VDA Y+xvRgud4veDx3H/mrAURagXnhuL28SjMPxiWch6lkSnORonn4iSJhUVBKqq2tLk+PVs KzHA9PsCU0+u2XyoJY3fTtEMlD6EbbJIAMAE/sRCWafCrsVlIY375EpEj+6UVnsSz5H4 8U4Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:mime-version:user-agent:date:message-id:subject :from:to:dkim-signature; bh=OCyVDUVx8KivTGbYC1Yp2Urd9ENGTmoja398E/dFYXw=; b=a3ydGPUNVuTHYvxssnYhpJoVXwnQntA0KE7A64E9dflEWh2WXpZYoH42zDR898c/HY uRcm27BeZIKGLATLRfjs4Ms8J2tVTdlYW3xEuoI4Logh+r8pJw3Sx+3i/6SjjGUV1jzT tNde9sfzCHVckl8Prm81Dp04K6QPQB5Y6Oq3s7Zu8XuySy2fTGdLMYyOSQ92jsrkvDWL ZKpY/0myhBzdaQ236Oe4tesDUj62FBJ1Qu9Bz4bqXrhKwZomb/4GisqwO3oZtKKWQifR ZKX/DuGZVWRPFH5tI1xGmZU/nx0dKExFgqn1Cj/HgCyofa17Y+FCtEB8VF/m+OLd2BgQ fqqQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mnmoran.org header.s=dkim header.b="Oru7qi/6"; 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 y1si6687126edp.472.2020.07.27.15.47.55; Mon, 27 Jul 2020 15:48:38 -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; dkim=pass header.i=@mnmoran.org header.s=dkim header.b="Oru7qi/6"; 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 S1726283AbgG0Wrv (ORCPT + 99 others); Mon, 27 Jul 2020 18:47:51 -0400 Received: from hoster906.com ([192.252.156.27]:57740 "EHLO hoster906.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726193AbgG0Wru (ORCPT ); Mon, 27 Jul 2020 18:47:50 -0400 X-Greylist: delayed 402 seconds by postgrey-1.27 at vger.kernel.org; Mon, 27 Jul 2020 18:47:50 EDT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=mnmoran.org; h=to:from :subject:message-id:date:mime-version:content-type :content-transfer-encoding; s=dkim; bh=aIGtX9zi9W5zjNuLkOa3D3TfS XfE3Ezgda+99Ph+dbA=; b=Oru7qi/6pyDtuCs8GkpFgKrW2v5viAKQGh+lstEEa 1Gm1FkhIx8av2EtdRuQr3OtVb3Ch8R90JEtqffx6NZYierdkYCOeqgYyOhveObq9 wJIKc7RH944zG0hoMw+cSOWTWULzmm7NxjF1sewAr+fj8QP6eZKP/wgWSd1IZp1Q uY= Received: (qmail 13785 invoked by uid 503); 27 Jul 2020 22:41:08 -0000 Received: from unknown (HELO ?192.168.254.79?) (pop-before-smtp@162.39.210.203) by hoster906.com with ESMTPA; 27 Jul 2020 22:41:08 -0000 To: "linux-bluetooth@vger.kernel.org" From: "Michael N. Moran" Subject: Mesh: Continuous Transaction Acknowledgment Message-ID: <20d1abee-8400-19a9-6f15-d3011a8a3d0a@mnmoran.org> Date: Mon, 27 Jul 2020 18:41:02 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org I'm using a clone of bluez master on a Fedora 32 system. I was using the Fedora 32 bluez-5.54 and bluez-mesh-5.54-1 packages, but there are some issues when using mesh-test where opcodes are using the wrong byte-order that has been fixed in master. Otherwise, mesh was working OK and I was able to provision and configure my device using mesh-cfgclient. However, running the master branch code I am having a problem where provisioning does not complete and in the end, a Transaction Acknowledgment for my Random PDU is sent endlessly. The bluetooth-meshd does not seem to be sending a LE Set Advertise Enable to DISABLE advertising. I assume that bluetooth-meshd has a timer that that fires that should disable the advertisement after some period of time (150ms), but the code is a bit opaque to my eyes. I have a btmon trace the shows the problem if needed. Also, the btmon trace shows that there are two LE Set Advertise Enable (DISABLE) HCI commands in a row just before the LE Set Advertising Data is issued for the offending Transaction Acknowledgment. Thoughts? -- Michael N. Moran (h) 770 704 9751 218 Wilshire Terrace (c) 678 521 5460 White, GA, USA 30184 http://mnmoran.org