Xen users - May 2007 - Bug 339 - peth1: received packet with own address as source address

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

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

Hi Cyrus,
> on Your first dom0 use: macid="F0"
> on your second dom0 use: macid="F1"
Well I left the first one at the default, and patched the second box.
Ifconfig shows my mac addresses as:

box1  peth0  HWaddr FE:FF:FF:FF:FF:FF
box2  peth0  HWaddr FE:FF:FF:FF:F0:00

Actually, grepping ifconfig for HWaddr, is interesting:

guest1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
guest2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
eth0        Link encap:Ethernet  HWaddr 00:A0:D1:E5:27:BA
peth0      Link encap:Ethernet  HWaddr FE:FF:FF:FF:F0:00
vif0.0       Link encap:Ethernet  HWaddr FE:FF:FF:FF:F0:00
xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:F0:00

It shows that peth0, vif0.0 and the bridge all share this MAC address.
Is that correct I wonder?  It''s similar on the other box.

box1 runs xen 3.0.3  and is not showing any "received packet with own
address"
in it''s logs. They only show up on box2, which is running 3.0.5-rc4
patched with the code to change the mac address.

I will try changing it again, but I suspected there is not another machine
on the network with this mac address (FE:FF:FF:FF:F0:00 ) and that there
is something else wrong!

John

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

For what it is worth, I have tried changing the macid  to several
other hex digits,
restarted the box2, but I am still getting the "recieved packet with
own address"
errors.

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:A7:00
vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:A7:00
xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:A7:00

May  4 19:54:40 box2 kernel: peth0: received packet with  own address
as source address
May  4 19:54:40 box2  kernel: peth0: received packet with  own address
as source address

It can''t be another dom0 on the network with my random chosen MAC
address.
Are there any other causes of this problem?

John

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

Hi,

we had similar problems half a year a go. As far as I can remember it was only
on our IBM Servers.
We installed the available BIOS and NIC Firmware updates and the problem was
solved!

Normaly you shouldn''t even see this MAC on the LAN because in ifconfig
it is set to NOARP.

regards,
Jan
> -----Ursprüngliche Nachricht-----
> Von: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] Im Auftrag von 
> John Hannfield
> Gesendet: Freitag, 4. Mai 2007 20:58
> An: Cyrus Katrak
> Cc: xen-users@lists.xensource.com
> Betreff: [Xen-users] Re: Bug 339 - peth1: received packet 
> with own addressas source address
> 
> For what it is worth, I have tried changing the macid  to several
> other hex digits,
> restarted the box2, but I am still getting the "recieved packet with
> own address"
> errors.
> 
> peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:A7:00
> vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:A7:00
> xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:A7:00
> 
> May  4 19:54:40 box2 kernel: peth0: received packet with  own address
> as source address
> May  4 19:54:40 box2  kernel: peth0: received packet with  own address
> as source address
> 
> It can''t be another dom0 on the network with my random chosen 
> MAC address.
> Are there any other causes of this problem?
> 
> John
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users