[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091112145529.303c2659@nehalam>
Date: Thu, 12 Nov 2009 14:55:29 -0800
From: Stephen Hemminger <shemminger@...ux-foundation.org>
To: harald.dunkel@...nline.de
Cc: Andrew Morton <akpm@...ux-foundation.org>,
bridge@...ts.linux-foundation.org,
bugzilla-daemon@...zilla.kernel.org,
bugme-daemon@...zilla.kernel.org, netdev@...r.kernel.org
Subject: Re: [Bugme-new] [Bug 14586] New: bridge on bonding interface: DHCP
replies don't get through
>
> I would like to run a bridge for kvm on a bonding interface (4 * 1Gbit, Intel
> e1000e). Problem: The DHCPDISCOVER packets sent by the guest show up on my dhcp
> server as expected, but the DHCPOFFER sent as a reply doesn't reach the guest
> behind the bridge.
>
> Using tcpdump on host and guest I can see the DHCPOFFER on the bond0 and br0
> interface, but it never shows up on vnet0 or on the guest's eth0.
>
> If I drop the bonding interface and use the host's eth2 for the bridge instead,
> then there is no such problem.
>
> Kernel on host and guest is 2.6.31.5. Attached you can find more information
> about my setup.
>
What is the configuration?
# brctl showstp virbr0
# brctl showmacs virbr0
Is dhclient being run on the bridge interface?
# cat /proc/net/ptype
# cat /proc/net/bonding/bond0
How is bond and bridge configured? Are bonding bridges (wrong)
or bridging bonded interfaces?
Are all links up?
Since this is the initial packet it will have to be flood forwarded by
the bridge, is there any iptables/netfilter rule that might be blocking
packets?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists