From mboxrd@z Thu Jan  1 00:00:00 1970
From: Held Bernhard <bheld@mgpi.de>
Subject: Re: Networkconfiguration with KVM
Date: Mon, 05 Apr 2010 22:04:17 +0200
Message-ID: <4BBA4241.4020203@mgpi.de>
References: <201004041417.41918.kvm@dmj.nu> <4BBA024A.7060504@mgpi.de> <4BBA2281.906@mgpi.de> <201004052004.34244.kvm@dmj.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Dan Johansson <kvm@dmj.nu>
Return-path: <kvm-owner@vger.kernel.org>
Received: from smtp.mgpi.de ([212.202.249.42]:48692 "EHLO smtp.mgpi.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1756069Ab0DEUEV (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 5 Apr 2010 16:04:21 -0400
In-Reply-To: <201004052004.34244.kvm@dmj.nu>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi Dan!

> 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?
No, an IP is not required. Just activate br-eth3 and don't forget to add
a route:

ifconfig br-eth3 up 0.0.0.0
route add 192.168.3.0 netmask 255.255.255.0 eth3

Bernhard