|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] peth1: received packet with own address as source addres
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] peth1: received packet with own address as source address, (continued)
- Re: [Xen-devel] peth1: received packet with own address as source address, Arnd Schmitter
- Re: [Xen-devel] peth1: received packet with own address as source address, David F Barrera
- Re: [Xen-devel] peth1: received packet with own address as source address, Arnd Schmitter
- Re: [Xen-devel] peth1: received packet with own address as source address, David F Barrera
- Re: [Xen-devel] peth1: received packet with own address as source address, Andrew Theurer
- Re: [Xen-devel] peth1: received packet with own address as source address, Nivedita Singhvi
- Re: [Xen-devel] peth1: received packet with own address as source address, Jerone Young
- Re: [Xen-devel] peth1: received packet with own address as source address, Ted Kaczmarek
- Re: [Xen-devel] peth1: received packet with own address as source address,
Andrew Theurer <=
- Re: [Xen-devel] peth1: received packet with own address as source address, Ted Kaczmarek
- Re: [Xen-devel] peth1: received packet with own address as source address, Nivedita Singhvi
- Re: [Xen-devel] peth1: received packet with own address as source address, Ted Kaczmarek
|
|
|
|
|