Type 61631 in Additional CoAP port number (2).Type 19789 in Additional CoAP port number (1).Under Edit → Preferences → Protocols → CoAP: Type your monitoring Thread network mesh local prefix in Context 0.Under Edit → Preferences → Protocols → 6LoWPAN: As Key hash, select Thread hash used to derive key.As Security Suite, select AES-128 Encryption, 32 bits Integrity Protection.Type your monitoring Thread network master key in Decryption key 1.Under Edit → Preferences → Protocols → IEEE 802.15.4: The following configuration is valid for “Wireshark Version 2.1.0-Thread”. However, if the tool is used to monitor a Thread network it is recommended to configure Wireshark accordingly in order to display the complete information contained in the capture frames. The KiTools application can be used to monitor the traffic of a wide variety of applications based on the IEEE 802.15.4 wireless standard, since it is completely transparent to the protocols that are used on top of such Link Layer. The tool works for both Windows and UNIX platforms. The –file option can be used in this case combined with –live to provide the Wireshark binary path, if it is installed somewhere else. The additional –live option tries to open a Wireshark instance from its default installation path, and makes possible to see the captured traffic in real time. Python -m kitools –port COM36 –channel 26 –file “C:\Users\Kirale\mycapture.pcap”
It is also possible to start a capture directly by providing the dongle’s port name, capture channel and output file name. If a KTDG102 USB Dongle is plugged in the computer, with the Sniffer firmware flashed and the proper drivers installed, the tool will detect it as a Kirale Sniffer and prompt the user for the desired channel, writing the captured packets in a PCAP file in the execution folder with a file name which includes the starting capture date. The open source KiTools project provides, among other functionalities, a simple way of starting a IEEE 802.15.4 packets capture, in both interactive and forced modes.
0 kommentar(er)
