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: Sun, 23 Oct 2005 22:53:28 +0000
Delivery-date: Sun, 23 Oct 2005 22:53:33 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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

ewan@xxxxxxxxxxxxx changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

------- Additional Comments From ewan@xxxxxxxxxxxxx  2005-10-23 22:53 -------
This is believed to have been caused by the machine's routing tables getting 
into a state where they claim to be going through peth0 rather than eth0.  If 
this happened with two Xen machines on the network, then one would complain 
about packets coming from the other.

This problem is believed fixed with changeset 7436:18eb059ae471.

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

Xen-bugs mailing list