Xen users - Jun 2009 - dealing with "eth0: received packet with own address as source address"

Usually I use a dedicated NIC for dom0 management, with another NIC
using vlans for domU, and bridges created using Redhat''s
/etc/sysconfig/network-scripts/ifcfg-*. All works great.

Now I''m testing a new machine with Xen 3.4, using only one NIC for
both dom0 and domU traffic, bridged networking, IPv6 disabled. The
result was not so good: I kept on getting "eth0: received packet with
own address as source address" whenever a domU is active. Turns out
it''s because domU''s vif (vif1.0, vif2.0, etc) uses MAC
FE:FF:FF:FF:FF:FF, and it pretty much results in
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=339

For dom0 part it can be "fixed" using the new network-bridge attached
in bug report (basically assigning vif0.x unique MAC address). This
does not fix domU though, as they''re vif still use FE:FF:FF:FF:FF:FF.
I had to hack vif-bridge, adding a random MAC generator to solve this
problem.

Do you guys have this problem as well? How did you deal with it?

-- 
Fajar

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