WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] peth0: received packet with own address as source addres

To: Matthew Haas <haas@xxxxxxxxxxxxxx>
Subject: Re: [Xen-users] peth0: received packet with own address as source address
From: Dylan Martin <dmartin@xxxxxxxxxxxx>
Date: Wed, 1 Aug 2007 15:24:15 -0700
Cc: xen users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 01 Aug 2007 15:22:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46B1040B.6@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <46AF1980.3060006@xxxxxxxxxxxxxxxxxx> <46B1034B.5070609@xxxxxxxxxxxxxx> <46B1040B.6@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.3i
Just a dumb idea: are you sure the two boxes have different mac
addresses?

Slightly less dumb idea: grep through /etc looking for your IP
address and MAC address.  Maybe the system is consulting some dumb
file and getting the wrong address that way.  

Much less dumb idea: start up tcpdump on both machines and see
what actual traffic is causing the error.

> *** RESEND: I neglected to change subject line on previous post.
> *** Sorry for the confusion/misleading subject. Been a long day.
> 
> Howdy,
> 
>  Wondering if anyone can shed any light on this:
> 
>  I had a hard drive crash in a machine (P4 2.6GHz, Debian Etch, Xen 
> 3.0.3), and being lazy, I took a new drive, partitioned and formatted, 
> mounted as a slave into an existing machine, and did a:
> 
>      "cp -a /source/* /dest/"
> 
>  Off a rescue disk, to get all the data copied over. I then went in and 
> changed hostname and IP configuration in the appropriate places, 
> restored both machines to operating order, and started them up.
> 
>  Both machines come up and are accessible on the network. However, 
> before too much time passes, the following messages start to appear on 
> the console of both machines, and continue over time:
> 
>     peth0: received packet with  own address as source address
> 
>  Googling for some clue, apparently this message appeared in certain 
> Xen configurations, and was (presumably?) due to IPv6 configuration 
> issues.. I don't even have IPv6 compiled into the kernels on these 
> machines, so that doesn't appear to be my issue.
> 
>  I've scrounged through the Xen scripts and believe I see where peth0 
> is being created and brought online, but I see nothing there that 
> references an existing file to get ID from, or anything that would seem 
> to create an interface with duplicate settings as the other machine.
> 
>  Seems like some sort of static data was duplicated during the copy and 
> is not auto-generated, so both machines see each other's traffic on 
> peth0? Question is.. what/where?
> 
>  Any clues/suggestions would be greatly appreciated.
> 
>  Thanks!
> 
> -Matthew
> -- 
>  Matthew Haas
>  Visiting Instructor
>  Corning Community College
>  Computer & Information Science
>  http://lab46.corning-cc.edu/haas/home/
> 
>   "Writing should be like breathing;
>    It is one of those important things we do." -- me
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

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