<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>Hello everyone,<br></div>
<div> </div>
<div>I have followed this guide to enable my Windows 10 guest to reach my Arch Linux host: <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/App_Macvtap.html">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/App_Macvtap.html</a><br></div>
<div> </div>
<div>My VM now has 2 NICs: <br></div>
<div>- macvtap (VEPA)<br></div>
<div>- virtual network 'isolated'<br></div>
<div> </div>
<div>I have statically assigned the IP 192.168.254.2 to my guest. The host's IP is 192.168.254.1. The interface it is using on the host is <b>virbr1</b>.<br></div>
<div> </div>
<div>I am able to ping the host from the guest and vice versa, so the network connectivity seems to be generally working. To control my VM I'd like to use Synergy which I have already set up and tested successfully once with the VM as the Server, but never since. When I try to connect the Synergy client from the host to a server running on the guest, I get the error <i>"failed to connect to server: address not found for: 192.168.254.2"</i>.<br></div>
<div> </div>
<div>This is the result of nmap:<br></div>
<div>[root@thearch ~]# nmap 192.168.254.0/30<br></div>
<div> </div>
<div>Starting Nmap 7.12 ( <a href="https://nmap.org">https://nmap.org</a> ) at 2016-05-14 17:14 CEST<br></div>
<div>Nmap scan report for 192.168.254.2<br></div>
<div>Host is up (0.0010s latency).<br></div>
<div>Not shown: 995 filtered ports<br></div>
<div>PORT STATE SERVICE<br></div>
<div>135/tcp open msrpc<br></div>
<div>139/tcp open netbios-ssn<br></div>
<div>445/tcp open microsoft-ds<br></div>
<div>5357/tcp open wsdapi<br></div>
<div>24800/tcp open unknown<br></div>
<div>MAC Address: 52:54:00:96:11:A9 (QEMU virtual NIC)<br></div>
<div> </div>
<div>Nmap scan report for 192.168.254.1<br></div>
<div>Host is up (0.0000040s latency).<br></div>
<div>Not shown: 999 closed ports<br></div>
<div>PORT STATE SERVICE<br></div>
<div>53/tcp open domain<br></div>
<div> </div>
<div>Nmap done: 4 IP addresses (2 hosts up) scanned in 5.16 seconds<br></div>
<div> </div>
<div>I also did nmap from a non-root user:<br></div>
<div>[christopher@thearch ~]$ nmap 192.168.254.0/30<br></div>
<div> </div>
<div>Starting Nmap 7.12 ( <a href="https://nmap.org">https://nmap.org</a> ) at 2016-05-14 17:17 CEST<br></div>
<div>Nmap scan report for 192.168.254.1<br></div>
<div>Host is up (0.000073s latency).<br></div>
<div>Not shown: 999 closed ports<br></div>
<div>PORT STATE SERVICE<br></div>
<div>53/tcp open domain<br></div>
<div> </div>
<div>Nmap done: 4 IP addresses (1 host up) scanned in 1.26 seconds<br></div>
<div> </div>
<div>As you can see, the host 192.168.254.2 is only found when running nmap with root, not with my other user. Pinging the guest still works however.<br></div>
<div> </div>
<div>I suspect this is the core of the issue, but I don't know how to solve it. Any suggestions are appreciated.<br></div>
<div> </div>
<div>Thanks,<br></div>
<div>Christopher Mühl</div>
<div> </div>
</body>
</html>