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] bridge + arp

To: Moritz Möller <m.moeller@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] bridge + arp
From: "Phil Winterfield (winterfi)" <winterfi@xxxxxxxxx>
Date: Fri, 19 Sep 2008 13:37:04 -0700
Authentication-results: sj-dkim-4; header.From=winterfi@xxxxxxxxx; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Cc:
Delivery-date: Fri, 19 Sep 2008 13:37:04 -0700
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=3654; t=1221856591; x=1222720591; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=winterfi@xxxxxxxxx; z=From:=20=22Phil=20Winterfield=20(winterfi)=22=20<winterfi@ cisco.com> |Subject:=20RE=3A=20[Xen-devel]=20bridge=20+=20arp |Sender:=20; bh=woaibmkXRw52E6+A5c0VCtAokaUOL8zHCjOUqaIyOpo=; b=bB39gxp1P1dQSa3/OqOitud4jBeG2xAuclgWHMbwQgjxp6y4jNFgD3xbmp lLRT9GaUBzkSRAtZaQvEHgwxYHTuJkOoggBXMrIEWIjxlDoXyEikpvyP30jv yyPanvkFaF;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <122AA196D7CE4E4DBB92911EF4AB5AB38462ED@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <122AA196D7CE4E4DBB92911EF4AB5AB38462ED@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ackaibd2x6RUc2hATrStZ9Z1KWttUgADFgcg
Thread-topic: [Xen-devel] bridge + arp
Moritz,

I am seeing something very similar - see 
http://lists.xensource.com/archives/html/xen-devel/2008-09/msg00686.html

It looks as though the responses to arp requests are being dropped by the 
bridge, causing a halt in packet forwarding. Interestingly, the packet drop 
occurs even if I manually fill in the arp table with the entry. I am running 
with xen-unstable c/s 18242.

Phil

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Moritz Möller
> Sent: Friday, September 19, 2008 11:59 AM
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] bridge + arp
> 
> Hi,
> 
> this is propably bridge related and not really a xen problem, but it
> might help someone:
> 
> Some of our domUs are not able to arp. Arp -n show (incomplete), and
> doing a tcpdump shows, that on the dom0's eth0 the arp request goes out,
> the response comes in, but on the vifX.0 interface the arp response is
> gone.
> 
> dom0# tcpdump -ni eth0
> arp who-has 10.32.2.51 tell 10.32.7.70
> arp reply 10.32.2.51 is-at 00:30:48:34:44:6c
> 
> dom0# tcpdump -ni br0
> arp who-has 10.32.2.51 tell 10.32.7.70
> arp reply 10.32.2.51 is-at 00:30:48:34:44:6c
> 
> dom0# tcpdump -ni vif3.0
> arp who-has 10.32.2.51 tell 10.32.7.70
> 
> Does someone know why the dom0 br0 or vif eats the arp response?
> 
> Thanks a lot,
> 
> Moritz
> 
> 
> ip a l
> 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen
> 1000
>     link/ether 00:30:48:34:13:dc brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::230:48ff:fe34:13dc/64 scope link
>        valid_lft forever preferred_lft forever
> 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>     link/ether 00:30:48:34:13:dd brd ff:ff:ff:ff:ff:ff
> 4: br0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue qlen 20000
>     link/ether 00:30:48:34:13:dc brd ff:ff:ff:ff:ff:ff
>     inet 10.32.2.50/14 brd 10.35.255.255 scope global br0
>     inet6 fe80::230:48ff:fe34:13dc/64 scope link
>        valid_lft forever preferred_lft forever
> 5: vif1.0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen
> 32
>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::fcff:ffff:feff:ffff/64 scope link
>        valid_lft forever preferred_lft forever
> 6: vif2.0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen
> 32
>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::fcff:ffff:feff:ffff/64 scope link
>        valid_lft forever preferred_lft forever
> 7: vif3.0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen
> 32
>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::fcff:ffff:feff:ffff/64 scope link
>        valid_lft forever preferred_lft forever
> 
> 
> brctl show
> bridge name     bridge id               STP enabled     interfaces
> br0             8000.0030483413dc       no              eth0
>                                                         vif1.0
>                                                         vif2.0
>                                                         vif3.0
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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

<Prev in Thread] Current Thread [Next in Thread>