On Wed, 2019-01-30 at 22:47 +0800, Ed Greshko wrote: > On 1/30/19 9:31 PM, Patrick O'Callaghan wrote: > > I hesitate to wimp out and reinstall it, > > but I'm running out of ideas. > > Before doing that I think I would create a couple of new F29 VM's and see if the new ones > exhibit the same issue as the old ones. I created a single F29 Server guest using all default settings. Running only that guest, pings work in both directions. When I boot the Windows guest, both guests are disconnected and pings from the host to either of them fail. Even when I shut down the Windows guest, they continue to fail. Rebooting the F29 guest from within does not fix the problem. Shutting it down from the host and restarting it does fix it. With Windows shut down: Running F28 and F29 guests fails. Running F29 and a cloned F29 fails. Running F29 and a fresh install of F29 fails. When the Windows guest is running on its own, it works. Ditto any of the Fedora guests on its own. In every case, failure occurs not instantly but after a few seconds, as if something is timing out. DHCP leases are an hour by default so I wondered if it could be an ARP cache problem. I rebooted both Fedora guests and ran 'arp' on each one as soon as they came up. They both show *the same MAC address*: 52:54:00:8b:88:60, which looks at least suspicious. Then after less than a minute I ran 'arp' on each of them again, and they both returned a hardware address of '(incomplete)'. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
