|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] Re: Bug 339 - peth1: received packet with own address as sou
After implementing the patch, you must edit the line that says:
macid="F0"
on ONE of the dom0's.
E.G:
on Your first dom0 use: macid="F0"
on your second dom0 use: macid="F1"
You mentioned the possiblity of an unkown dom0 on the network. I
believe you can use any MAC you want, but changing macid="F0" to some
other 2-hex digit ID should provide you with enough options.
Please let me know if this works
-Cyrus
On 5/4/07, John Hannfield <hal9020@xxxxxxxxx> wrote:
Hello,
I have two xen servers on the same subnet, and I'm seeing these messages
logged every minute to /var/log/messages
peth1: received packet with own address as source address
It's in bugzilla as bug 339
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=339
It seems to be due to both machines using the same hardware address
for dom0 peth1. So I have implemented the patch by Cyrus Katrak
and changed one machine to
FE:FF:FF:FF:F0:FF
However it still occurs. There could be a (unkown to me) dom0 server
on the network with this MAC address, so my question is:
Can I just assign any MAC address I want to peth1 ?
Like one of the private range that I use for my guests?
Or does it have to be FE:FF:FF:FF:xx:xx ?
--
John
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|