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 problem on FC3. Please help!

To: Kir <kir@xxxxxxxxxx>
Subject: Re: [Xen-devel] bridge problem on FC3. Please help!
From: James Bulpin <james@xxxxxxxxxxxxx>
Date: Thu, 30 Jun 2005 23:47:25 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 30 Jun 2005 22:46:21 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <732405245.20050630141137@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <732405245.20050630141137@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
Does your iptables FORWARD chain in dom0 prevent the forwarding of
packets across the bridge?

James

Kir wrote:
Hello all,

I've got some strange problem with bridge. Ping from DomU doesn't
work, but I can see correct icmp packets on the bridge.
On domU I run:
ping 213.33.197.1

On Dom0 I see:
tcpdump -i xen-br0
12:41:41.697372 IP 213.33.197.2 > 213.33.197.1: icmp 64: echo request seq 1
12:41:41.697709 IP 213.33.197.1 > 213.33.197.2: icmp 64: echo reply seq 1

I've spent 4 days playing with bridge, but no result! Please help me!
Fedora 3 and xen 2.0.6 are installed on my box.

Bridge config for dom0 is:
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.0004762663d3       no              eth0
                                                        vif2.0
Router config of Dom0 is:
213.33.197.0    *               255.255.255.192 U     0      0        0 xen-br0
default         213.33.197.1    0.0.0.0         UG    0      0        0 xen-br0

ip addr show (Dom0) is:
1: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:04:76:26:63:d3 brd ff:ff:ff:ff:ff:ff
    inet 213.33.197.3/26 brd 213.33.197.63 scope global eth0
3: lo: <LOOPBACK,UP> 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 brd 127.255.255.255 scope host lo
4: xen-br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:04:76:26:63:d3 brd ff:ff:ff:ff:ff:ff
    inet 213.33.197.3/32 brd 213.33.197.63 scope global xen-br0
6: vif2.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff

DomU has vif:
(vif
     (idx 0)
     (vif 0)
     (mac aa:10:00:00:00:11)
     (vifname vif2.0)
     (bridge xen-br0)
     (evtchn 12 4)
     (index 0)
 )



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

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