Skip to content
This repository has been archived by the owner on Nov 14, 2024. It is now read-only.

Fix WPA supplicant internal events processing #139

Merged
merged 4 commits into from
Dec 7, 2023

Conversation

krish2718
Copy link
Collaborator

No description provided.

fixup! [nrf noup] Monitor supplicant state and inform applications

Even though the payload is of fixed size, move it to the end for easier
parsing.

Signed-off-by: Chaitanya Tata <[email protected]>
fixup! [nrf noup] Monitor supplicant state and inform applications

Incoming message has a pre-defined structure and isn't a arbitrary blob,
so, use the structure to parse properly.

This was working earlier as the payload was in the beginning of the
structure, but if we ever end up with a longer message then we would see
issues.

Signed-off-by: Chaitanya Tata <[email protected]>
fixup! [nrf noup] Monitor supplicant state and inform applications

The incoming message is payload + length, so, need to include size of
the "length" field.

Fixes SHEL-2250.

Signed-off-by: Chaitanya Tata <[email protected]>
fixup! [nrf noup] Monitor supplicant state and inform applications

Sender is sending the entire structure, and receiving one byte lesser
results in two receive calls per-message, this screws up the message
parsing.

Fixes SHEL-2250.

Signed-off-by: Chaitanya Tata <[email protected]>
@rlubos rlubos merged commit 6e26b99 into nrfconnect:main Dec 7, 2023
1 check passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants