This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 339] peth0: received packet with own address as source a

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 339] peth0: received packet with own address as source address
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sat, 19 Aug 2006 11:38:55 -0700
Delivery-date: Sat, 19 Aug 2006 11:39:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-339-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

russell@xxxxxxxx changed:

           What    |Removed                     |Added
                 CC|                            |russell@xxxxxxxx

------- Comment #6 from russell@xxxxxxxx  2006-08-19 11:38 -------
I am running Xen via the Fedora Core 5 kernels.  Unfortunately I don't know how
to deterine what version of Xen I'm running, but 'xm dmesg' say Xen version 

3.0-unstable (brewbuilder@xxxxxxxxxxxxxxxx) (gcc version 4.1.1 20060525 (Red
Hat 4.1.1-1)) Tue Aug  8 15:25:20 EDT 2006

These are messages that come out of the xen0's 'dmesg', (IE: not the 'xm
dmesg'), and unless there is something wrong in the default scripts from RedHat
it isn't a network config problem (IE: the XenU's and Xen0's on this LAN are
all unique addresses).   I do have two Xen servers if that might be the source
of the problem.  The other LAN I administrate Xen machines on also has more
than one Xen server, and each of them are issuing similar warnings.

I wish this bug were re-opened or at least further investigated.  Is the
problem that peth0 and all the vif?.0 interfaces all have the same HW address
of FE:FF:FF:FF:FF:FF and thus also have one of the IPv6 addresses on each of
these interfaces being fe80::fcff:ffff:feff:ffff/64 ?  Should the default
scripts that are setting up these interfaces discontinue setting up IPv6
addresses on these interfaces?

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>