Re: [Xen-devel] veth0 stuff in -unstable?

[Nate Carlson <natecars@xxxxxxxxxxxxxxx>]

On Fri, 8 Jul 2005, Keir Fraser wrote:
> veth0 serves two purposes. First, it correctly provides 
> checksum-avoidance across the Ethernet bridge. Second, it ensures that 
> locally-delivered packets coming from other domains on the same box are 
> copied into local buffers. This is actually quite important: otherwise 
> we end up tying up network buffers belonging to a domU for unbounded 
> time (buffers may wait in socket queues in dom0 for example) and also 
> tying up resources in dom0's netback driver.
> We have had reports of problems with veth0 though -- possibly the setup 
> script (/etc/xen/scripts/network iirc) is broken for some people.
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?
------------------------------------------------------------------------
| nate carlson | natecars@xxxxxxxxxxxxxxx | http://www.natecarlson.com |
|       depriving some poor village of its idiot since 1981            |
------------------------------------------------------------------------

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