blocks|key|2445908|text|下面是Windows和Linux的ping命令之间的区别。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2445909|备注：|2445910|2445911|Linux+system+=+192.168.1.201|unordered-list-item|2445912|Windows+system+=+192.168.1.7|2445913|the以下输出来自|2445914|数据包捕获|2445915|从Windows+pinging时：|2445916|18:21:38.740379+IP+192.168.1.7+>+192.168.1.201:+ICMP+echo+request,+id+1,+seq+3094,+length+40
18:21:38.740433+IP+192.168.1.201+>+192.168.1.7:+ICMP+echo+reply,+id+1,+seq+3094,+length+40|code-block|syntax|javascript|2445917|从Linux执行Linux操作时：|2445918|18:29:44.152333+IP+192.168.1.201+>+192.168.1.7:+ICMP+echo+request,+id+11524,+seq+1,+length+64
18:29:44.152460+IP+192.168.1.7+>+192.168.1.201:+ICMP+echo+reply,+id+11524,+seq+1,+length+64|2445919|id和seq无关紧要。然而，length是一个实质性的区别。|2445920|要使Linux在这方面与Windows相匹配，您可以指定数据包大小(它设置数据有效负载的大小，它将在顶部添加8字节的开销)。|2445921|此Linux命令：|2445922|$+ping+192.168.1.7+-s+32|2445923|此数据包捕获的结果：|2445924|18:30:59.528357+IP+192.168.1.201+>+192.168.1.7:+ICMP+echo+request,+id+11569,+seq+2,+length+40
18:30:59.528522+IP+192.168.1.7+>+192.168.1.201:+ICMP+echo+reply,+id+11569,+seq+2,+length+40+++|2445925|2445926|关于nmap的使用，您可以使用-O标志来启用它的operating+system+detection+feature。|2445927|$+nmap+-O+<target+IP>|2445928|entityMap|0|LINK|mutability|MUTABLE|url|https://nmap.org/book/man-os-detection.html^0|H|4|0|0|0|0|0|0|0|0|0|0|0|0|2|3|3|E|6|0|0|0|0|0|0|0|2|4|F|2|O|Y|0|0|0^^$0|@$1|2|3|4|5|6|7|1R|8|@$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1U|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|1W|8|@]|D|@]|E|$]]|$1|L|3|M|5|K|7|1X|8|@]|D|@]|E|$]]|$1|N|3|O|5|K|7|1Y|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|20|8|@]|D|@]|E|$]]|$1|T|3|U|5|V|7|21|8|@]|D|@]|E|$W|X]]|$1|Y|3|Z|5|6|7|22|8|@]|D|@]|E|$]]|$1|10|3|11|5|V|7|23|8|@]|D|@]|E|$W|X]]|$1|12|3|13|5|6|7|24|8|@$9|25|A|26|B|C]|$9|27|A|28|B|C]|$9|29|A|2A|B|C]]|D|@]|E|$]]|$1|14|3|15|5|6|7|2B|8|@]|D|@]|E|$]]|$1|16|3|17|5|6|7|2C|8|@]|D|@]|E|$]]|$1|18|3|19|5|V|7|2D|8|@]|D|@]|E|$W|X]]|$1|1A|3|1B|5|6|7|2E|8|@]|D|@]|E|$]]|$1|1C|3|1D|5|V|7|2F|8|@]|D|@]|E|$W|X]]|$1|1E|3|-4|5|6|7|2G|8|@]|D|@]|E|$]]|$1|1F|3|1G|5|6|7|2H|8|@$9|2I|A|2J|B|C]|$9|2K|A|2L|B|C]]|D|@$9|2M|A|2N|1|2O]]|E|$]]|$1|1H|3|1I|5|V|7|2P|8|@]|D|@]|E|$W|X]]|$1|1J|3|-4|5|6|7|2Q|8|@]|D|@]|E|$]]]|1K|$1L|$5|1M|1N|1O|E|$1P|1Q]]]]

Here's an illustration of the difference between the Windows vs. Linux <code>ping</code> command.

Notes:

<ul>
<li>Linux system = 192.168.1.201</li>
<li>Windows system = 192.168.1.7</li>
<li>the outputs below are from <code>tcpdump</code> packet captures</li>
</ul>

When pinging from Windows:

<pre><code>18:21:38.740379 IP 192.168.1.7 &gt; 192.168.1.201: ICMP echo request, id 1, seq 3094, length 40
18:21:38.740433 IP 192.168.1.201 &gt; 192.168.1.7: ICMP echo reply, id 1, seq 3094, length 40
</code></pre>

When pinging from Linux:

<pre><code>18:29:44.152333 IP 192.168.1.201 &gt; 192.168.1.7: ICMP echo request, id 11524, seq 1, length 64
18:29:44.152460 IP 192.168.1.7 &gt; 192.168.1.201: ICMP echo reply, id 11524, seq 1, length 64
</code></pre>

The <code>id</code> and <code>seq</code> are inconsequential. However, <code>length</code> is a material difference.

To make Linux match Windows on that front, you can specify a packet size (which sets the size of the data payload, which will have 8 bytes of overhead added on top).

This Linux command:

<pre><code>$ ping 192.168.1.7 -s 32
</code></pre>

Results in this packet capture:

<pre><code>18:30:59.528357 IP 192.168.1.201 &gt; 192.168.1.7: ICMP echo request, id 11569, seq 2, length 40
18:30:59.528522 IP 192.168.1.7 &gt; 192.168.1.201: ICMP echo reply, id 11569, seq 2, length 40 
</code></pre>

<hr>

Regarding the use of <code>nmap</code>, you can use the <code>-O</code> flag to enable it's <a href="https://nmap.org/book/man-os-detection.html" rel="nofollow noreferrer">operating system detection feature</a>.

<pre><code>$ nmap -O &lt;target IP&gt;
</code></pre>

I have an antenna dish pedestal. Something that looks like this (just one of these). Eventually pedestal will have an dish antenna connected to it.
<a href="https://i.stack.imgur.com/WhkTY.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/WhkTY.jpg" alt="enter image description here" /></a>
This pedestal has two motors to rotate the dish horizontally and vertically. Each motor has an IP address. For the sake of the discussion let's assume they are 10.10.10.161 and 10.10.10.162
The company (can't disclose it) that makes the pedestals provides a Windows application to communicate with the pedestal over Ethernet (sends UDP packets).
We tried pinging both of the motors from Windows and had no issues. However when we ping the motors from Linux there is no response.
We tried looking up online what could be the issue but didn't find any reasonable answers. To add to our problems, our project manager doesn't allow us to contact the pedestal manufacturer. We must find an explanation of the problem first and then we can let the manufacturer know what the issue is.
Has anyone encountered this type of problem before (able to ping from Windows but not able to ping from Linux)? If yes, then wow did you resolve the issue? What are we missing?

talking to a network device on windows and on linux

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有一个天线碟座。看起来像这样的东西(只是其中之一)。最终底座将有一个碟形天线连接到它。​​这个底座有两个马达来水平和垂直旋转碟子。每个电机都有一个IP地址。为了便于讨论，我们假设它们是10.10.10.161和10.10.10.162制造底座的公司(不能透露)提供了一个Windows应用程序来通过以太网与底座通信(发...

在windows和linux上与网络设备对话-腾讯云开发者社区-腾讯云

问在windows和linux上与网络设备对话
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在windows和linux上与网络设备对话EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在windows和linux上与网络设备对话
EN