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] veth0 is from netback and vifu.0 is fromthebridge-utils?

To: Anthony.Golia@xxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] veth0 is from netback and vifu.0 is fromthebridge-utils?
From: Nivedita Singhvi <niv@xxxxxxxxxx>
Date: Mon, 24 Oct 2005 12:57:45 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 24 Oct 2005 19:55:06 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.58.200510241352240.5045@xxxxxxxxxxxx>
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: <A95E2296287EAD4EB592B5DEEFCE0E9D32DE0D@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.58.200510241352240.5045@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.8 (X11/20041020)
Anthony.Golia@xxxxxxxxxxxxxxxxx wrote:
sorry to bring this up again but i'm still confused (i know things changed
recently with peth0 and all).  so theres no more veth0?  whats peth0?
(someone said it was the physical int, i thought that was eth0, eth1,
etc.).  Also, i'm using vif-route not bridge:

bash-3.00# ip addr
1: peth0: <BROADCAST,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
2: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:09:6b:b5:6b:95 brd ff:ff:ff:ff:ff:ff
    inet 172.31.215.177/24 brd 172.31.215.255 scope global eth1
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 scope host lo
    inet 172.31.254.207/32 brd 172.31.254.207 scope global lo:hostname
4: vif0.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
5: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:09:6b:b5:6b:94 brd ff:ff:ff:ff:ff:ff
    inet 172.31.205.177/24 brd 172.31.205.255 scope global eth0
6: xen-br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
7: vif1.1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet 169.254.1.0/32 brd 169.254.1.0 scope global vif1.1


Anthony, what version/changeset are you running?
Any answer you get is probably true only for a range of changesets.

We're trying to put together some documentation of the networking
stack this week, once we clean up a few issues...

Firstly, you seem to be running in bridged mode - you have all the
infrastructure we create in the default bridge scripts (which we
don't in the default routing setup):

The 0 in the names below is the default, it will be $vifnum,
specific to your local script changes, otherwise...


              Domain0 network stack
                       ^^
                       ||
                       ||
              eth0 [local virtual interface]
                       ^^
                       ||
                       || local traffic intended for domain0
                       ||
                       ||
xen-br0 [bridge] <===> vif0.0 [virtual dom0]  <=======> eth0 [domU virtual nic]
  ||
  ||
  || external traffic
  ||
  VV
peth0 [real, physical interface]
  ||
--XX ------------ NETWORK -----------------


I'm trying to put together some documentation of the networking
stack this week, once a few issues get cleaned up. I started on
this lastweek but the stack has been a bit volatile (someone else
floated something similar more recently with some more text)..

Hope that helps for now..

thanks,
Nivedita



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