3/20/2024 0 Comments Ping loopback ping local![]() Valid_lft 83207sec preferred_lft 83207sec Tracing route to 192.168.111.81 over a maximum of 30 hopsġ: lo: mtu 65536 qdisc noqueue state UNKNOWN group default Tunnel adapter Teredo Tunneling Pseudo-Interface:ĭescription. : Bluetooth Device (Personal Area Network) : 192.168.220.2Įthernet adapter Bluetooth Network Connection: : VMware Virtual Ethernet Adapter for VMnet8 : fec0:0:0:ffff::1%1Įthernet adapter VMware Network Adapter VMnet8:ĭescription. : VMware Virtual Ethernet Adapter for VMnet1 : EnabledĮthernet adapter VMware Network Adapter VMnet1:ĭescription. : Intel(R) 82579V Gigabit Network Connection The fact that at least 3 independent machines exhibit the same issue suggests it's more subtle (or blunt!) than me messing up my home desktop though. Is there any magic hoop jumping required now? Or maybe has a small bug crept in and gone unnoticed for a while? I'm thinking I shouldn't have to do anything other than say bridged networking. ![]() This has worked in the past as I used guest accessing host for the shared partition. And a friend with a winxp guest inside win10 host also cannot ping between each other. I also tried the work laptop and host/guest cannot ping each other with bridged networking. I also tried a quick new guest and it has the same problem. It turns out that host and guest cannot ping each other at all. Sometime (maybe a few months ago?) it stopped working. win10 exports a mount over smb and the linux mounts it and this gives me a shared partition. Host and guest can access everything they should, except they cannot access/ping each other. I have a win10 host with a debian jessie guest and bridged networking.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |