topic Re: macOS bigsur virtual machine version 12.2.0 doesn't respond to remote ping when configured to NA in VMware Fusion Discussions

macOS bigsur virtual machine version 12.2.0 doesn't respond to remote ping when configured to NAT.

zohar811 — Tue, 26 Oct 2021 20:04:51 GMT

Hi,

I've upgraded my fusion to version 12.2.0, and my VM that run macOS bigSur is now configured to hardware version is 19 under compatibility. my physical machine also runs the same OS version.

However, since the upgrade I can only get response to ping to my physical machine (ip 192.168.214.1) with the bridge interface below, but when I try ips outside the subnet it doesn't get any response (i.e. ping 8.8.8.8) although I've checked that it's working on wiki mode.

Any idea if it's a known issue and how can I debug it ?

bridge101: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=3<RXCSUM,TXCSUM>
ether 8a:66:5a:c1:37:65
inet 192.168.214.1 netmask 0xffffff00 broadcast 192.168.214.255
inet6 fe80::cd2:364e:523b:97b1%bridge101 prefixlen 64 secured scopeid 0x14
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: en9 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 19 priority 0 path cost 0
member: en10 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 21 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active

Re: macOS bigsur virtual machine version 12.2.0 doesn't respond to remote ping when configured to NA

simonanthony — Thu, 04 Nov 2021 10:56:54 GMT

I have the same problem. VMs can no longer see the external network (access the Internet) with NAT. I tried also testing on a further VM at hardware version 18 before upgrading to hardware version 19 with the same result.

Re: macOS bigsur virtual machine version 12.2.0 doesn't respond to remote ping when configured to NA

simonanthony — Thu, 11 Nov 2021 16:34:45 GMT

Actually NAT does work. The gateway has changed from ".1" to ".2". Which would have passed un-noticed if Fusion were still able to provide DHCP on Big-Sur/Monterey,

However, can no longer route between private networks as was possible with a previously working configuration.