All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anupam Roy <anupam.r@samsung.com>
To: "Stotland, Inga" <inga.stotland@intel.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	Dohyun Pyun <dh79.pyun@samsung.com>,
	Semun Lee <semun.lee@samsung.com>,
	AMIT KUMAR JAISWAL <amit.jaiswal@samsung.com>,
	Nitin Jhanwar <nitin.j@samsung.com>
Subject: RE: RE: Re: Mesh Key Refreshment procedure from Config client
Date: Fri, 27 Mar 2020 19:17:42 +0530	[thread overview]
Message-ID: <20200327134742epcms5p46a971a1f5653956a287898e01a296dee@epcms5p4> (raw)
In-Reply-To: <20200327053515epcms5p1cd532ff3b1ac4b97d375a6336e3ded50@epcms5p1>

 
Hi Inga,

>--------- Original Message ---------
>Sender : Anupam Roy <anupam.r@samsung.com> Staff Engineer/Application S/W Group /SRI-Delhi/Samsung Electronics
>Date : 2020-03-27 11:07 (GMT+5:30)
>Title : RE: Re: Mesh Key Refreshment procedure from Config client
> 
>Hi Inga,
> 
>> 
>>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)
>I missed mentioning above step in my email. Actually, before updating netkey to remote, I did update local subnet.
>But yes, I missed out below step (Updating netkey to local node). Will give it a try now. Much thanks!
>

After updating the Netkey to the local node(config client) and then to the remote node, I monitored the beaconing key used by local config client.
Please note that since, only two netkeys are at presently configured in both the nodes, therefore, the key ID's are 1 (for primary netkey at index 0), 2(For Netkey at index 1) & 3(For new NetKey at index 1).

After NetKey update, The KR phase in both sides are set to 1, but it seems, the new key id (which is 3 in this case) is still *NOT used for beaconing, by the 'Config Client node'
Config Client still keeps on beaconing with key ID 1 & 2. Sharing a bit of logs for your reference.

During NetKey Update-
mesh/cfgmod-server.c:cfg_srv_pkt() CONFIG-SRV-opcode 0x8045 size 18 idx 000
key refresh phase 1: Key ID 3

Beacon Keys after NetKey update on remote Node -
mesh/net-keys.c:snb_timeout() beacon 2 for 1 nodes, period 30, obs 2, exp 3
mesh/net-keys.c:snb_timeout() beacon 1 for 1 nodes, period 20, obs 2, exp 2

Please share your opinion to check the issue further. Thank You
 
>>   - 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

BR,
-Anupam Roy

  parent reply	other threads:[~2020-03-27 13:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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               ` Anupam Roy [this message]
2020-03-30  6:04                 ` RE: Re: Mesh Key Refreshment procedure from Config client Stotland, Inga
     [not found]                 ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p5>
2020-03-31  8:05                   ` Anupam Roy
2020-03-27  5:35           ` Anupam Roy
     [not found] <20200326144743epcms5p401053700dae86ae93749df5fc77a2807@epcms5p4>
     [not found] ` <20200304153920epcms5p47e26659f715177b0244f18c71e4b5fed@epcms5p4>
     [not found]   ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p2>
2020-03-26 14:52     ` Anupam Roy
2020-03-27  5:10       ` Stotland, Inga

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=20200327134742epcms5p46a971a1f5653956a287898e01a296dee@epcms5p4 \
    --to=anupam.r@samsung.com \
    --cc=amit.jaiswal@samsung.com \
    --cc=dh79.pyun@samsung.com \
    --cc=inga.stotland@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=nitin.j@samsung.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.