On Monday 05 April 2010 19.48:49 Bernhard Held wrote: > Am 05.04.2010 17:31, schrieb Held Bernhard: > > Hi Dan! > > > >> But Still I get the following: > >> From the Host to the VM: > >> $ ssh root@xxxxxxxxxxx > >> ssh: connect to host 192.168.4.4 port 22: Connection refused > >> > >> And from the VM to the Host: > >> # ssh root@xxxxxxxxxxx > >> 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`). > > > > Regards, > > Bernhard > > Just another idea: did you enable routing? > > echo 1 > /proc/sys/net/ipv4/ip_forward Hi Bernhard, That was already done. As per my last mail the host<-->guest communication now works. What I am now trying to get to run is the communication between the VM and a network where the host-server has "no access" (i.e. no IP). This should be done over the host-eth3 interface and I have set up the br-eth3 and qtap3 the same way as with the eth1/br-eth1/qtap1 with one difference - the br-eth3 interface is setup without an IP. When doing traffic from the VM to the network I can see traffic on the qtap3 and br-eth3 interface but none on the eth3. Must I specify an IP for the br-eth3 interface? Regards, -- Dan Johansson, <http://www.dmj.nu> *************************************************** This message is printed on 100% recycled electrons! *************************************************** -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
