macOS guest networking returning DHCP failure

[Intensity]

Describe the issue

While running a macOS guest, I continue to see a DHCP "failure" (169.254.0.0/16) for the guest's IP address assignment. I get the same result from different macOS (Apple Silicon) WiFi access points. In the past I've had issues mainly when running a VPN on the host or when using an 802.1x network. However, now I'm universally getting this DHCP failure in every known scenario, without any let-up.

To not have networking in the macOS guest creates lots of limitations.

Presumably this is reproducible. However in addition to this being a bug report, I'll suggest some remedies which, if implemented, would enhance networking options.

If running a VPN (Cisco IPSec for example) on the macOS host causes a known issue with guest networking, I'll suggest lifting this limitation or finding a viable and seamless workaround. Having a VPN running on the host can enhance privacy. However if the guest OS truly wants to increase its isolation level network-wise, it can run a VPN within this VM and thus alter the egress point.

If a fundamental 802.1x access point causes issues with guest network access, then I'll suggest lifting these limitations. Note that in my case, the WiFi AP is not 802.1x and I'm no longer running a VPN when I've been trying to get UTM to support macOS networking for the guest.

Perhaps an alternative might be a "user mode" networking path (like 10.0.2.15 in the guest), but support for this may be subject to Apple's current virtualisation support for networking features. However, feature requests could be suggested to Apple for future refinement.

Another enhancement might involve enabling more advanced bridges, including bridging to a dummy interface or connecting a VM's network device to a virtual switch. At the moment, bridging is very limited. Perhaps "ifconfig feth" fake ethernet type may be of assistance. My best known workaround is to attach a USB Ethernet device (connected to nothing), but that's limiting.

With the underlying problem fixed, and some other fallback networking option considered (from the above list, or in general), this should increase the chances that the (macOS) guest will have networking. I'll have to say that it's certainly worked before. However I continually get DHCP failure (169.254.0.0/16) assignments without an apparent resolution.

Configuration

• UTM Version: 4.5.3
• macOS Version: 14.5 Sonoma
• Mac Chip (Intel, M1, ...): Apple Silicon

Crash log
N/A

Debug log
macOS-on-macOS VM / not applicable (as in, I presume this to be easily reproducible)

Upload VM
Presumed to be highly reproducible.