Mailinglist Archive: opensuse-bugs (8107 mails)

< Previous Next >
[Bug 244018] New: XEN being used with bonding causes bad network bridge setup ("kernel: bond0: received packet with own address as source address")
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 9 Feb 2007 02:44:55 -0700 (MST)
  • Message-id: <bug-244018-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=244018

Summary: XEN being used with bonding causes bad network bridge
setup ("kernel: bond0: received packet with own address
as source address")
Product: SUSE Linux 10.1
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Xen
AssignedTo: cgriffin@xxxxxxxxxx
ReportedBy: Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx
QAContact: qa@xxxxxxx


(This was found in SLES10, but I could not find any report on it, so here it
comes)
When configuring xend to use a bonding device according to
http://www.novell.com/coolsolutions/feature/17605.html, the syslog is filled
with messages like:
kernel: bond0: received packet with own address as source address
(see also
http://lists.xensource.com/archives/html/xen-users/2006-11/msg00338.html)
According to
http://www.mail-archive.com/linux-net@xxxxxxxxxxxxxxx/msg00892.html ("There
should be no IP on any interface part of a bridge. Only the bridge device
should have IP assigned. Any other configuration will produce somewhat odd
results.") the configuration the XEN scripts produce is illegal.

When I let the bonding device configured, but tell XEN to only use one of the
enslaved devices, xend shuts down the bonding devices during startup, naturally
leading to "no network". In that case I have a "peth0" interface corresponding
to the previous "eth0", but in the case of using the bonding device, I do not
see a "pbond0" device. I admit that I do not understand what the scripts do in
the bridge case.


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >
This Thread
  • No further messages