From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David S. Ahern" Subject: Re: Networkconfiguration with KVM Date: Mon, 05 Apr 2010 12:34:51 -0600 Message-ID: <4BBA2D4B.2030303@cisco.com> 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 Return-path: Received: from sj-iport-6.cisco.com ([171.71.176.117]:31429 "EHLO sj-iport-6.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755815Ab0DESex (ORCPT ); Mon, 5 Apr 2010 14:34:53 -0400 In-Reply-To: <201004052004.34244.kvm@dmj.nu> Sender: kvm-owner@vger.kernel.org List-ID: On 04/05/2010 12:04 PM, Dan Johansson wrote: > Must I specify an IP for the br-eth3 interface? You do not have to specify an IP address for the bridge. In my case: mainbr0 Link encap:Ethernet HWaddr UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7328933 errors:0 dropped:0 overruns:0 frame:0 TX packets:6992 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:481076877 (458.7 MiB) TX bytes:629184 (614.4 KiB) tap0 Link encap:Ethernet HWaddr UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:139390 errors:0 dropped:0 overruns:0 frame:0 TX packets:7460821 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:13554808 (12.9 MiB) TX bytes:601113602 (573.2 MiB) # brctl show bridge name bridge id STP enabled interfaces mainbr0 8000. no tap0 eth0 eth0 is the interface connected to the physical LAN. mainbr0 ties the VM's tap to eth0. David > > Regards,