Host is a Mac mini X86 working Sonoma 14.2.1, VMware Fusion Participant Model 13.5.0 (that are present as of this writing.). Visitor vms embrace Home windows 11, macOS Sonoma 14.2.1, and a Linux, the place I used to be finest in a position to isolate and diagnose the issue.
Contemplate this transcript (with some additional clean traces for readability), which begins in Terminal on the host, and continues through ssh on a contemporary (File/New/Create customized …) vm working an set up CD:
scott@Mac-mini-x86 ~ $ scutil --dns | tail -9
DNS configuration (for scoped queries)
resolver #1
search area[0] : attlocal.web
nameserver[0] : 2600:1700:6b0:e60::1
nameserver[1] : 192.168.1.254
if_index : 11 (en1)
flags : Scoped, Request A data, Request AAAA data
attain : 0x00020002 (Reachable,Instantly Reachable Deal with)
scott@Mac-mini-x86 ~ $ ping -c 1 www.ibm.com
PING user-att-162-198-200-0.e7817.dscx.akamaiedge.web (23.0.23.183): 56 information bytes
64 bytes from 23.0.23.183: icmp_seq=0 ttl=53 time=14.879 ms
--- user-att-162-198-200-0.e7817.dscx.akamaiedge.web ping statistics ---
1 packets transmitted, 1 packets acquired, 0.0% packet loss
round-trip min/avg/max/stddev = 14.879/14.879/14.879/0.000 ms
scott@Mac-mini-x86 ~ $ ping6 -c 1 www.ibm.com
PING6(56=40+8+8 bytes) 2600:1700:6b0:e60:b9a0:4f76:4b85:6a1d --> 2600:1407:7400:d87::1e89
16 bytes from 2600:1407:7400:d87::1e89, icmp_seq=0 hlim=50 time=32.135 ms
--- user-att-162-198-200-0.e7817.dscx.akamaiedge.web ping6 statistics ---
1 packets transmitted, 1 packets acquired, 0.0% packet loss
round-trip min/avg/max/std-dev = 32.135/32.135/32.135/0.000 ms
scott@Mac-mini-x86 ~ $ ssh $vm
<---*snip a dozen traces of login banner omitted*--->
livecd ~ # ping -c 1 23.0.23.183
PING 23.0.23.183 (23.0.23.183) 56(84) bytes of knowledge.
64 bytes from 23.0.23.183: icmp_seq=1 ttl=53 time=21.6 ms
--- 23.0.23.183 ping statistics ---
1 packets transmitted, 1 acquired, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 21.590/21.590/21.590/0.000 ms
livecd ~ # ping6 -c 1 2600:1407:7400:d87::1e89
PING 2600:1407:7400:d87::1e89(2600:1407:7400:d87::1e89) 56 information bytes
--- 2600:1407:7400:d87::1e89 ping statistics ---
1 packets transmitted, 0 acquired, 100% packet loss, time 0ms
livecd ~ # ping -c 1 www.ibm.com
PING www.ibm.com(g2600-1407-7400-0d94-0000-0000-0000-1e89.deploy.static.akamaitechnologies.com (2600:1407:7400:d94::1e89)) 56 information bytes
--- www.ibm.com ping statistics ---
1 packets transmitted, 0 acquired, 100% packet loss, time 0ms
livecd ~ # cat /and so forth/resolv.conf
# Generated by dhcpcd from enp2s1.dhcp, enp2s1.dhcp6, enp2s1.ra
# /and so forth/resolv.conf.head can substitute this line
area attlocal.web
nameserver 192.168.1.254
nameserver 2600:1700:6b0:e60::1
# /and so forth/resolv.conf.tail can substitute this line
Very first thing to notice is that though this instance was run on an set up picture in a contemporary vm, primarily the identical factor occurs in a Home windows VM or a macOS VM — ipv6 would not work!
Again to the story: I ping www.ibm.com, each with ping (ipv4) and ping6 (ipv6) whereas on the host — works nice, and rapidly. Within the visitor vm, the ping nonetheless works, and rapidly, however the ping6 simply instances out. Why did I exploit specific addresses on the visitor? The final experiment exhibits that on the visitor, www.ibm.com will resolve to an ipv6 tackle (DNS lookup working, proper?) however then cannot be reached 🧐.
Notice additionally that scutil (on the Mac) or cat /and so forth/resolv.conf (on the visitor) each present that very same addresses, ipv4 and ipv6, for dsldevice.attlocal.web, my router.
Maybe there’s some configuration magic within the .vmx file or one thing comparable that would make ipv6 simply work, or if not, make ipv6 fail in a means that issues do not get confused, and simply use ipv4 just like the Earlier than Instances.
