[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-users] Re: vif0.0: received packet with own address as source
- To: xen-users@xxxxxxxxxxxxxxxxxxx
- From: "Kevin Kult" <kevin.kult@xxxxxxxxx>
- Date: Mon, 7 Aug 2006 19:47:41 -0700
- Delivery-date: Mon, 07 Aug 2006 19:48:20 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=H48uEEodL8jelaO1cecv/GYBi/PHrxN9konVkXgKEeSSiOibKDcAU2QXPjrBUOAxs0l6+fG4WJPvYsLlss7Y3jB12jOadNpw7kR5d+nnttG+va4hLpoOkrRASH3ANbEXaFykujXrl8lKWJsg06s0q9JRISLBdGOHOvNTTOoEju0=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Sorry!
#3. in my earlier message should have read UNICAST MAC.
Kevin
On 8/7/06, Kevin Kult <kevin.kult@xxxxxxxxx
> wrote:Realizing that this error is not a XEN issue, but one of bridged networks, I understand why when this question has been posed in the past responders on lists like this dismiss the question quickly. I found the same on the FC list archives as well. Anyway just to help out anyone else who tries to resolve an issue like this and turns to the archive as a first source for answers, here are my findings and a resolution that worked for me.
It turns out that some Network cards ( in my case a Linksys) use the same default MAC (FE:FF:FF:FF:FF:FF) as the Xenbridge uses as a default for the attached virtual interfaces. This resulted in the "received packet with own address as source" error message as the virtual ethernet card tries to send packets through the bridge. The first stop along the way is the associated
vifX.X, which announces the above complaint. The steps I followed to clear this were:
1. Down the bridge,
2. Down the eth0 network card,
3. Bring eth0 back up with a forced multicast MAC (ie: FA:00:00:00:FF:FF),
4. Restart the xen bridge with the network-bridge script.
I hope this helps someone else out.
Kevin
On 7/29/06, Kevin Kult <
kevin.kult@xxxxxxxxx> wrote:I am new to Xen and am running Fedora 5 with Xen 3 and have been unable to get the network-bridge working at all. Once Xend starts and the xenbridge is brought up all networking ability dies. Any traffic generated to or from the bridged network causes the error noted above. I have seen this and similar errors (peth0, eth0....) discussed on this list, bugzilla, and the Fedora Xen list. On none of the threads have I seen a definitive answer for how to fix the problem.
One possibility I have is that the error occurrs because all the virtual devices have the same MAC (FE:FF:FF:FF:FF:FF). If my theory is correct where do I redefine the MAC's assigned to the various Dom0 interfaces. If I'm mistaken any suggestions would be greatly appreciated. I am attaching the various query responses to help in diagnosis. Thanks in advance.
Kevin
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
