Xen users - Mar 2007 - Resolved | peth1: received packet with own address as source address

If you get a lot of those messages and you don''t want them:

peth1: received packet with  own address as source address
or
peth0: received packet with  own address as source address

This is the way I found to solve this problem on Debian maybe someone can
post more information about other distribution like suse or redhat...
This problem will occur if you have more than one dom0 on your network.

Problem: the interfaces created by Xen on boot always use the same MAC
Address: FE:FF:FF:FF:FF:FF and the other dom0 have the same MAC address...

Look:
peth1     Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          adr inet6: fe80::fcff:feff:feff:ffff/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1738 errors:8 dropped:0 overruns:0 frame:0
          TX packets:1317 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:200719 (196.0 KiB)  TX bytes:172960 (168.9 KiB)
          Interruption:17 Adresse de base:0x8000

Go to you Xen folder, then in the scripts folder:
cd /etc/xen/scripts

you''ll have to modify two script :

vi /etc/xen/scripts/xen-network-common.sh
vi /etc/xen/scripts/network-bridge

Try to find in those files the pattern "fe:" you''ll see
"fe:ff:ff:ff:ff:ff"
without the bracket.. then just change one "f" for a "e" or
something like
that.. do it for both script then reboot.

Be careful.. if you have 3 Xen dom0 do not make the same change on each
server.. you''ll have the same problem..

On reboot you''ll see your virtual device with a brand new Mac address!
and
no more anoying messages ;)

-- 
René Jr Purcell
Chargé de projet, sécurité et sytèmes
Techno Centre Logiciels Libres, http://www.tc2l.ca/
Téléphone : (418) 681-2929 #124


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