blocks|key|246883|text|快速的网络搜索表明Wireshark正在与定制插件一起使用(由Jen尼克提供)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|246884|在当前的Wireshark源代码中找不到字符串"Jennic协议“，这强烈表明正在使用自定义版本的Wireshark。|246885|因此:我怀疑您需要咨询供应商和/或供应商文档(我注意到这些文档讨论了各种配置首选项)。|246886|在任何情况下，如果不能够分析实际的截图，基本上是不可能说得太多的；仅根据屏幕截图，我只会说以下几句。|246887|专家窗口说：“我们不支持协议版本的加密?”|246888|这指的是你突出显示的第322帧吗。如果是这样的话，信息的意思就是它所说的(假设尝试的解剖是有效的)。|246889|“格式错误”消息意味着分解器无法理解数据。|246890|更大的图景:考虑到各种各样的“麦芽糖”和不支持解密的警告，任何事情都是可能的.|246891|同样，您最好的方法可能是与供应商协商。|246892|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

A quick web search suggests that Wireshark is being used with customized plugins (provided by Jennic ?).

The string "Jennic Sniffer protocol" is not found in the current Wireshark sources which suggests strongly that a customized version of Wireshark is being used.

So: i suspect you'll need to consult with the vendor and/or the vendor documentation (which I note discusses various configuration preferences).

<hr>

In any case, it's basically impossible to say much without being able to analyze the actual capture; based only on the screen shots I'll just say the following.

The expert window says "We don't support encryption with protocol [version ?]"

Does that refer to the frame 322 that you've highlighted. If so, the message means just what it says (assuming that the attempted dissection is valid).

The "malformed" messages mean that the dissector(s) are unable to make sense of the data.

Bigger picture: Given the various "malformeds"and the warning about decryption not being supported, anything is possible...

Again, your best approach might be to consult with the vendor.

blocks|key|1567069|text|您的Wireshark屏幕截图显示您正在使用Wireshark+1.6.5+(或基于Wireshark1.6.5的定制版本)，该版本现在已经超过5年了。根据Wireshark的生命周期维基页面，对Wireshark1.6的支持于2013年6月7日结束。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1567070|从那时起就出现了IEEE802.15.4分解器的许多更新，因此，更新后的解剖可能很有可能对您现在感兴趣的数据进行剖析。|1567071|我建议您更新您的Wireshark版本。|1567072|entityMap|0|LINK|mutability|MUTABLE|url|https://www.wireshark.org/news/20120110.html|1|https://wiki.wireshark.org/Development/LifeCycle|2|https://code.wireshark.org/review/gitweb?p=wireshark.git;a=history;f=epan/dissectors/packet-ieee802154.c;h=7cd95e0fbb71409e6ceee613fe33a40a0aeebb23;hb=HEAD|3|https://www.wireshark.org/#download^0|M|F|0|2G|4|1|0|8|K|2|0|8|9|3|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]|$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|F|3|G|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|H|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]|T|$5|K|L|M|C|$N|U]]]]

Your Wireshark screenshots indicate that you're using <a href="https://www.wireshark.org/news/20120110.html" rel="nofollow noreferrer">Wireshark 1.6.5</a> (or a customized version based on Wireshark 1.6.5), which is over 5 years old now. According to Wireshark's <a href="https://wiki.wireshark.org/Development/LifeCycle" rel="nofollow noreferrer">Lifecycle</a> wiki page, support for Wireshark 1.6 ended on June 7, 2013.

There have been <a href="https://code.wireshark.org/review/gitweb?p=wireshark.git;a=history;f=epan/dissectors/packet-ieee802154.c;h=7cd95e0fbb71409e6ceee613fe33a40a0aeebb23;hb=HEAD" rel="nofollow noreferrer">many updates to the IEEE 802.15.4 dissector</a> since then and as such, there's probably a very good chance that the updated dissector dissects the data you're interested in now.

I would recommend that you update your version of <a href="https://www.wireshark.org/#download" rel="nofollow noreferrer">Wireshark</a>.

We are capturing traffic using JN5148EK010 nodes via WireShark. The packets received are shown in the screenshot provided.

<ol>
<li>I want to know how to decode the data</li>
<li>An error occurs afer capturing a few packets, whose screen shot is also provided. How to resolve this error?</li>
<li>List item</li>
</ol>

Another error (please refer to third screenshot) occured.

How to resolve that?

<img src="https://i.stack.imgur.com/GbGlR.jpg" alt="enter image description here">
<img src="https://i.stack.imgur.com/den37.png" alt="enter image description here">

<img src="https://i.stack.imgur.com/r4jAp.png" alt="enter image description here">

How to decode a packet received through WireShark & resolving some errors

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们使用JN5148EK010节点通过WireShark捕获通信量。所接收的分组显示在所提供的屏幕截图中。我想知道如何解码这些数据在捕获几个数据包后发生错误，还提供了屏幕截图。如何解决此错误？列表项目另一个错误(请参考第三个屏幕截图)发生。如何解决这个问题？​​​​

问如何解码通过WireShark接收的数据包&解决一些错误
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何解码通过WireShark接收的数据包&解决一些错误EN