From: Dan Johansson <kvm@dmj.nu>
To: kvm@vger.kernel.org
Subject: Re: Networkconfiguration with KVM
Date: Mon, 5 Apr 2010 18:25:14 +0200 [thread overview]
Message-ID: <201004051825.14995.kvm@dmj.nu> (raw)
In-Reply-To: <4BBA024A.7060504@mgpi.de>
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, <http://www.dmj.nu>
***************************************************
This message is printed on 100% recycled electrons!
***************************************************
next prev parent reply other threads:[~2010-04-05 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 12:17 Networkconfiguration with KVM Dan Johansson
2010-04-04 13:00 ` sudhir kumar
2010-04-04 18:02 ` Dan Johansson
2010-04-04 20:23 ` Held Bernhard
2010-04-05 10:09 ` Dan Johansson
[not found] ` <z2sbb653c6e1004050434g209dcc0cmc330c2e391cd68d4@mail.gmail.com>
2010-04-05 14:35 ` Dan Johansson
2010-04-05 16:00 ` David Mair
[not found] ` <4BBA024A.7060504@mgpi.de>
2010-04-05 16:25 ` Dan Johansson [this message]
[not found] ` <4BBA2281.906@mgpi.de>
2010-04-05 18:04 ` Dan Johansson
2010-04-05 18:34 ` David S. Ahern
2010-04-05 20:04 ` Held Bernhard
2010-04-11 15:41 ` Dan Johansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201004051825.14995.kvm@dmj.nu \
--to=kvm@dmj.nu \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.