Re: [Xen-users] veth0 is from netback and vifu.0 is fromthebridge-utils?

[Nivedita Singhvi <niv@xxxxxxxxxx>]

Anthony.Golia@xxxxxxxxxxxxxxxxx wrote:

> thx.  that helps but leaves me with a few more questions.  any doc is
> appreciated.  i had bridging on then changed the xend-config.sxp
> to use vif-route so now i have a completely different set of ints
> (see below).  i thought the eth0 in domU was linked to vifx.U in dom0?
> so with routing on there's no peth0?  is eth0 and eth1 still my real,
> physical interface?  the ascii diagram you have above is helpfull how does
> it look with routing?
>
> bash-3.00# ip addr
> 1: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>     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
> 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> mtu 1500 qdisc noop
>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> 5: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 6: 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
This really depends on your patchset/version you are running, and
your local script. Are you running the default network-route and
vif-route that's currently in the unstable tree? If you change
the vif file to be vif-route, you should have changed the network
file to be network-route, too. Looks like you have two interfaces
in dom0, that's why you have both eth0 and eth1. You have two
virtual backends (vif0.0, vif1.1). The default route scripts don't
rename the interface (so you won't have a peth0, for instance)..
Is the above working for you? Can you send netstat -rn output?

In brief:

physical interface (e.g. eth0) <=> virtual backend (e.g. vif0.0)
                                         ||
                                         \\
                                           =====> domU nic (eth0)


I'll confirm this once I get the latest tip working...

thanks,
Nivedita

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