Could someone explain what is the eth0 interface and how it is created inside MobyLinuxVM (Hyper v)?
I’m takling about this:
docker run -it --rm --privileged --pid host d4w/nsenter /bin/sh
eth0 Link encap:Ethernet HWaddr C0:FF:EE:C0:FF:EE
inet addr:192.168.65.2 Bcast:192.168.65.7 Mask:255.255.255.248
hvint0 Link encap:Ethernet HWaddr 00:15:5D:00:50:05
inet addr:10.0.75.2 Bcast:0.0.0.0 Mask:255.255.255.0
I understand what hvint0 is.
Who and why creates eth0?
I too am searching for this answer. Also, what does the use for the hvint- interface?
@rockoutwithyourclock hvint interface connects guest OS to Hyper-V switch to communicate with host OS (Windows 10), data flows between hyper-v virtual machines (aka docker swarms) goes through Hyper-V switch.
I am also confused. In fact, I see even I disconnected the NIC card of the MobyLinuxVM from hyper-V, and then go into MobyLinuxVM, I can still ping external IP like “google.com” successfully. Seems like the packet send out from eth0. By I do not understand why.