linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stotland, Inga" <inga.stotland@intel.com>
To: "anupam.r@samsung.com" <anupam.r@samsung.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Cc: "dh79.pyun@samsung.com" <dh79.pyun@samsung.com>,
	"semun.lee@samsung.com" <semun.lee@samsung.com>,
	"amit.jaiswal@samsung.com" <amit.jaiswal@samsung.com>
Subject: Re: Mesh Key Refreshment procedure from Config client
Date: Fri, 27 Mar 2020 05:10:42 +0000	[thread overview]
Message-ID: <81d243b6c593e1edb6b36be87898fc57e1e5f0f2.camel@intel.com> (raw)
In-Reply-To: <20200326145252epcms5p2b9b6bded2e2a5d9c68e680e9de403662@epcms5p2>

Hi Anupam,

On Thu, 2020-03-26 at 20:22 +0530, Anupam Roy wrote:
> Hi ,
>  Presently, I am trying to check *Key Refreshment Procedure* from Mesh Config client.
> 
> For checking the operation, I did following steps
>  - Create Subnet in Config client at Net index 1
>  - Add SubNetKey to Local Node at Net Index 1
>  - Add SubNetKey to Remote Node at Net Index 1
> 

Please try to add two steps more here:
   - Update Subnet 1 (subnet-update command in main menu)
   - Update NetKey 1 for a local node (switch to config menu)

>  - Update Netkey to remote Node in Net index 1
> 
> After updating the Netkey, I believe, config client has to either send out SNB with KeyRefreshment(KR) Flag=1 & secured with updated NetKey (i.e by subnet->net_key_upd id)
> or send out "Config Key Refresh Phase Set" with transition parameter, set to 2. I could not find the later provision in cfgclient menu.
> However, Config Client seems to be not sending out Secure Network Beacon as well. So KR procedure seems to be not progressing at my setup at present.
> 
> Any hint of what could be missing will be really helpful! Thank You.
> 

Best Regards,
Inga

  reply	other threads:[~2020-03-27  5:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200326144743epcms5p401053700dae86ae93749df5fc77a2807@epcms5p4>
     [not found] ` <20200304153920epcms5p47e26659f715177b0244f18c71e4b5fed@epcms5p4>
     [not found]   ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p2>
2020-03-26 14:52     ` Mesh Key Refreshment procedure from Config client Anupam Roy
2020-03-27  5:10       ` Stotland, Inga [this message]
     [not found] <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p3>
2020-03-02 12:53 ` Regarding OOB authentication method & action for Mesh provisioner Anupam Roy
2020-03-02 14:22   ` Michał Lowas-Rzechonek
     [not found]   ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p7>
2020-03-02 14:55     ` Anupam Roy
2020-03-02 16:56       ` Gix, Brian
2020-03-02 17:15         ` Stotland, Inga
2020-03-02 17:31           ` Gix, Brian
2020-03-03  8:55             ` michal.lowas-rzechonek
     [not found]         ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p1>
2020-03-03  9:18           ` Re: " Anupam Roy
2020-03-03 18:26             ` Gix, Brian
     [not found]             ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p4>
2020-03-04 14:52               ` Anupam Roy
2020-03-27 13:47               ` RE: Re: Mesh Key Refreshment procedure from Config client Anupam Roy
2020-03-30  6:04                 ` Stotland, Inga
     [not found]                 ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p5>
2020-03-31  8:05                   ` Anupam Roy
2020-03-27  5:35           ` Anupam Roy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81d243b6c593e1edb6b36be87898fc57e1e5f0f2.camel@intel.com \
    --to=inga.stotland@intel.com \
    --cc=amit.jaiswal@samsung.com \
    --cc=anupam.r@samsung.com \
    --cc=dh79.pyun@samsung.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=semun.lee@samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).