I have created a Hyper-V Virtual Machine running Arch Linux. I want to have two NIC's.

  • The first NIC is an external nic for internet connection.
  • The second NIC should be an internal nic - the reason is that if I change network I want to have a static ip address that works on my laptop regardless of the DHCP settings of the network.

I have created a virtual switch with internal as adapter. On my laptop (Win 10) I have set up as follows:

IP Address:
Gateway: Blank
DNS 1:
DNS 2: Blank

My Virtual Machine (Arch Linux) has:


Ping from HOST to GUEST does not work, GUEST to HOST does not work.

Any help/advice?

  • Running Ubuntu 16.10 does not give any problems :S – Marc Went Oct 31 '16 at 14:43
  • From the Arch Linux machine, are you able to ping the gateway ( at all? – SleepyMan Oct 31 '16 at 15:07
  • Nope, not able to ping from HOST <=!=> GUEST – Marc Went Oct 31 '16 at 18:16

If and are visible interfaces on the same machine (eth0 and eth1 for instance), that won't work

If the are on separate kernel stacks, have a look at each interface using the ip command. Ensure the link is state UP on each interface.

# ip link sho eth1
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:15:17:38:41:ff brd ff:ff:ff:ff:ff:ff

Next, su/sudo to root and run the arping command to/from each IP address (/usr/sbin/arping You will probably need to install the utility. Devices on the same subnet will always reply to this if they are plugged in and there is no problem with physical cabling, hardware. Even if ICMP is dropped on firewall, arping will succeed.

Also, make sure dhcp is disabled for the interface you have configured manually (static). Depending on what craziness your Linux distro is using for configuring the interface, this can be quite a chore for some.

if arping fails, you will need to do some investigation into the pieces between the IP address. Make sure the hypervisor knows the nic should be enabled on the virtual machine and is allowing access to it, virtual switch is configured correctly, etc. etc. Maybe remove some pieces in between and test again.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.