tcpdump was initiated on the host not on guest. (Guest has no issue)
On my main Mac I gave downgraded to Ventura, and same setup is working. While on spare Mac which is running Sequoia issue persists.
I confirm firewall is disabled. Fusion working perfectly on Ventura and Sonoma. I'll capture the packets tomorrow and upload.
Thank you.
Original Message:
Sent: Feb 14, 2025 08:25 AM
From: Rajeswara Reddy Kotla
Subject: Fusion network bridge issue, sequoia
There is only one packet present in the dump and it is ICMP - Destination Unreachable. Can you confirm if the tcpdump command is executed on host or VM?
The host and guest IP mentioned in Reply#16 says host is 192.168.29.100 and guest is 192.168.29.200
But in the pcap its showing 192.168.29.6 and 192.168.29.1. I guess 192.168.29.1 is the gateway IP. What is 192.168.29.6 ?
I think the packets are not routing properly to VM? Can you confirm this? Please initiate a tcpdump in both host and VM before starting ping and share the pcap.
Also since the VM is able to ping from other MAC hosts and if we see, Sonoma to Sequio is the only change made, can you please check any firewall/privacy setting enabled in the host or vm.
Original Message:
Sent: Feb 11, 2025 04:53 AM
From: Snail off
Subject: Fusion network bridge issue, sequoia
I have attached the gzip.
1 thing I noticed, I have a spare Mac on which I installed sequoia and installed VMware, as anticipated I can't ping the guest VM. When I tried from another Mac I can ping/ssh to the guest.
Original Message:
Sent: Feb 10, 2025 05:26 AM
From: Rajeswara Reddy Kotla
Subject: Fusion network bridge issue, sequoia
We don't see any attachment of tcpdump logs. Can you attach if not done.
Original Message:
Sent: Feb 08, 2025 06:51 AM
From: Snail off
Subject: Fusion network bridge issue, sequoia
from inside the vm there is no issue, issue is, connecting from host (Mac OS Sequoia) to guest VM both ping/ssh. I just upgraded from Sanoma to Sequoia and my existing setup stopped working. Same setup was working before the upgrade.
Yes, firewall is disabled.
host IP is 192.168.29.100 and guest is 192.168.29.200
I have attached tcpdump logs. initiated ping from host to VM.
Please let me know if you need any other details.
Original Message:
Sent: Feb 05, 2025 04:25 AM
From: Rajeswara Reddy Kotla
Subject: Fusion network bridge issue, sequoia
@Snail off, can you please share the pcap data for the below cases
1.Initiate the pcap capture in vm (cmd: tcpdump -enni <interface> icmp -w <file>.pcap). Ping from host to guest. We just want to see if icmp packets are reaching vm.
2.Initiate the pcap capture on host. Ping from vm to host.
3.Can you confirm if firewall is enabled
4.confirm your host and guest ip
Thanks
Original Message:
Sent: Feb 03, 2025 04:34 AM
From: Snail off
Subject: Fusion network bridge issue, sequoia
What's the meaning of "remove answer"?
I added same network on Ventura and I don't see "remove answer" line.
Output from Ventura with Adguard running.snehal@Snehals-MacBook-Pro ~ % cat /Library/Preferences/VMware\ Fusion/networkingVERSION=1,0answer VNET_1_DHCP yesanswer VNET_1_DHCP_CFG_HASH 8724CA78D9C8C70716C1BB75A8668271AF4BEA74answer VNET_1_HOSTONLY_NETMASK 255.255.255.0answer VNET_1_HOSTONLY_SUBNET 192.168.33.0answer VNET_1_HOSTONLY_UUID 979D8C92-669E-4586-B8EF-C08CC8BDA40Fanswer VNET_1_VIRTUAL_ADAPTER yesanswer VNET_3_DHCP yesanswer VNET_3_HOSTONLY_NETMASK 255.255.255.0answer VNET_3_HOSTONLY_SUBNET 172.16.182.0answer VNET_3_HOSTONLY_UUID ACA00658-D8E5-4876-9030-73E869A5A1B4answer VNET_3_NAT yesanswer VNET_3_NAT_PARAM_UDP_TIMEOUT 30answer VNET_3_VIRTUAL_ADAPTER yesanswer VNET_8_DHCP yesanswer VNET_8_DHCP_CFG_HASH 6D02E5E93467C13717EF7D1171B9EAE3B8F565F3answer VNET_8_HOSTONLY_NETMASK 255.255.255.0answer VNET_8_HOSTONLY_SUBNET 192.168.212.0answer VNET_8_HOSTONLY_UUID CBEF0C87-B5A5-4AA6-BB6F-059EB54FA9D9answer VNET_8_NAT yesanswer VNET_8_VIRTUAL_ADAPTER yesadd_bridge_mapping en0 2answer VNET_3_DHCP_CFG_HASH F258AF64071B8340501FC9A11FAE7E7238322AF4
Original Message:
Sent: Feb 01, 2025 01:07 PM
From: Technogeezer
Subject: Fusion network bridge issue, sequoia
Very strange indeed.
The networking file is pretty much the same as mine, with the difference that I do not have the remove_answer and additional VNET_3_DHCP_CFG_HASH entry.
Grasping at straws here:
You wouldn't happen to be running any kind of third party networking filter or firewall (such as Little Snitch) are you?
@Prajakta Malla or anyone else from Broadcom - can you give us a hand with this?
------------------------------
- Paul (technogeezer)
Original Message:
Sent: Feb 01, 2025 12:27 AM
From: Snail off
Subject: Fusion network bridge issue, sequoia
Networking file, I have attached vnetlib logs as well.
yes tried traceroute, its not reaching to the gateway as expected.
I noticed sometimes ping/ssh works for minute and then stops working. I did trace route during that moment, it worked.
Yes I have tried both static and DHCP address to VM. Even in router I configured vm's static ip along with mac address.
Regarding router security, I would rule that out as the same settings work on Ventura and Sanoma.
Snehals-MacBook-Pro:VMware Fusion root# cat /Library/Preferences/VMware\ Fusion/networkingVERSION=1,0answer VNET_1_DHCP yesanswer VNET_1_DHCP_CFG_HASH 28EBCAAC6EE2ECB84BBA0005311E74225AE9A0F3answer VNET_1_HOSTONLY_NETMASK 255.255.255.0answer VNET_1_HOSTONLY_SUBNET 172.16.145.0answer VNET_1_HOSTONLY_UUID 86CE327C-E3E1-46B3-B741-A9B8B5615E42answer VNET_1_VIRTUAL_ADAPTER yesanswer VNET_3_DHCP yesanswer VNET_3_DHCP_CFG_HASH A60C119EDBF0C4ABE4FB80C5598FF0C35630B63Banswer VNET_3_HOSTONLY_NETMASK 255.255.255.0answer VNET_3_HOSTONLY_SUBNET 192.168.55.0answer VNET_3_HOSTONLY_UUID BA85FCC8-EA5E-406B-857F-F0A3DB7481F0answer VNET_3_NAT yesanswer VNET_3_NAT_PARAM_UDP_TIMEOUT 30answer VNET_3_VIRTUAL_ADAPTER yesanswer VNET_8_DHCP yesanswer VNET_8_DHCP_CFG_HASH 625AAF45791DB76A906C9F1842680801CE25997Canswer VNET_8_HOSTONLY_NETMASK 255.255.255.0answer VNET_8_HOSTONLY_SUBNET 192.168.72.0answer VNET_8_HOSTONLY_UUID A296DA5A-7BCD-458D-ACEA-A490CF0FA090answer VNET_8_NAT yesanswer VNET_8_VIRTUAL_ADAPTER yesadd_bridge_mapping en0 2remove_answer VNET_3_DHCP_CFG_HASHanswer VNET_3_DHCP_CFG_HASH F3F9D4F528820E7621546C36C2326BA07F8606F8
Original Message:
Sent: Jan 30, 2025 04:26 PM
From: Technogeezer
Subject: Fusion network bridge issue, sequoia
I'm not seeing this behavior with a bridged Wi-Fi network. I can reach a VM attached to that network both locally and from another device on the same Wi-Fi network.
It does look like your virtual network configuration may be slightly different than mine. Can you attach a copy of the /Library/Preferences/VMware Fusion/networking file?
Have you tried assigning a static address to the VM (on the same network as the bridged network)?
On the Mac, have you tried running traceroute 192.168.72.190 ?
What kind of Wi-Fi access point are you using? Is there anything on it that may be restricting port/IP address access (such as found in enterprise-class networking infrastructure)?
------------------------------
- Paul (technogeezer)
Original Message:
Sent: Jan 30, 2025 12:57 PM
From: Snail off
Subject: Fusion network bridge issue, sequoia
yes, correct, its the Wifi's DHCP. The .200 IP was configured earlier. "Bridged networking option" is not working at all no matter what I do. I have Always used bridged networking option using routers DHCP address.
Today as a work around I created a new custom network VMNET3 and it's working so far. I can ssh to the guest from Mac.
Hope it gets fixed in future release. is the same setup working for you? bridged Networking (WI-FI) with router's DHCP address?
Custom Network screenshot.
Original Message:
Sent: Jan 30, 2025 11:14 AM
From: Technogeezer
Subject: Fusion network bridge issue, sequoia
From the screen shot of your VM, its network interface has IP address 192.168.29.190, not .200. Try that IP address and see if you can ping from the Mac.
Are you using DHCP in that VM to get IP addresses? If so, it's the Wi-Fi's DHCP server that's giving you the .190 address, not Fusion.
------------------------------
- Paul (technogeezer)
Original Message:
Sent: Jan 29, 2025 11:30 PM
From: Snail off
Subject: Fusion network bridge issue, sequoia
Hi Paul, is everything working for you? Here is the requested output.
snehal@Snehals-MacBook-Pro ~ % vmrun listHostNetworksTotal host networks: 4INDEX NAME TYPE DHCP SUBNET MASK0 vmnet0 bridged false empty empty 1 vmnet1 hostOnly true 172.16.145.0 255.255.255.0 2 vmnet2 bridged false empty empty 8 vmnet8 nat true 192.168.72.0 255.255.255.0
snehal@Snehals-MacBook-Pro ~ % netstat -rnRouting tablesInternet:Destination Gateway Flags Netif Expiredefault 192.168.29.1 UGScg en0 default link#23 UCSIg bridge100 !default link#25 UCSIg bridge101 !127 127.0.0.1 UCS lo0 127.0.0.1 127.0.0.1 UH lo0 169.254 link#14 UCS en0 !172.16.145/24 link#23 UC bridge100 !172.16.145.255 ff.ff.ff.ff.ff.ff UHLWbI bridge100 !192.168.29 link#14 UCS en0 !192.168.29.1/32 link#14 UCS en0 !192.168.29.1 a8:da:c:c1:bc:cb UHLWIir en0 1183192.168.29.15/32 link#14 UCS en0 !192.168.29.15 6c:7e:67:cc:52:b2 UHLWI lo0 192.168.29.190 link#14 UHRLWI en0 !192.168.29.255 ff:ff:ff:ff:ff:ff UHLWbI en0 !192.168.72 link#25 UC bridge101 !192.168.72.255 ff.ff.ff.ff.ff.ff UHLWbI bridge101 !224.0.0/4 link#14 UmCS en0 !224.0.0.251 1:0:5e:0:0:fb UHmLWI en0 255.255.255.255/32 link#14 UCS en0 !
snehal@Snehals-MacBook-Pro ~ % ifconfig -alo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP> inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 nd6 options=201<PERFORMNUD,DAD>gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280stf0: flags=0<> mtu 1280anpi1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=400<CHANNEL_IO> ether 46:68:1e:28:fd:69 media: none status: inactiveanpi2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=400<CHANNEL_IO> ether 46:68:1e:28:fd:6a media: none status: inactiveanpi0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=400<CHANNEL_IO> ether 46:68:1e:28:fd:68 media: none status: inactiveen4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=400<CHANNEL_IO> ether 46:68:1e:28:fd:48 nd6 options=201<PERFORMNUD,DAD> media: none status: inactiveen5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=400<CHANNEL_IO> ether 46:68:1e:28:fd:49 nd6 options=201<PERFORMNUD,DAD> media: none status: inactiveen6: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=400<CHANNEL_IO> ether 46:68:1e:28:fd:4a nd6 options=201<PERFORMNUD,DAD> media: none status: inactiveen1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=460<TSO4,TSO6,CHANNEL_IO> ether 36:5a:3d:fd:62:00 media: autoselect <full-duplex> status: inactiveen2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=460<TSO4,TSO6,CHANNEL_IO> ether 36:5a:3d:fd:62:04 media: autoselect <full-duplex> status: inactiveen3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=460<TSO4,TSO6,CHANNEL_IO> ether 36:5a:3d:fd:62:08 media: autoselect <full-duplex> status: inactiveap1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM> ether 92:26:c7:84:a1:0a nd6 options=201<PERFORMNUD,DAD> media: autoselect (none) status: inactiveen0: flags=8b63<UP,BROADCAST,SMART,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500 options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM> ether 6c:7e:67:cc:52:b2 inet6 fe80::8d0:9d20:44c5:4650%en0 prefixlen 64 secured scopeid 0xe inet 192.168.29.15 netmask 0xffffff00 broadcast 192.168.29.255 nd6 options=201<PERFORMNUD,DAD> media: autoselect status: activebridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=63<RXCSUM,TXCSUM,TSO4,TSO6> ether 36:5a:3d:fd:62:00 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: en1 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 10 priority 0 path cost 0 member: en2 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 11 priority 0 path cost 0 member: en3 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 12 priority 0 path cost 0 nd6 options=201<PERFORMNUD,DAD> media: <unknown type> status: inactiveawdl0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM> ether d2:72:89:e1:1e:90 inet6 fe80::d072:89ff:fee1:1e90%awdl0 prefixlen 64 scopeid 0x10 nd6 options=201<PERFORMNUD,DAD> media: autoselect status: activellw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=400<CHANNEL_IO> ether d2:72:89:e1:1e:90 inet6 fe80::d072:89ff:fee1:1e90%llw0 prefixlen 64 scopeid 0x11 nd6 options=201<PERFORMNUD,DAD> media: autoselect (none)utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380 inet6 fe80::efaf:3669:b95c:d96f%utun0 prefixlen 64 scopeid 0x12 nd6 options=201<PERFORMNUD,DAD>utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 inet6 fe80::72d9:5d52:a5b9:372a%utun1 prefixlen 64 scopeid 0x13 nd6 options=201<PERFORMNUD,DAD>utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000 inet6 fe80::5fc3:4bbc:85ce:666b%utun2 prefixlen 64 scopeid 0x14 nd6 options=201<PERFORMNUD,DAD>utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000 inet6 fe80::ce81:b1c:bd2c:69e%utun3 prefixlen 64 scopeid 0x15 nd6 options=201<PERFORMNUD,DAD>vmenet0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 ether b2:52:1c:66:32:fb media: autoselect status: activebridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=3<RXCSUM,TXCSUM> ether 6e:7e:67:cc:97:64 inet 172.16.145.1 netmask 0xffffff00 broadcast 172.16.145.255 inet6 fe80::6c7e:67ff:fecc:9764%bridge100 prefixlen 64 scopeid 0x17 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: vmenet0 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 22 priority 0 path cost 0 member: vmenet3 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 27 priority 0 path cost 0 nd6 options=201<PERFORMNUD,DAD> media: autoselect status: activevmenet1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 ether 4a:40:e1:1b:7d:2d media: autoselect status: activebridge101: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=3<RXCSUM,TXCSUM> ether 6e:7e:67:cc:97:65 inet 192.168.72.1 netmask 0xffffff00 broadcast 192.168.72.255 inet6 fe80::6c7e:67ff:fecc:9765%bridge101 prefixlen 64 scopeid 0x19 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: vmenet1 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 24 priority 0 path cost 0 member: vmenet2 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 26 priority 0 path cost 0 nd6 options=201<PERFORMNUD,DAD> media: autoselect status: activevmenet2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 ether ca:cf:a3:60:92:80 media: autoselect status: activevmenet3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 ether 7e:c4:82:dc:15:4f media: autoselect status: activevmenet4: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 ether be:66:15:0c:33:51 media: autoselect status: activebridge102: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=3<RXCSUM,TXCSUM> ether 6e:7e:67:cc:97:66 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: en0 flags=8003<LEARNING,DISCOVER,MACNAT> ifmaxaddr 0 port 14 priority 0 path cost 0 member: vmenet4 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 28 priority 0 path cost 0 media: autoselect status: activeutun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380 inet6 fe80::694d:cabd:f8e6:aaf7%utun4 prefixlen 64 scopeid 0x20 nd6 options=201<PERFORMNUD,DAD>utun5: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380 inet6 fe80::9f1e:23f5:387c:ad51%utun5 prefixlen 64 scopeid 0x21 nd6 options=201<PERFORMNUD,DAD>
Original Message:
Sent: Jan 29, 2025 01:04 PM
From: Technogeezer
Subject: Fusion network bridge issue, sequoia
I have the same version of Ubuntu running in a VM on Sonoma 15.3 on a M1 Mac mini.
Let's get a bit more information from both the Mac and the VM.
On the Mac, run the following in the Terminal:
ifconfig -a
netstat -r
vmrun listHostNetworks
In the VM, run the following in the shell:
ip address
ip route
------------------------------
- Paul (technogeezer)
Original Message:
Sent: Jan 29, 2025 02:21 AM
From: Snail off
Subject: Fusion network bridge issue, sequoia
Hi,
here are the details. Tried all versions of Mac OS sequoia (Clean install of all versions) VMware Fusion version 13.6.2
Wifi network is 192.168.29.0/24
my guest network is all good, able to ping default gateway and able to ping google as well. I'm unable to ping/connect (ssh) from Mac to the guest Ubuntu 24.04.1 LTS.
snehal@Snehals-MacBook-Pro ~ % ping 192.168.29.200 PING 192.168.29.200 (192.168.29.200): 56 data bytesRequest timeout for icmp_seq 0Request timeout for icmp_seq 1Request timeout for icmp_seq 2Request timeout for icmp_seq 3ping: sendto: No route to hostRequest timeout for icmp_seq 4^C--- 192.168.29.200 ping statistics ---6 packets transmitted, 0 packets received, 100.0% packet losssnehal@Snehals-MacBook-Pro ~ % ps -ef | egrep "vmnet-natd|vmnet-dhcpd|vmnet-bridge" | grep -v egrep 0 3595 1 0 12:02PM ?? 0:00.02 /Library/Application Support/VMware/VMware Fusion/Services/Contents/Library/vmnet-bridge 0 3598 1 0 12:02PM ?? 0:00.08 /Library/Application Support/VMware/VMware Fusion/Services/Contents/Library/vmnet-dhcpd -s 6 -cf /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf -lf /var/db/vmware/vmnet-dhcpd-vmnet1.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid vmnet1 0 3603 1 0 12:02PM ?? 0:00.14 /Library/Application Support/VMware/VMware Fusion/Services/Contents/Library/vmnet-natd -s 6 -m /Library/Preferences/VMware Fusion/vmnet8/nat.mac -c /Library/Preferences/VMware Fusion/vmnet8/nat.conf 0 3605 1 0 12:02PM ?? 0:00.06 /Library/Application Support/VMware/VMware Fusion/Services/Contents/Library/vmnet-dhcpd -s 6 -cf /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf -lf /var/db/vmware/vmnet-dhcpd-vmnet8.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8snehal@Snehals-MacBook-Pro ~ %
Original Message:
Sent: Jan 28, 2025 05:06 PM
From: Technogeezer
Subject: Fusion network bridge issue, sequoia
Also when network connectivity fails, see if all the Fusion networking processes are running on the host Mac. When the VM is running In the Terminal use the following command:
ps -ef | egrep "vmnet-natd|vmnet-dhcpd|vmnet-bridge" | grep -v egrep
In a standard virtual network configuration, you should see one vmnet-bridge, one vmnet-natd and two vmnet-dhcpd processes. (You may see more vmnet-natd or vmnet-dhcpd processes if you've configured additional custom virtual networks)
------------------------------
- Paul (technogeezer)
Original Message:
Sent: Jan 28, 2025 04:41 PM
From: Technogeezer
Subject: Fusion network bridge issue, sequoia
What Fusion version and what update to Sequoia are you using. I don't see this behavior on Sequoia 15.3 and Fusion 13.6.2.
What is the operating system running in the VM?
The first thing I would check is your macOS configuration for the Wi-Fi network you're using (System Settings > Wi-Fi). What is the Private Wi-Fi Address setting for the Wi-FI network you're connected to?
The next thing I'd suggest is to check the IP address assigned to the VM -- espeically if you're setting the IP address using DHCP. Just to make sure that the IP address is what you think it should be.
------------------------------
- Paul (technogeezer)
Original Message:
Sent: Jan 27, 2025 04:05 AM
From: Snail off
Subject: Fusion network bridge issue, sequoia
Hi,
I'm using latest VMware Fusion with Mac OS sequoia on MacBook Pro M2. After upgrading or doing clean install of sequoia I'm unable to connect to guest VM.
I always use bridge networking with Wi-FI option selected so that I can ssh to the guest network. After upgrade and even clean install I'm unable to ssh to the guest. I see guest is perfectly fine able to connect to internet without any packet drop.
But from Mac I'm unable to connect. sometimes it works just for 5 min and then disconnects.
After downgrading to macOS Sanoma everything is perfect. Is the fix coming for sequoia?
------------------------------
Snehal
------------------------------