Question VM can't communicate with host

Apr 8, 2020
Hi, I run a Debian (kali) VM in Hyper-V on a Windows 10 host. I've been using it with no issues for several months; the other day I noticed that DHCP had assigned a new IP to the system on the LAN and I wished to revert it to what it had been before. I did this in the router IP reservation table and on the Linux system, and that broke my connection. I was able to fix the internet access by specifying gateway and subnet mask which I didn't realize had to be configured when using a static IP, however I was not able to ping the host PC over LAN. This is important for me to do as I connect to the machine through VNC (the Hyper-V interface kind of sucks for graphical Linux systems) as well as SSH, etc. from the host OS while it runs as a background service.

I flushed the entire config for the interface and did it from scratch so it now looks like this:

lumin@ry:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# Virtual Ethernet Connection
auto eth0
iface eth0 inet static

lumin@ry:~$ sudo ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet  netmask  broadcast
        inet6 fe80::2022:22ff:fe22:2222  prefixlen 64  scopeid 0x20<link>
        ether 22:22:22:22:22:22  txqueuelen 1000  (Ethernet)
        RX packets 4218  bytes 1257569 (1.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1253  bytes 149632 (146.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet  netmask
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1295  bytes 745197 (727.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1295  bytes 745197 (727.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Traceroutes in either direction don't reveal anything, the system just responds to itself that the destination host is unreachable. The box is able to communicate with the gateway (and Internet), as well as various other hosts on the LAN, but not the host.

Anybody have any idea what the issue could be? I didn't change anything else in the virtual machine/switch settings, only the ip config of the system itself, and reserved the IP for that MAC address in the router settings.

Any input is much appreciated!!! Hope everyone is well in these uncertain times
Last edited: