Получение двух Linux виртуальных машин для проверки связи друг с другом - PullRequest
Новая
       133

Получение двух Linux виртуальных машин для проверки связи друг с другом

0 голосов
/ 08 мая 2020

Я использую VMWare Workstation 14.1.8 с двумя Linux виртуальными машинами: Red Hat 6 и Red Hat 7. Мне нужно, чтобы они могли пинговать друг друга через хост-машину, а это Windows 10. Они у меня есть. оба настроены с использованием настраиваемой виртуальной сети c (VMNet2 (только хост) в диапазоне 192.168.116) и IP-адреса:

RH6: 192.168.116.128

RH7: 192.168 .116.129

По какой-то причине RH7 может пинговать RH6, но RH6 не может пинговать RH7. Мне кажется, что мои настройки VMWare верны, а проблема заключается в конфигурации сети RH6. Какие шаги я могу предпринять на машине RH6, чтобы исправить конфигурацию сети, чтобы он пинговал виртуальную машину RH7?

Вот что происходит, когда я пингую с RH7 на RH6 (успешно)

И вот что происходит, когда я пытаюсь выполнить эхо-запрос с RH6 на RH7

Изменить: Добавление вывода tcpdump из RH6. Таким образом, кажется, что RH6 каким-то образом видит RH7, потому что 00: 0 c: 29: 51: 10: 97 - это адрес MA C виртуальной машины RH7. 

[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

Настройки редактора виртуальной сети:

Virtual Network Editor Settings

Настройки DHCP vmnet2 (что настроено на использование обеих виртуальных машин):

VMNet2 DHCP Settings

Итак, я собирался опубликовать таблицу маршрутизации 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

Вот как выглядит tcpdump RH7, когда я пингую его с RH6: 

[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

Final Edit: Похоже, что виновником был брандмауэр. Я запустил «остановка службы firewalld», и теперь RH6 получает эхо-запросы от RH7: enter image description here

1 Ответ

0 голосов
/ 11 мая 2020

Так что, похоже, виноват брандмауэр. Я выполнил команду «service firewalld stop», и теперь RH6 получает эхо-запросы от RH7.

...