peth1: received packet with own address as source address

peth1: received packet with own address as source address

[David F Barrera]

I am seeing a series of messages (below):

peth1: received packet with  own address as source address
peth1: received packet with  own address as source address
peth1: received packet with  own address as source address
peth1: received packet with  own address as source address
peth1: received packet with  own address as source address
peth1: received packet with  own address as source address
peth1: received packet with  own address as source address
peth1: received packet with  own address as source address
peth1: received packet with  own address as source address
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. 

-- 
Regards,

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

"The wisest men follow their own direction. "
                                                        Euripides

Re: peth1: received packet with own address as source address

[Arnd Schmitter]

David F Barrera wrote:
> I am seeing a series of messages (below):
>
> peth1: received packet with  own address as source address
> peth1: received packet with  own address as source address
> peth1: received packet with  own address as source address
> peth1: received packet with  own address as source address
> peth1: received packet with  own address as source address
> peth1: received packet with  own address as source address
> peth1: received packet with  own address as source address
> peth1: received packet with  own address as source address
> peth1: received packet with  own address as source address
> 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

	

	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

Re: peth1: received packet with own address as source address

[David F Barrera]

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

Re: peth1: received packet with own address as source address

[Arnd Schmitter]

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

Take a look at your ifconfig output. Maybe there are two 
Virtual-Interfaces witch the same MAC.

Arnd


	

	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

Re: peth1: received packet with own address as source address

[David F Barrera]

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

Re: peth1: received packet with own address as source address

[Andrew Theurer]

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 ??
>
> Take a look at your ifconfig output. Maybe there are two 
> Virtual-Interfaces witch the same MAC.

Unless the network-bridge script has changed the generated mac for eth0 
(which gets renamed to peth0), all systems probably have the same mac 
for peth0 & xen-br0: fe:ff:ff:ff:ff:ff.  I have tried using unique macs 
(for just peth0, vif0.0, and xen-br0, other vifs still have fe:ff...), 
and these messages disappear.  So, why would the mac for a veth0 or 
xen-br0 get sent to another system?  Not sure, since they should not 
have an ip address, and should not respond to an arp request.  I do 
notice that peth0 has 'noarp' but xen-br0 does not.  Perhaps adding 
noarp to xen-br0 will fix this.

-Andrew

Re: peth1: received packet with own address as source address

[Nivedita Singhvi]

Andrew Theurer wrote:
> 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 ??
>>
>> Take a look at your ifconfig output. Maybe there are two 
>> Virtual-Interfaces witch the same MAC.
> 
> 
> Unless the network-bridge script has changed the generated mac for eth0 
> (which gets renamed to peth0), all systems probably have the same mac 
> for peth0 & xen-br0: fe:ff:ff:ff:ff:ff.  I have tried using unique macs 
> (for just peth0, vif0.0, and xen-br0, other vifs still have fe:ff...), 
> and these messages disappear.  So, why would the mac for a veth0 or 
> xen-br0 get sent to another system?  Not sure, since they should not 
> have an ip address, and should not respond to an arp request.  I do 
> notice that peth0 has 'noarp' but xen-br0 does not.  Perhaps adding 
> noarp to xen-br0 will fix this.

This is what I thought it was, until Anthony said he was seeing
it even without guest domains, and without xend starting.  I'd
thought the network rename was in vif-bridge, but misremembered,
it's in network-bridge, so it really doesn't need xend to run to
run into the problem.

The MAC address is expected to be unique in a network, so it is
a problem if it's not.

The non-public MAC should not be going out, and if someone could just
say which the "same MAC address" reported in the message is, that
would confirm it. But xen-br0 shouldn't need a noarp(?) (checking...)


thanks,
Nivedita

Re: peth1: received packet with own address as source address

[Jerone Young]

On Mon, 2005-10-17 at 16:04 -0500, Andrew Theurer wrote:
> 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 ??
> >
> > Take a look at your ifconfig output. Maybe there are two 
> > Virtual-Interfaces witch the same MAC.
> 
> Unless the network-bridge script has changed the generated mac for eth0 
> (which gets renamed to peth0), all systems probably have the same mac 
> for peth0 & xen-br0: fe:ff:ff:ff:ff:ff.  I have tried using unique macs 
> (for just peth0, vif0.0, and xen-br0, other vifs still have fe:ff...), 
> and these messages disappear.  So, why would the mac for a veth0 or 
> xen-br0 get sent to another system?  Not sure, since they should not 
> have an ip address, and should not respond to an arp request.  I do 
> notice that peth0 has 'noarp' but xen-br0 does not.  Perhaps adding 
> noarp to xen-br0 will fix this.

This might just be it. We are no longer seeing it if we start xend with
#export netdev=eth1
#xend start
#ifconfig xen-br0 -arp

on an IBM HS20 blade that showed the error earlier. Could anyone else
seeing this try this to confirm this amongst more setups.


> 
> -Andrew
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
-- 
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)

Re: peth1: received packet with own address as source address

[Ted Kaczmarek]

On Mon, 2005-10-17 at 16:54 -0500, Jerone Young wrote:
> On Mon, 2005-10-17 at 16:04 -0500, Andrew Theurer wrote:
> > 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 ??
> > >
> > > Take a look at your ifconfig output. Maybe there are two 
> > > Virtual-Interfaces witch the same MAC.
> > 
> > Unless the network-bridge script has changed the generated mac for eth0 
> > (which gets renamed to peth0), all systems probably have the same mac 
> > for peth0 & xen-br0: fe:ff:ff:ff:ff:ff.  I have tried using unique macs 
> > (for just peth0, vif0.0, and xen-br0, other vifs still have fe:ff...), 
> > and these messages disappear.  So, why would the mac for a veth0 or 
> > xen-br0 get sent to another system?  Not sure, since they should not 
> > have an ip address, and should not respond to an arp request.  I do 
> > notice that peth0 has 'noarp' but xen-br0 does not.  Perhaps adding 
> > noarp to xen-br0 will fix this.
> 
> This might just be it. We are no longer seeing it if we start xend with
> #export netdev=eth1
> #xend start
> #ifconfig xen-br0 -arp
> 
> on an IBM HS20 blade that showed the error earlier. Could anyone else
> seeing this try this to confirm this amongst more setups.
> 
> 
> > 

I never see this when I use a setup like this.


dom0 #1
dom0 eth0 1.1.1.1/24
dom0 eth0:1 1.1.2.1/24
all domU's 1.1.1.2-127/24

dom0 #2
dom0 eth0 1.1.1.2/24
dom0 eth0:1 1.1.2.1/24
all domU's 1.1.1.127-254/24


But like this

dom0 eth0 1.1.1.1/24
dom0 eth1 1.1.2.1/24
all domU's 1.1.1.2-127/24

dom0 #2
dom0 eth0 1.1.1.2/24
dom0 eth1 1.1.2.1/24
all domU's 1.1.1.127-254/24

It happens consistently.

The no arp issue may be masking something else, you really want the
bridge to respond for arps for nodes behind it, otherwise all ports must
get flooded.


Ted

Re: peth1: received packet with own address as source address

[Andrew Theurer]

>
>The no arp issue may be masking something else, you really want the
>bridge to respond for arps for nodes behind it, otherwise all ports must
>get flooded.
>  
>
Would leaving arp on for the bridge really replying to arps for other 
devices on the bridge?  Would that not be a different feature, like 
proxy arp?  For some reason I think the bridge interface itself might be 
responding to an arp request, or possibly doing a reverse arp 
broadcast.  Is this happening only on a ping, or will a tcp 
communication cause this, too?

-Andrew

Re: peth1: received packet with own address as source address

[Ted Kaczmarek]

On Mon, 2005-10-17 at 18:52 -0400, Ted Kaczmarek wrote:
> On Mon, 2005-10-17 at 16:54 -0500, Jerone Young wrote:
> > On Mon, 2005-10-17 at 16:04 -0500, Andrew Theurer wrote:
> > > 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 ??
> > > >
> > > > Take a look at your ifconfig output. Maybe there are two 
> > > > Virtual-Interfaces witch the same MAC.
> > > 
> > > Unless the network-bridge script has changed the generated mac for eth0 
> > > (which gets renamed to peth0), all systems probably have the same mac 
> > > for peth0 & xen-br0: fe:ff:ff:ff:ff:ff.  I have tried using unique macs 
> > > (for just peth0, vif0.0, and xen-br0, other vifs still have fe:ff...), 
> > > and these messages disappear.  So, why would the mac for a veth0 or 
> > > xen-br0 get sent to another system?  Not sure, since they should not 
> > > have an ip address, and should not respond to an arp request.  I do 
> > > notice that peth0 has 'noarp' but xen-br0 does not.  Perhaps adding 
> > > noarp to xen-br0 will fix this.
> > 
> > This might just be it. We are no longer seeing it if we start xend with
> > #export netdev=eth1
> > #xend start
> > #ifconfig xen-br0 -arp
> > 
> > on an IBM HS20 blade that showed the error earlier. Could anyone else
> > seeing this try this to confirm this amongst more setups.
> > 
> > 
> > > 
> 
> I never see this when I use a setup like this.
> 
> 
> dom0 #1
> dom0 eth0 1.1.1.1/24
> dom0 eth0:1 1.1.2.1/24
> all domU's 1.1.1.2-127/24
> 
> dom0 #2
> dom0 eth0 1.1.1.2/24
> dom0 eth0:1 1.1.2.1/24
> all domU's 1.1.1.127-254/24
> 
> 
> But like this
> 
> dom0 eth0 1.1.1.1/24
> dom0 eth1 1.1.2.1/24
> all domU's 1.1.1.2-127/24
> 
> dom0 #2
> dom0 eth0 1.1.1.2/24
> dom0 eth1 1.1.2.1/24
> all domU's 1.1.1.127-254/24
> 
> It happens consistently.
> 
> The no arp issue may be masking something else, you really want the
> bridge to respond for arps for nodes behind it, otherwise all ports must
> get flooded.
> 
> 
 My bad, mixing up arp snooping here, the arps must always be flooded.
Been mulling this, peth0 is the bridge id, but without spanning tree
running should not be doing anything. Ian also stated this when I first
brought this up.

Has anyone captured this packet/frame yet? 

That would likely explain a lot.

Regards,
Ted

Re: peth1: received packet with own address as source address

[Nivedita Singhvi]

Ted Kaczmarek wrote:

>>It happens consistently.
>>
>>The no arp issue may be masking something else, you really want the
>>bridge to respond for arps for nodes behind it, otherwise all ports must
>>get flooded.
>>
>>
> 
>  My bad, mixing up arp snooping here, the arps must always be flooded.
> Been mulling this, peth0 is the bridge id, but without spanning tree
> running should not be doing anything. Ian also stated this when I first
> brought this up.

Er, peth0 is the physical interface - not sure what you mean by
"is the bridge id", Ted?

> Has anyone captured this packet/frame yet? 

Timezone delay ;). Tmrw morning..

> That would likely explain a lot.

Yep. I'll try and repro tonight if possible, or just catch one
of the guys on irc who are seeing it if they're around..

thanks,
Nivedita

Re: peth1: received packet with own address as source address

[Ted Kaczmarek]

On Mon, 2005-10-17 at 17:36 -0700, Nivedita Singhvi wrote:
> Ted Kaczmarek wrote:
> 
> >>It happens consistently.
> >>
> >>The no arp issue may be masking something else, you really want the
> >>bridge to respond for arps for nodes behind it, otherwise all ports must
> >>get flooded.
> >>
> >>
> > 
> >  My bad, mixing up arp snooping here, the arps must always be flooded.
> > Been mulling this, peth0 is the bridge id, but without spanning tree
> > running should not be doing anything. Ian also stated this when I first
> > brought this up.
> 
> Er, peth0 is the physical interface - not sure what you mean by
> "is the bridge id", Ted?
> 
> > Has anyone captured this packet/frame yet? 
> 
> Timezone delay ;). Tmrw morning..
> 
> > That would likely explain a lot.
> 
> Yep. I'll try and repro tonight if possible, or just catch one
> of the guys on irc who are seeing it if they're around..
> 
> thanks,
> Nivedita
brctl show

bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.feffffffffff       no              peth0
                     ^^^^^^^^^^^^ 

The bridges id is comprised of the mac address of the parent and the
preamble.

xen-br1         8000.00e081053c6d       no              eth1
                     ^^^^^^^^^^^^ 

eth1      Link encap:Ethernet  HWaddr 00:E0:81:05:3C:6D

                

brctl showmacs xen-br0
port no mac addr                is local?       ageing timer
  2     00:0c:f1:c9:6d:62       no               163.43
  2     00:60:97:bd:e5:af       no                 1.89
  2     00:90:f5:24:a8:13       no                 0.00
  2     00:b0:d0:07:0a:d1       no                 6.65
  1     00:e0:81:05:3c:6c       no                 0.00<<<<<<<<<
  9     aa:00:00:00:00:17       no                21.71
  2     aa:00:66:00:01:03       no                 0.12
  4     aa:00:66:00:01:07       no                25.57
  3     aa:00:66:00:01:08       no                 0.78
 14     aa:bb:bb:00:01:01       no                 7.38
 11     aa:bb:bb:00:01:02       no                 0.11
 12     aa:bb:bb:00:01:03       no                15.80
  8     aa:bb:bb:15:15:15       no                22.16
  6     aa:bb:bb:16:16:16       no                14.23
  7     aa:bb:bb:55:55:55       no                 7.82
  5     aa:bb:bb:66:66:66       no                15.34
  1     fe:ff:ff:ff:ff:ff       yes                0.00<<<<<<<<<

ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:E0:81:05:3C:6C

So if peth0 is a physical interface and eth0 is a physical interface
with xen I get a free nic card, just kidding.

What is the function of the peth0?

Say one doesn't want to use pethX at all, is that even possible?
I couldn't get vifs to map correctly when I tried, but that could just
be something still not implemented or a bug.


Regards,
Ted

Re: peth1: received packet with own address as source address

[Anthony Liguori]

David F Barrera wrote:

>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.
>  
>
There's at least 3 other people seeing this with snapshots as far back 
as 20050810.

Are you seeing this on a RHEL or Fedora system?

Regards,

Anthony Liguori

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

Re: peth1: received packet with own address as source address

[David F Barrera]

On Mon, 2005-10-17 at 15:31 -0500, Anthony Liguori wrote:
> David F Barrera wrote:
> 
> >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.
> >  
> >
> There's at least 3 other people seeing this with snapshots as far back 
> as 20050810.
Yes, I've been seeing this problem for some time now. 
> 
> Are you seeing this on a RHEL or Fedora system?

RHEL 4, SLES 9 SP2, and FC4 on both x86 and x86_64.
> 
> Regards,
> 
> Anthony Liguori
> 
> >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@lists.xensource.com
> >>http://lists.xensource.com/xen-devel
> >>
> >>    
> >>
> 
> 
> _______________________________________________
> 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

Re: peth1: received packet with own address as source address

[Andrew Theurer]

David F Barrera wrote:

>I am seeing a series of messages (below):
>
>peth1: received packet with  own address as source address
>peth1: received packet with  own address as source address
>peth1: received packet with  own address as source address
>peth1: received packet with  own address as source address
>peth1: received packet with  own address as source address
>peth1: received packet with  own address as source address
>peth1: received packet with  own address as source address
>peth1: received packet with  own address as source address
>peth1: received packet with  own address as source address
>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. 
>
>  
>
I am curious, on one machine with xen, can you ping another machine with 
xen?  Does it work when you get these messages?

-Andrew

Re: peth1: received packet with own address as source address

[David F Barrera]

On Mon, 2005-10-17 at 13:56 -0500, Andrew Theurer wrote:
> David F Barrera wrote:
> 
> >I am seeing a series of messages (below):
> >
> >peth1: received packet with  own address as source address
> >peth1: received packet with  own address as source address
> >peth1: received packet with  own address as source address
> >peth1: received packet with  own address as source address
> >peth1: received packet with  own address as source address
> >peth1: received packet with  own address as source address
> >peth1: received packet with  own address as source address
> >peth1: received packet with  own address as source address
> >peth1: received packet with  own address as source address
> >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. 
> >
> >  
> >
> I am curious, on one machine with xen, can you ping another machine with 
> xen?  Does it work when you get these messages?
> 
Yes, it works. Incidentally, both machines show the message.

> -Andrew
> 
> 
> _______________________________________________
> 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