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-devel

Re: [Xen-devel] peth1: received packet with own address as source addres

To: Arnd Schmitter <arnd_xen@xxxxxxxx>
Subject: Re: [Xen-devel] peth1: received packet with own address as source address
From: David F Barrera <dfbp@xxxxxxxxxx>
Date: Mon, 17 Oct 2005 15:15:10 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 17 Oct 2005 20:12:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4353F277.3080703@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1129574685.6253.20.camel@dbarrera_tp> <4353F277.3080703@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2005-10-17 at 20:50 +0200, Arnd Schmitter wrote:
> David F Barrera wrote:
> > peth1: received packet with  own address as source address
> >
> > Is this something that I should care about? I don't see an obvious
> > impact to the machine.    
> 
> This means normaly two things: Packets you send out are returning or 
> there is another PC with the same address.
> The Linuxkernel drops this packets as he think its a knd of address 
> spoofing.
> If all networking is working fine you will only have a minimal impact on 
> performance. But it could indicate that something with your network 
> configuration is wrong
Arnd, thanks for your response. My network configuration appears to be
OK; it is simple, one NIC and its IP address, and everything seems to be
working well. Also, there are no two machines with the same address. So,
I am wondering if this is a problem with Xen. I have opened up a
bugzilla report, as I would like to have a definitive answer as to
whether this is a bug or a network configuration issue.

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=339
> 
> Arnd
> 
>       
> 
>       
>               
> ___________________________________________________________ 
> Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: 
> http://mail.yahoo.de
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


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