6PCLEAR fails in case of schedule inconsistency due to parent switch

Description

If we do have the following setup

Node A is parent of Node B and Node C all have the minimal shared cell. And we had an dedicated cell between both pairs. Now Node B powercycles and resync to Node C.

Now it happens that Node A has a cell to Node B an there will clear that because it's not needed anymore. But sending the 6PCLEAR on the dedicated link fails on linklayer because there will be no ACK from Node B. In that case we end up in endless CLEAR Requests because sixtop_six2six_sendDone
https://github.com/openwsn-berkeley/openwsn-fw/blob/develop/openstack/02b-MAChigh/sixtop.c#L921
always resets the sixtop statemachine. If the timeout would occure the cells would been removed then but the timer is only started in case we received an ACK.

can we do something like the following without beeing inconsistent with the draft?

Environment

None

Activity

Show:
Tengfei Chang
September 25, 2018, 7:54 AM

, yes, we can. I will take this issue into my sprint and will be fixed in next release.

Christian Hopfner
February 18, 2019, 1:41 PM
Edited

Hey ,

i guess this is solved by isn't it

Tengfei Chang
March 15, 2019, 10:23 AM

With current code in the develop branch, sixtop will send on autonomous cell which won't have this problem.

Tengfei Chang
March 25, 2019, 9:58 AM

to be fixed

Tengfei Chang
July 12, 2019, 9:23 AM

The fix has been merged into develop branch.

Assignee

Christian Hopfner

Reporter

Christian Hopfner

Labels

None

Story Points

1

Sprint

None

Fix versions

Affects versions

Priority

Normal
Configure