The ping packet in Linux returns DUP.

When the ping packet of Linux returns the system ping Internet address created on DUP virtual machine, DUP is easy to occur! The virtual machine here is workstation, not esxi. Returns: 64 bytes from 115.239.210.26: icmp_seq = 1 ttl = 57 time = 10 MS 64 bytes from 115.239.210.26: icmp_seq = 1 ttl = 56 time = 12 MS (DUP !) 64 bytes from 115.239.210.26: icmp_seq = 2 ttl = 56 time = 12 MS 64 bytes from 115.239.210.26: icmp_seq = 2 ttl = 56 time = 13 MS (DUP !) 64 bytes from 115.239.210.26: icmp_seq = 3 ttl = 57 time = 10 MS 64 bytes from 115.239.210.26: icmp_seq = 3 ttl = 56 time = 12 MS (DUP !) 64 bytes from 115.239.210.26: icmp_seq = 4 ttl = 56 time = 12 MS 64 bytes from 115.239.210.26: icmp_seq = 4 ttl = 56 time = 13 MS (DUP !) (DUP !) This is an abbreviation of DUPLICATE, that is, when the ping packet receives multiple repeated response values, usually occurs in a linux environment, in windows, the ping reply is only sent to the first one, and subsequent repeated responses will be discarded. This usually happens when the IP address of the host machine conflicts, or the gateway has repeated route settings, or the router is blocked badly. There may be other reasons. The solution is to change the IP address segment of the host.