Windows 11 ARM Network Issue

**Describe the issue**
I encountered a rather peculiar issue while using UTM.

My device has two network cards. One is connected to a wired network (en6), but this wired network is an internal network and cannot connect to the Internet. The other is a wireless network card (en1), which connects to a wireless network that has Internet access.

```
en6: flags=8863 mtu 1500
options=6464
ether 20:7b:d5:1a:1d:d3
inet6 fe80::1c5c:d3ae:afb2:fb0f%en6 prefixlen 64 secured scopeid 0xb
inet 192.168.126.10 netmask 0xffffff00 broadcast 192.168.126.255
nd6 options=201
media: autoselect (100baseTX )
status: active
en1: flags=8863 mtu 1500
options=6460
ether 5c:1b:f4:de:1a:d5
inet6 fe80::43e:81ab:ae21:b97%en1 prefixlen 64 secured scopeid 0xe
inet 192.168.8.5 netmask 0xffffff00 broadcast 192.168.8.255
nd6 options=201
media: autoselect
status: active
```

Then I installed Windows 11 ARM on UTM and used the shared network with a virtio-net-pci emulated network card, which created a new network card, bridge100, on macOS.

```
bridge100: flags=8a63 mtu 1500
options=3
ether 5e:1b:f4:1e:ca:64
inet 192.168.64.1 netmask 0xffffff00 broadcast 192.168.64.255
inet6 fe80::5c1b:f4ff:fe1e:ca64%bridge100 prefixlen 64 optimistic scopeid 0x16
inet6 fd1f:409e:2a35:baa7:1c16:6b66:a023:55d prefixlen 64 tentative autoconf secured
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
ifmaxaddr 0 port 21 priority 0 path cost 0
nd6 options=201
media: autoselect
status: active
```

In my Windows 11 ARM, the network query results are as follows:
```
Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : fd1f:409e:2a35:baa7:295e:4cf1:edb0:4e45
Temporary IPv6 Address. . . . . . : fd1f:409e:2a35:baa7:a9d2:731f:20f2:a02c
Link-local IPv6 Address . . . . . : fe80::295e:4cf1:edb0:4e45%14
IPv4 Address. . . . . . . . . . . : 192.168.64.8
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.64.1
```

Now, if I ping Google from Windows 11 ARM, it works. However, if I ping the address of the en6 network card, it doesn't work. I specifically want to use this internal network port en6.

If I change the network mode to Bridged (Advanced) and bridge the en6 interface, an even stranger phenomenon occurs. In my Windows 11 ARM, the network query results are as follows:
```
Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::295e:4cf1:edb0:4e45%14
Autoconfigured IPv4 Address . . . : 169.254.78.69
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
```
And now, I cannot ping either the internal network or the external network.

**Configuration**
* UTM Version: 4.5.3(99)
* macOS Version: macOS Sonama Version 14.4(23E214)
* Mac Chip (Intel, M1, ...): Apple M2

**Crash log**
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to `Crash Reports`, and find the latest entry for either UTM, QEMU, QEMUHelper, or qemu-\*. Right click and choose `Reveal in Finder`. Attach the report here.

**Debug log**
attached.