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

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








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