Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reporting: If chip-tool does not initiate the connection to the server, incoming reports are dropped #4531

Closed
woody-apple opened this issue Jan 27, 2021 · 3 comments
Assignees
Labels
lib p1 priority 1 work testing
Milestone

Comments

@woody-apple
Copy link
Contributor

Problem

If chip-tool does not initiate the connection to the server, incoming reports are dropped with: CHIP: [IN] Data received on an unknown connection (0). Dropping it!!

@pan-apple
Copy link
Contributor

The issue is caused by the unprovoked message (reports) from the server to chip-tool. This will be handled by CASE session setup mechanism. The flow of events will be

  1. chip-tool perform the device pairing, and provisions operational credentials on the device.
  2. At some point in time, the device generates a report that will be sent to another node (e.g. chip-tool)
  3. The device looks for an existing CASE session with the other node. If one exists, it'll use it. Otherwise, it'll setup a new CASE session using the provisioned operational credentials.
  4. The CASE handshake will ensure that the other node (chip-tool) has a secure connection that can receive and decrypt the data.
  5. The device will send the report using the secure session established via CASE.

Currently, the CASE handshake is not implemented in the code. I talked to @vivien-apple and he has a work around for the time being. So, maybe we can wait for CASE implementation to resolve this issue.

@woody-apple woody-apple added this to the V0.7 milestone Feb 3, 2021
@woody-apple woody-apple modified the milestones: V0.7, Next Feb 4, 2021
@franck-apple franck-apple modified the milestones: Next, Test Event 1 Feb 26, 2021
@franck-apple franck-apple added TE2 and removed TE1 labels Mar 9, 2021
@franck-apple franck-apple added TE3 and removed TE2 labels Apr 20, 2021
@pan-apple
Copy link
Contributor

The following PRs had some CASE related work done that's relevant to this issue.
#6810
#6791

@franck-apple franck-apple added TE4 and removed TE3 labels May 17, 2021
@woody-apple
Copy link
Contributor Author

SW Dev Bug Review: Closing this, as doesn't appear needed anymore and/or is complete, please reopen if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lib p1 priority 1 work testing
Projects
None yet
Development

No branches or pull requests

4 participants