I would like to tackle some networking issues/questions I didn’t really pay attention to until now (thus I don’t know if the below described behavior is recent or has always been this way on Whonix-Host).
On installed Whonix-Host in KVM there is a (expected) conflict between the host (i.e. the physical machine) and the guest (i.e. the KVM Whonix-Host VM) virtual virbr0 NAT interfaces as both by default use 192.168.122.0/24.
Problem: I cannot bring up eth0 on installed KVM Whonix-Host even after disabling virbr0:
user@host:~$ sudo ifup eth0
No DHCP client software found!
ifup: failed to bring eth0
Is it related to dhcpcanon which has its own syntax? (btw I still don’t understand why we insist on using dhcpcanon instead of network-manager for DHCP).
Then I noticed that eth0 is defined in /etc/network/interfaces.d/30-kicksecure
auto eth0
iface eth0 inet dhcp
This raises a (maybe very naive and stupid) question:
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?