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

ot-ns Frame Control #497

Open
rlourenco-centi opened this issue Mar 20, 2023 · 1 comment
Open

ot-ns Frame Control #497

rlourenco-centi opened this issue Mar 20, 2023 · 1 comment

Comments

@rlourenco-centi
Copy link

I have some questions:

  • Is there any way to detect the content of the messages on the otns for identification? Is it possible to accurately detect the type of message that is being sent?

  • For example, when the frame_control is 56417 and the message is sent in unicast, it can be Parent Request, Child Request or a Child response .
    How can I know all the possible values for the frame control?

  • Is it possible to decrypt the capture "current.pcap"?

@EskoDijk
Copy link

The details of every frame can be seen in the PCAP file. But as you indicate, you can only see details once the frames are decrypted in Wireshark. To make decryption easy (configure only once in Wireshark), otns uses a fixed network key. This key needs to be set in the "IEEE 802.15.4 protocol parameters" in Wireshark (add key -> set "Thread hash" hash type for key).

This is a necessary detail that I wanted to add in the updated tutorial for OTNS2 somewhere in the coming weeks/months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants