堆棧內存溢出
  簡體   English   中英

讓兩個 Linux 虛擬機相互 Ping

[英]Getting Two Linux VMs to Ping Each Other

 原文  2020-05-08 13:31:31  9   1    networking/ redhat/ vmware/ vmware-workstation

問題描述

我正在使用帶有兩個 Linux 虛擬機的 VMWare Workstation 14.1.8：Red Hat 6 和 Red Hat 7。我需要它們能夠在 Windows 10 主機上相互 ping。我讓它們都使用自定義特定設置虛擬網絡（VMNet2（僅限主機）在 192.168.116 范圍內），IP 為：

RH6：192.168.116.128

RH7：192.168.116.129

由於某種原因，RH7 可以 ping 到 RH6，但 RH6 不能 ping 到 RH7。 我覺得我的 VMWare 設置是正確的，問題出在 RH6 網絡配置上。 我可以在 RH6 機器上采取哪些步驟來修復網絡配置，以便 ping RH7 虛擬機？

這是我從 RH7 ping 到 RH6 時發生的情況（成功）

這就是我嘗試從 RH6 ping 到 RH7 時發生的情況

編輯：從 RH6 添加 tcpdump output。 所以似乎 RH6 以某種方式看到了 RH7，因為 00:0c:29:51:10:97 是 RH7 VM 的 MAC 地址。

[root@cody-rh6 network-scripts]# tcpdump -ennqti eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.60172 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.60171 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.60171 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.60172 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.60171 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.60172 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.60171 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.60172 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.60171 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.60172 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.60171 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.60172 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.60171 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.60172 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 216: 192.168.116.1.49299 > 239.255.255.250.1900: UDP, length 174
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 216: 192.168.116.1.49299 > 239.255.255.250.1900: UDP, length 174
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 216: 192.168.116.1.49299 > 239.255.255.250.1900: UDP, length 174
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 216: 192.168.116.1.49299 > 239.255.255.250.1900: UDP, length 174
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.57946 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.57945 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.57945 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.57946 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.57945 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.57946 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.57945 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.57946 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.57945 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.57946 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.57945 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.57946 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.57945 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.57946 > ff02::c.3702: UDP, length 656
00:0c:29:e9:65:f3 > ff:ff:ff:ff:ff:ff, ARP, length 42: Request who-has 192.168.116.129 tell 192.168.116.128, length 28
00:0c:29:51:10:97 > 00:0c:29:e9:65:f3, ARP, length 60: Reply 192.168.116.129 is-at 00:0c:29:51:10:97, length 46

WHERE I STARTED THE PING

00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 1, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 2, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 3, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 4, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 5, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 6, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 7, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 8, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 9, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 10, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 11, length 64
00:0c:29:51:10:97 > 01:00:5e:00:00:fb, IPv4, length 160: 192.168.116.129.5353 > 224.0.0.251.5353: UDP, length 118
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 12, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 59971, seq 13, length 64

ENDED PING

00:0c:29:e9:65:f3 > 00:50:56:ff:82:3b, IPv4, length 342: 192.168.116.128.68 > 192.168.116.254.67: UDP, length 300
00:50:56:ff:82:3b > 00:0c:29:e9:65:f3, IPv4, length 342: 192.168.116.254.67 > 192.168.116.128.68: UDP, length 300
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 79: 192.168.116.128.55467 > 192.168.116.1.53: UDP, length 37
00:0c:29:e9:65:f3 > 00:50:56:ff:82:3b, ARP, length 42: Request who-has 192.168.116.254 tell 192.168.116.128, length 28
00:50:56:ff:82:3b > 00:0c:29:e9:65:f3, ARP, length 60: Reply 192.168.116.254 is-at 00:50:56:ff:82:3b, length 46
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, ARP, length 42: Request who-has 192.168.116.1 tell 192.168.116.128, length 28
00:50:56:c0:00:02 > 00:0c:29:e9:65:f3, ARP, length 60: Reply 192.168.116.1 is-at 00:50:56:c0:00:02, length 46
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 79: 192.168.116.128.55467 > 192.168.116.1.53: UDP, length 37
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 91: 192.168.116.128.40800 > 192.168.116.1.53: UDP, length 49
00:0c:29:51:10:97 > 00:50:56:ff:82:3b, IPv4, length 342: 192.168.116.129.68 > 192.168.116.254.67: UDP, length 300
00:50:56:ff:82:3b > 00:0c:29:51:10:97, IPv4, length 342: 192.168.116.254.67 > 192.168.116.129.68: UDP, length 300
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 216: 192.168.116.1.49346 > 239.255.255.250.1900: UDP, length 174
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 216: 192.168.116.1.49346 > 239.255.255.250.1900: UDP, length 174
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 91: 192.168.116.128.40800 > 192.168.116.1.53: UDP, length 49
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 216: 192.168.116.1.49346 > 239.255.255.250.1900: UDP, length 174
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.49349 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.49348 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.49348 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.49349 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.49348 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 216: 192.168.116.1.49346 > 239.255.255.250.1900: UDP, length 174
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.49349 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.49348 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.49349 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.49348 > 239.255.255.250.3702: UDP, length 656
00:0c:29:51:10:97 > 00:50:56:ff:82:3b, ARP, length 60: Request who-has 192.168.116.254 tell 192.168.116.129, length 46
00:50:56:ff:82:3b > 00:0c:29:51:10:97, ARP, length 60: Reply 192.168.116.254 is-at 00:50:56:ff:82:3b, length 46
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.49349 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.49348 > 239.255.255.250.3702: UDP, length 656
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 81: 192.168.116.128.35443 > 192.168.116.1.53: UDP, length 39
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.49349 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.49348 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.49349 > ff02::c.3702: UDP, length 656
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 81: 192.168.116.128.35443 > 192.168.116.1.53: UDP, length 39
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 93: 192.168.116.128.56316 > 192.168.116.1.53: UDP, length 51
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 93: 192.168.116.128.56316 > 192.168.116.1.53: UDP, length 51
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 83: 192.168.116.128.52652 > 192.168.116.1.53: UDP, length 41
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, ARP, length 42: Request who-has 192.168.116.1 tell 192.168.116.128, length 28
00:50:56:c0:00:02 > 00:0c:29:e9:65:f3, ARP, length 60: Reply 192.168.116.1 is-at 00:50:56:c0:00:02, length 46
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 83: 192.168.116.128.52652 > 192.168.116.1.53: UDP, length 41
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 83: 192.168.116.128.52898 > 192.168.116.1.53: UDP, length 41
00:0c:29:e9:65:f3 > 00:50:56:c0:00:02, IPv4, length 83: 192.168.116.128.52898 > 192.168.116.1.53: UDP, length 41
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.52566 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.52565 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.52566 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.52565 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.52566 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.52565 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.52566 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.52565 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.52566 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > ff:ff:ff:ff:ff:ff, IPv4, length 92: 192.168.116.1.137 > 192.168.116.255.137: UDP, length 50
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.52565 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.52566 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.52565 > 239.255.255.250.3702: UDP, length 656
00:50:56:c0:00:02 > 33:33:00:00:00:0c, IPv6, length 718: fe80::456e:a615:2dbc:c4bf.52566 > ff02::c.3702: UDP, length 656
00:50:56:c0:00:02 > 01:00:5e:7f:ff:fa, IPv4, length 698: 192.168.116.1.52565 > 239.255.255.250.3702: UDP, length 656

來自 RH6 的路由表：

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.116.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0

虛擬網絡編輯器設置：

虛擬網絡編輯器設置

vmnet2 DHCP 設置（兩個 vm 都設置為使用）：

VMNet2 DHCP 設置

所以我之前也打算發布 RH7 路由表，但它看起來與 RH6 完全相同：

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.116.0   0.0.0.0         255.255.255.0   U         0 0          0 ens37

這是我從 RH6 ping 時 RH7 tcpdump 的樣子：

[root@localhost groberts]# tcpdump -ennqti ens37
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens37, link-type EN10MB (Ethernet), capture size 262144 bytes
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 1, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 2, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 3, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 4, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 5, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, ARP, length 60: Request who-has 192.168.116.129 tell 192.168.116.128, length 46
00:0c:29:51:10:97 > 00:0c:29:e9:65:f3, ARP, length 42: Reply 192.168.116.129 is-at 00:0c:29:51:10:97, length 28
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 6, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 7, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 8, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 9, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 10, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 11, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 12, length 64
00:0c:29:e9:65:f3 > 00:0c:29:51:10:97, IPv4, length 98: 192.168.116.128 > 192.168.116.129: ICMP echo request, id 36126, seq 13, length 64

最終編輯：看來防火牆是罪魁禍首。 我運行了“service firewalld stop”，RH6 現在收到來自 RH7 的 ping： 在此處輸入圖像描述

1 個解決方案

解決方案1
 0 已采納  2020-05-11 12:58:53

因此，防火牆似乎是罪魁禍首。 我運行了“service firewalld stop”，RH6 現在收到來自 RH7 的 ping。

暫無
暫無

聲明:本站的技術帖子網頁，遵循CC BY-SA 4.0協議，如果您需要轉載，請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

相關問題 無法通過 LAN 從 windows ping avahi 別名，但可以從其他 linux 虛擬機 Virtualbox - 配置兩個VM以相互通信/主機和Internet 橋接網絡-VM ping問題 如何連接2台VMware機器互相ping通 Azure VM無法ping 將Kents的Centos VM彼此連接 無法ping通兩個即席無線筆記本電腦（Linux） 如何啟用Docker容器通過其主機名相互ping通？ 允許局域網網段在多宿主路由器上相互ping通 如何使用腳本檢查遠程服務器是否可以互相ping通？
相關標簽
 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM