Xen users - Jul 2006 - vif0.0: received packet with own address as source

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@lists.xensource.com
http://lists.xensource.com/xen-users

On Saturday 29 July 2006 5:27 pm, Kevin Kult wrote:
> 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
AFAIK, it''s ok for all virtual devices at Dom0 to have the same MAC. 
what
must be unique on the network is the DomU''s eth0 devices.

-- 
Javier


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

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@gmail.com>
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@lists.xensource.com
http://lists.xensource.com/xen-users

Sorry!
 #3. in my earlier message should have read UNICAST MAC.
Kevin

On 8/7/06, Kevin Kult <kevin.kult@gmail.com>
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@gmail.com> 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@lists.xensource.com
http://lists.xensource.com/xen-users