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-devel] veth0 stuff in -unstable?

To: Nate Carlson <natecars@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] veth0 stuff in -unstable?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 08 Jul 2005 18:20:37 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 08 Jul 2005 17:19:35 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Your message of "Fri, 08 Jul 2005 11:49:46 CDT." <Pine.LNX.4.61.0507081135500.20046@xxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> OK - so for a bridging setup, on d0, as I understand it from that script, 
> we're supposed to have 4(!) interfaces now:
> eth0
> veth0
> vif0.0
> xen-br0
> One thing I find odd is that it assigns the IP address to veth0, but 
> vif0.0 is the one that gets added to the bridge with eth0 - is that the 
> expected behavior?
> How does veth0/vif0.0 relate to the physical device? Is it just another 
> entirely "virtual" device, or should I be able to take eth0 down, assign 
> the IP to veth0, and have things work?

veth0/vif0.0 is basically a two-interface (back-to-back) loopback
device. Packets transmitted on one interface are received on the other
(with appropriate copying and checksum-offload twiddling).

 -- Keir

Xen-devel mailing list

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