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

Re: [Xen-users] multiple vif's/bridges

To: andrew mathes <amathes@xxxxxxxxxxxx>
Subject: Re: [Xen-users] multiple vif's/bridges
From: Mark Doll <doll@xxxxxxxxx>
Date: Tue, 03 May 2005 12:06:58 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 03 May 2005 10:06:27 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.62.0505021201590.24098@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <900f397f05042811593195bab5@xxxxxxxxxxxxxx> <Pine.LNX.4.62.0504281225410.11340@xxxxxxxxxxxxxxxxxx> <900f397f0504281330637df347@xxxxxxxxxxxxxx> <Pine.LNX.4.62.0504291137590.561@xxxxxxxxxxxxxxxxxx> <900f397f05042914305022b40e@xxxxxxxxxxxxxx> <Pine.LNX.4.62.0504291522001.4465@xxxxxxxxxxxxxxxxxx> <900f397f050430090544ad824a@xxxxxxxxxxxxxx> <Pine.LNX.4.62.0505012141250.5264@xxxxxxxxxxxxxxxxxx> <20050502142412.GE7330@xxxxxxxxxxxxxxxx> <Pine.LNX.4.62.0505020834200.20512@xxxxxxxxxxxxxxxxxx> <Pine.LNX.4.62.0505021021220.20512@xxxxxxxxxxxxxxxxxx> <42766E55.7000007@xxxxxxxxx> <Pine.LNX.4.62.0505021201590.24098@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.6) Gecko/20050317 Thunderbird/1.0.2 Mnenhy/0.7
Hi Andrew!

andrew mathes wrote:
> hm, tcpdump from external -> eth3 of dom0 looks fine
>
> tcpdump from exteran -> eth1 of domU = no reply
>
> tcpdump from eth3 -> ext = fine
>
> tcpdump from eth3->domU ... the ping says it's ok, but tcpdump shows
> nothing
>
> likewise domU->eth3 ... says it's pinging, but tcpdump shows nothing
>

Run tcpump on xen-br1 instead of eth3 and you should see the ICMP packets.


> so is what's happening here is both sides pinging the bridge, but
> nothing is going through?  i have this in dmesg:
>
> device vif1.0 entered promiscuous mode
> xen-br0: port 1(vif1.0) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 1(vif1.0) entering forwarding state
> device vif1.1 entered promiscuous mode
> xen-br1: port 2(vif1.1) entering learning state
> xen-br1: topology change detected, propagating
> xen-br1: port 2(vif1.1) entering forwarding state
>
> so that looks good ...

ACK.


> i'm not supposed to make the domU gateway the same as the domO nic or
> anything am i?

dom0 isn't a gateway (forwarding is disabled). Bridging runs entirely on
layer 2 (Ethernet), not layer 3 (IP).

>
> perhaps that dump information will clarify the problem ...
>
> i hope =)

Not really. I have ne idea where the mistake in your config is. :-(

Mark.

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>