So I tried this, because all my machine run Linux only (Gentoo/arch), I have always a Linux notebook with me and I had no spare notebook in arms reach to install Windows.
Disclaimer: Listen to Power6, x119 and IMAY2023 - if you are not sure about your skills or lack experience: get a spare laptop with Windows.
That out of the way, here's what I tried and discovered…
Running win11 is absolutely no problem for any half decent device nowadays and the hardware support for it is pretty standard.
With proper configuration the risk of sudden suspending or resource exhaustion is fairly minimal.
In this case I ran a virtual win11 on a laptop. I assigned the VM 4 cores and 8GiB RAM with KVM/QEMU via libvirt/virt-manager.
Just keep an eye on power consumption when running VMs on a laptop, and have a power supply or compatible power bank on hand.
Try A: Network via USB redirection
At first, I tried just plugging in a USB Ethernet adapter and just redirect the whole USB device to the VM. Thinking that it will work best when Windows has full control over the USB device and thus the network interface. This worked fine for everything (connecting my normal network/internet etc.), but somehow not for OrBit. It just said it found the car, but then got a timeout (Windows Firewall rules were in place and the firewall even was disabled). I could see the Vehicle Announcements in Wireshark, but no successful connection has been made (no TCP connections or Routing activation requests seen though). I tried that with two different adapters with no success.
Try B: Network via NAT/Bridging
Next I set up the network card on Linux.
Tip for NetworkManager Users: If NetworkManager keeps reconnecting due to no DHCP response, set the IPv4 method to "link-local" in the config to maintain the connection (or use something else like systemd-networkd etc.).
Try B.1: NAT mode
Then I tried the NAT mode (just because it was mentioned here). It did not work for me (and it did not surprise me, because it would set up a segmented network (Linux bridge with DHCP server and iptables rules to masquerade)). I also never checked if link local addresses are NATed and multicast is relayed in NAT mode, but that could be a problem. Also, I'm always a fan of avoiding NAT if it isn't needed anyway. But hey it was worth a try - I haven't looked further into how the connection is established and what exactly could be the issue here.
Try B.2: Bridging
Since host-to-guest communication wasn’t necessary, I opted for macvtap with the USB network interface. This approach worked flawlessly, allowing OrBit to connect without issues instantly.
Although macvtap works I may set up a traditional Linux bridge in the future to compare, I expect it would work similarly well.
I did (so far) do 2 programming runs (including enabled ACC/PA, Adaptive Headlights etc.) with zero problems.
For now, I am super happy with this setup.
EDIT:
Traditional linux bridge, set up with systemd-networkd with bridging in libvirt works flawless as well.
Disclaimer: Listen to Power6, x119 and IMAY2023 - if you are not sure about your skills or lack experience: get a spare laptop with Windows.
That out of the way, here's what I tried and discovered…
Running win11 is absolutely no problem for any half decent device nowadays and the hardware support for it is pretty standard.
With proper configuration the risk of sudden suspending or resource exhaustion is fairly minimal.
In this case I ran a virtual win11 on a laptop. I assigned the VM 4 cores and 8GiB RAM with KVM/QEMU via libvirt/virt-manager.
Just keep an eye on power consumption when running VMs on a laptop, and have a power supply or compatible power bank on hand.
Try A: Network via USB redirection
At first, I tried just plugging in a USB Ethernet adapter and just redirect the whole USB device to the VM. Thinking that it will work best when Windows has full control over the USB device and thus the network interface. This worked fine for everything (connecting my normal network/internet etc.), but somehow not for OrBit. It just said it found the car, but then got a timeout (Windows Firewall rules were in place and the firewall even was disabled). I could see the Vehicle Announcements in Wireshark, but no successful connection has been made (no TCP connections or Routing activation requests seen though). I tried that with two different adapters with no success.
Try B: Network via NAT/Bridging
Next I set up the network card on Linux.
Tip for NetworkManager Users: If NetworkManager keeps reconnecting due to no DHCP response, set the IPv4 method to "link-local" in the config to maintain the connection (or use something else like systemd-networkd etc.).
Try B.1: NAT mode
Then I tried the NAT mode (just because it was mentioned here). It did not work for me (and it did not surprise me, because it would set up a segmented network (Linux bridge with DHCP server and iptables rules to masquerade)). I also never checked if link local addresses are NATed and multicast is relayed in NAT mode, but that could be a problem. Also, I'm always a fan of avoiding NAT if it isn't needed anyway. But hey it was worth a try - I haven't looked further into how the connection is established and what exactly could be the issue here.
Try B.2: Bridging
Since host-to-guest communication wasn’t necessary, I opted for macvtap with the USB network interface. This approach worked flawlessly, allowing OrBit to connect without issues instantly.
Although macvtap works I may set up a traditional Linux bridge in the future to compare, I expect it would work similarly well.
I did (so far) do 2 programming runs (including enabled ACC/PA, Adaptive Headlights etc.) with zero problems.
For now, I am super happy with this setup.
EDIT:
Traditional linux bridge, set up with systemd-networkd with bridging in libvirt works flawless as well.