1, VMware Workstation 12 Pro installed on Centos 7.3,
The host OS(Centos 7.3) with network interface eth0 with address 192.168.1.10/24 and 192.168.10.1/24
"vmware-modconfig --console --install-all" was performed while host OS kernel updated under the host OS.
192.168.1.1/24 is default router.
192.168.10.0/24 is forward into 192.168.1.10/24, which is configured in router 192.168.1.1 as static route table item.
net.ipv4.ip_forward = 1 is set in /etc/sysctl.conf.
Firewalls on all host OS and guest OS are disabled or removed.
2, For Guest OS 1, Ubuntu, bridged with address 192.168.1.100/24,
it is okay for running "ping 192.168.10.1", no packets lost.
ATTN, the source guest IP and target host IP for ping are in different subnet.
but there are about 30% packets lost for running "ping 192.168.1.10".
ATTN, the source guest IP and target host IP for ping are in same subnet.
3, For Guest OS 2, Windows 7, bridged with address 192.168.10.100/24,
it is okay for running "ping -t 192.168.1.10", no packets lost,
ATTN, the source guest IP and target host IP for ping are in different subnet.
but there are about 30% packets lost for running "ping -t 192.168.10.1".
ATTN, the source guest IP and target host IP for ping are in same subnet.
4, If only one IP address bound into the host OS, there are still about 30% packets lost for guest OS pinging host OS
while the source guest IP and target host IP for ping are in same subnet.
5, I tried different Operating Systems, e.g, Windows 8, Windows 10, CentOS, acting as Guest OS, and got the same result as descriptions of 2, 3 or 4.
6, No any issue for guest pinging guest.
No any issue for host pinging guest.
No any issue for guest pinging other available IP addresses.
7, Is there anyone confront this kind of issue? Thanks for any helps.
