Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp1623894pxb; Fri, 6 Nov 2020 14:53:39 -0800 (PST) X-Google-Smtp-Source: ABdhPJy2zWWXTVR3mAeMu/dFDgCxwvvNgg4w//Ih0b7gYirhEIR1le3kyrVAWuI+XTmeg1GGpyvC X-Received: by 2002:a17:906:1902:: with SMTP id a2mr4185078eje.269.1604703219413; Fri, 06 Nov 2020 14:53:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604703219; cv=none; d=google.com; s=arc-20160816; b=DViEA+zlTjiUP4w9EneObMd2ps87g9FZVfZ+C22z9LKmA7JRV/+HIlH3IkfJd3u79R uVkpBm7lvoLJQO/hcAI2PzqR+CyHKxeXaoEugbu8gsqF8HEM/VYFDtMTgvk+GUi4eRoD kAj3MIZlDzGVPePGOz3qkigz1f6KlT4sy5pgK+Q9Gf6ELIxVzrkbgSc+1D/WFUJVetMo pzi5sFmKVUs/gkgxqNXpcLsEyAD2tUlGHGhd5Jyp3PRticii/HaQVu3/f3bi3jY7dxXr TmubC1PTVkfAQIwPDzd4kULic/pVqDnt25SPbm9KImdGZGwaX/euXilZ/f/XENzK4KdV oaxA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:references:to :from:subject:dkim-signature; bh=w+DqTdjqflGhPIECBRvj+f2TgN4nKDGJYRZzGzqDWqQ=; b=cwmP1u71yaRn4tUrc6UUaoXWNjX2fdcaaQ7NVlfZpgW4O7dUVl3EV1+V09uz7rYdPD mJOd7ilsPA9275EdxGqB13QelkKwUfprA/xH/JgBBCwANsGE9RxoL+MBiQvX8Rs6zshv 2tk1N5R6oHo1vaDsKjdRZw5P2WROQn9lkLFlT8rIcwc+LnBAyZuCCOcoSd8qWb2JKoBf BBt0cGPzwuVoQPFXImtMNKqvxlv6MDZl+Y08TASWTbyV3+oVrIuUfLZ3oqRcJ2LNYK+M iev/A6NeoICfVsBlaZ6KKB+5tCCgk6JtRRGoGLepRj/GUgMzdoKOqhCTPwQezhedjNqr cexA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mnmoran.org header.s=dkim header.b=urrVHUUo; 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 l3si1921749eja.544.2020.11.06.14.53.15; Fri, 06 Nov 2020 14:53:39 -0800 (PST) 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=urrVHUUo; 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 S1728358AbgKFWxJ (ORCPT + 99 others); Fri, 6 Nov 2020 17:53:09 -0500 Received: from hoster906.com ([192.252.156.27]:38650 "EHLO hoster906.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728111AbgKFWxH (ORCPT ); Fri, 6 Nov 2020 17:53:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=mnmoran.org; h=subject :from:to:references:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=dkim; bh=Vh2kFVTD94If LC7ksKz3ILzaMfiSlwrtB6Y2WEJ57Uk=; b=urrVHUUoJrfsXGrWCV2F1ANSLSbk XTBP8rBYMmM/JqaC+ZuVsqoqNZf6Dh0lj5pwCYBAhmn0m52Edpy9lRKyfP2isQoA IHP/AwJAo+ceGSTJXi4LgGDENI75A66HrGEYaRfpig3Evx1z7SnvCnF5Xz0zhREO mHzLNZ2+SjP4B9A= Received: (qmail 38253 invoked by uid 503); 6 Nov 2020 22:53:04 -0000 Received: from unknown (HELO ?192.168.254.79?) (mike@mnmoran.org@40.134.89.129) by hoster906.com with ESMTPA; 6 Nov 2020 22:53:04 -0000 Subject: Re: bluetooth-meshd: Leave borks bluetooth-meshd From: "Michael N. Moran" To: "linux-bluetooth@vger.kernel.org" References: <12e1bb50-64da-7e72-c13d-f7486fbd3283@mnmoran.org> Message-ID: Date: Fri, 6 Nov 2020 17:53:04 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1 MIME-Version: 1.0 In-Reply-To: <12e1bb50-64da-7e72-c13d-f7486fbd3283@mnmoran.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org I submitted a patch that fixes this issue. On 11/5/20 3:23 PM, Michael N. Moran wrote: > Hi Meshers, > > My provisioning/configuration application supports multiple networks. > > In general, everything works great [1] for adding, provisioning and configuring the networks. > > I recently added the org.bluez.mesh.Network1 Leave(token) to delete a network. The Leave() operation succeeds. However, when I subsequently try to use DevKeySend() on a different network, > the DevKeySend() succeeds but I never receive any responses from the addressed node. > > If I restart my application, nothing changes. > > If I restart the bluetooth-meshd, then it all starts working again > until I use Leave() again. > > The mesh-cfgclient does not seem to support Leave(), which is not > too surprising since it only supports a single network. > > This leads me to believe that the Leave() function in the bluetoot-meshd > is not very well tested. Please correct me if I'm wrong. > > I'm willing to poke around in the bluetooth-meshd code if I can get some > pointers from the bluetooth-meshd experts. :-) > > Answers: > * I am using the bluez git tip. Rebased today. > > [1] Occasionaly, bluetooth-meshd seems to get into a similar state "overnight". > -- Michael N. Moran (h) 770 704 9751 218 Wilshire Terrace (c) 678 521 5460 White, GA, USA 30184 http://mnmoran.org