Linux-Bluetooth Archive on
 help / color / Atom feed
From: Anupam Roy <>
To: "" <>
	Dohyun Pyun <>,
	Semun Lee <>
Subject: Mesh Key Refreshment procedure from Config client
Date: Thu, 26 Mar 2020 20:22:52 +0530
Message-ID: <20200326145252epcms5p2b9b6bded2e2a5d9c68e680e9de403662@epcms5p2> (raw)
In-Reply-To: <20200326144743epcms5p401053700dae86ae93749df5fc77a2807@epcms5p4>

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
 - 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.

-Anupam Roy

       reply index

Thread overview: 14+ 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     ` Anupam Roy [this message]
2020-03-27  5:10       ` Stotland, Inga
     [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-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:

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

  git send-email \
    --in-reply-to=20200326145252epcms5p2b9b6bded2e2a5d9c68e680e9de403662@epcms5p2 \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Bluetooth Archive on

Archives are clonable:
	git clone --mirror linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ \
	public-inbox-index linux-bluetooth

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone