From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>,
bridge@lists.linux-foundation.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
harald.dunkel@t-online.de
Subject: Re: [Bugme-new] [Bug 14586] New: bridge on bonding interface: DHCP replies don't get through
Date: Thu, 12 Nov 2009 14:39:13 -0800 [thread overview]
Message-ID: <20091112143913.3d89e4f4.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-14586-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Wed, 11 Nov 2009 14:28:00 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14586
>
> Summary: bridge on bonding interface: DHCP replies don't get
> through
> Product: Networking
> Version: 2.5
> Kernel Version: 2.6.31.5
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: harald.dunkel@t-online.de
> Regression: No
>
>
> 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.
>
> I had sent this information to the linux kvm mailing list before, but consensus
> was that this is a bridging problem. See
>
> http://www.spinics.net/lists/kvm/msg25153.html
>
> There was no reply on the linux bridge mailing list, see
>
>
> https://lists.linux-foundation.org/pipermail/bridge/2009-November/006749.html
next parent reply other threads:[~2009-11-12 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14586-10286@http.bugzilla.kernel.org/>
2009-11-12 22:39 ` Andrew Morton [this message]
2009-11-12 22:55 ` [Bugme-new] [Bug 14586] New: bridge on bonding interface: DHCP replies don't get through Stephen Hemminger
2009-11-13 3:23 ` Andy Gospodarek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091112143913.3d89e4f4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=harald.dunkel@t-online.de \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).