From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm problem: bonding network interface breaks dhcp Date: Wed, 04 Nov 2009 13:09:08 +0200 Message-ID: <4AF160D4.7010109@redhat.com> References: <4AF0502C.5010304@aixigo.de> <4AF1443D.8020109@redhat.com> <4AF15F41.9050506@aixigo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Harald Dunkel Return-path: Received: from mx1.redhat.com ([209.132.183.28]:32911 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755167AbZKDLJJ (ORCPT ); Wed, 4 Nov 2009 06:09:09 -0500 In-Reply-To: <4AF15F41.9050506@aixigo.de> Sender: kvm-owner@vger.kernel.org List-ID: On 11/04/2009 01:02 PM, Harald Dunkel wrote: > Avi Kivity wrote: > >> Can you tcpdump on bond0, br0, vnet0, and the guest's interface to see >> where the packet is lost? >> >> > Sure. Using the tcpdump command line: > > tcpdump -i br0 -w /var/tmp/tcpdump.br0 ether host 00:16:36:2f:f1:d2 > > (similar for other interfaces) I can see the DHCPOFFER coming > from my dhcp server on bond0: > > 11:00:08.237350 00:15:17:91:3f:59> 00:16:36:2f:f1:d2, ethertype IPv4 (0x0800), length 364: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 350) > 172.19.96.124.67> 172.19.97.250.68: BOOTP/DHCP, Reply, length 322, xid 0x78fb274e, secs 3, Flags [none] > Your-IP 172.19.97.250 > Client-Ethernet-Address 00:16:36:2f:f1:d2 [|bootp] > > It is also visible on br0: > > 11:00:08.237350 00:15:17:91:3f:59> 00:16:36:2f:f1:d2, ethertype IPv4 (0x0800), length 364: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 350) > 172.19.96.124.67> 172.19.97.250.68: BOOTP/DHCP, Reply, length 322, xid 0x78fb274e, secs 3, Flags [none] > Your-IP 172.19.97.250 > Client-Ethernet-Address 00:16:36:2f:f1:d2 [|bootp] > > > But it is not visible on vnet0, and of course not on the > guest. All I see there are the DHCPDISCOVER calls sent by > the guest, and some IPv6 traffic: > > So, it looks like a bridging problem. Can you send this the bridge maintainers (Stephen Hemminger , bridge@lists.linux-foundation.org)? -- error compiling committee.c: too many arguments to function