From: David F Barrera <dfbp@us.ibm.com>
To: Arnd Schmitter <arnd_xen@yahoo.de>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: peth1: received packet with own address as source address
Date: Mon, 17 Oct 2005 15:55:40 -0500 [thread overview]
Message-ID: <1129582541.6256.41.camel@dbarrera_tp> (raw)
In-Reply-To: <435409BE.1070006@yahoo.de>
On Mon, 2005-10-17 at 22:29 +0200, Arnd Schmitter wrote:
> David F Barrera wrote:
> > 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
> >
>
> Only one NIC and peth1 ??
Actually peth0 (I have a blade that has two NICs, but I am using eth1,
so it shows peth1).
>
> Take a look at your ifconfig output. Maybe there are two
> Virtual-Interfaces witch the same MAC.
Right on. vif0.0 and vif1.1 (vif1.1 and xen-br0, too) have the same
HWaddr. But why? I there some configuration I need to do?
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:25:3E:39:F2
inet addr:9.3.189.44 Bcast:9.3.189.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:133688 errors:0 dropped:0 overruns:0 frame:0
TX packets:1956 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:61267457 (58.4 Mb) TX bytes:1010478 (986.7 Kb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:20444177 errors:0 dropped:0 overruns:0 frame:0
TX packets:20444177 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2151657391 (2051.9 Mb) TX bytes:2151657391 (2051.9
Mb)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:152597 errors:0 dropped:0 overruns:0 frame:0
TX packets:2861 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:71081525 (67.7 Mb) TX bytes:1507449 (1.4 Mb)
Interrupt:24
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1956 errors:0 dropped:0 overruns:0 frame:0
TX packets:133688 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1010478 (986.7 Kb) TX bytes:61267457 (58.4 Mb)
vif1.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:913 errors:0 dropped:0 overruns:0 frame:0
TX packets:131949 errors:0 dropped:244 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:485625 (474.2 Kb) TX bytes:60965539 (58.1 Mb)
xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70489 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6514187 (6.2 Mb) TX bytes:0 (0.0 b)
>
> Arnd
>
>
>
>
>
>
> ___________________________________________________________
> Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> 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
next prev parent reply other threads:[~2005-10-17 20:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 18:44 peth1: received packet with own address as source address David F Barrera
2005-10-17 18:50 ` Arnd Schmitter
2005-10-17 20:15 ` David F Barrera
2005-10-17 20:29 ` Arnd Schmitter
2005-10-17 20:55 ` David F Barrera [this message]
2005-10-17 21:04 ` Andrew Theurer
2005-10-17 21:32 ` Nivedita Singhvi
2005-10-17 21:54 ` Jerone Young
2005-10-17 22:52 ` Ted Kaczmarek
2005-10-17 23:13 ` Andrew Theurer
2005-10-17 23:31 ` Ted Kaczmarek
2005-10-18 0:36 ` Nivedita Singhvi
2005-10-18 11:54 ` Ted Kaczmarek
2005-10-17 20:31 ` Anthony Liguori
2005-10-17 20:44 ` David F Barrera
2005-10-17 18:56 ` Andrew Theurer
2005-10-17 19:00 ` David F Barrera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1129582541.6256.41.camel@dbarrera_tp \
--to=dfbp@us.ibm.com \
--cc=arnd_xen@yahoo.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.