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/
Home Products Support Community News


Re: [Xen-users] RESOLVED: Broadcom NetXtreme II (DELL 1950)

To: "Fajar A. Nugraha" <fajar@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] RESOLVED: Broadcom NetXtreme II (DELL 1950)
From: Stefan de Konink <skinkie@xxxxxxxxx>
Date: Wed, 10 Oct 2007 09:08:47 +0200 (CEST)
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 10 Oct 2007 00:09:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <470C7325.1070103@xxxxxxxxxxxxx>
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 10 Oct 2007, Fajar A. Nugraha wrote:

> This is how linux bridge works.
> Solaris bridge uses a different bridging configration, in which you put
> IP address on the NIC.

Interesting, than it was not stupidness ;)

> What I like to do is this :
> eth1 --- bridge --- tap0,vif0.1
> veth1:
> That is :
> - disabled Xen's network-bridge script
> - put vif0.1 on the bridge
> - setup ip address on veth1
> vif0.1 and veth1 is created by xen's netloop driver (loaded by xend. I
> also added it to /etc/modprobe.conf). I prefer this setup because :
> - there's no IP address on the bridge
> - All networking setup is done by redhat's standard config files.

When I put a tcpdump on the interface the only thing data came out was
tap0. What is vif0.1 doing for Xen?


Xen-users mailing list