From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Johansson Subject: Re: Networkconfiguration with KVM Date: Mon, 5 Apr 2010 18:25:14 +0200 Message-ID: <201004051825.14995.kvm@dmj.nu> References: <201004041417.41918.kvm@dmj.nu> <201004051635.44908.kvm@dmj.nu> <4BBA024A.7060504@mgpi.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from mail18.bluewin.ch ([195.186.19.64]:18658 "EHLO mail18.bluewin.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755173Ab0DEQZU (ORCPT ); Mon, 5 Apr 2010 12:25:20 -0400 In-Reply-To: <4BBA024A.7060504@mgpi.de> Sender: kvm-owner@vger.kernel.org List-ID: On Monday 05 April 2010 17.31:22 Held Bernhard wrote: > Hi Dan! > > > But Still I get the following: > > From the Host to the VM: > > $ ssh root@192.168.4.4 > > ssh: connect to host 192.168.4.4 port 22: Connection refused > > > > And from the VM to the Host: > > # ssh root@192.168.4.1 > > ssh: connect to host 192.168.4.1 port 22: Connection refused > > > > Any more suggestions? > > qtap1 and eth1 on the guest show rx- and tx-packets, this looks not that > bad. > > "Connection refused" smells like a closed or firewalled port > (hosts.allow / hosts.deny?). If there's no network at all (and no arp > resolution) ssh would print "no route to host". > > Please make sure that you remove all rules from iptables on both the > host and the guest. Then start pinging: > host -> host > host -> guest > guest -> guest > guest -> host > > If I have to debug network problems I always run `tcpdump`. This way I > can quickly isolate the problem (`tcpdump -i eth1`, `tcpdump -i qtap1`). First of all - I appreciate you help! Here are the results of my tests: host->host: No traffic on eth1, qtap1 or br-eth1 host->guest: No traffic on eth1, qtap1 or br-eth1 guest->guest: No traffic on eth1, qtap1 or br-eth1 guest->host: No traffic on eth1, ECHO-request & Host unreachable on qtap1 and br-eth1 18:05:22.597808 IP 192.168.4.4 > 192.168.4.1: ICMP echo request, id 47120, seq 1, length 64 18:05:22.597935 IP 192.168.4.1 > 192.168.4.4: ICMP host 192.168.4.1 unreachable, length 92 Thanks to you and this information I reviewed my iptables (again) and found an old entry for the 192.168.4.0/24 subnet on the Host hidden within a startup- script. I was probably using that subnet for some other tests some years ago and did not clean out everything afterwards. Now I just have to get the other interfaces in the VM working (and putting it all in some startup-script). Once again thanks for your help!!! Regards, -- Dan Johansson, *************************************************** This message is printed on 100% recycled electrons! ***************************************************