I also had a similar issue. “Host” networing was functional (in
VirtualBox) but couldn’t start gateway due to eth0 already being in use.
onion_knight via Whonix Forum:
Is it related to
dhcpcanonwhich has its own syntax? (btw I still don’t understand why we insist on usingdhcpcanoninstead ofnetwork-managerfor DHCP).
dhcpcanon might not even be starting due to upstream bugs. Linked in the
dhcpcanon discussion forum. network-manager currently does DHCP.
Why do we need to define the default Ethernet interface on Whonix-Host (and using the old naming system instead of new predictable ones)? Isn’t is supposed to be automatically taken care of by NetworkManager?
Good question. I don’t remember. Notes
Disable Predictable Network Interface Names as these are problematic.
Whonix 14.0.0.0.7 developers-only - #4 by Patrick
Disabling them as per
zless /usr/share/doc/udev/README.Debian.gz
Need to rewrap my head around it. Maybe these weren’t stable among
different virtualizers, vbox, kvm, qubes. Can be re-considered.