Ian Pratt
2005-Oct-25 12:15 UTC
RE: [Xen-users] veth0 is from netback and vifu.0 isfromthebridge-utils?
> 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:peth0 is the physical interface. eth0 is the virtual interface dom0 has that is attached to the bridge and should be configured with an IP address and have routes pointed through it etc. When you run xend it runs network-bridge which creates the bridge, renames eth0->peth0 and veth0->eth0 and brings the new eth0 back up. Best, Ian> 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 > > > > On Wed, 14 Sep 2005, Ian Pratt wrote: > > > > > > > It''s effectively a point to point link, allowing domain 0 > > > to connect > > > > on to the bridge in the same manner that other domains do. > > > > (before, packets to domain 0 were short-cutted and came off the > > > > bridge directly, which could lead to traffic from other domains > > > being stalled > > > > if a lot of traffic was destined to user space in dom0. > > > > > > thx. what''s the diff betwn the two (veth0 and vifu.0) ? > > > > vifX.0 is the end of the virtual ''cross-over cable'' that''s > connected > > to the bridge. veth0 is the end that''s effectively the domain''s > > virtual NIC, and hence has the IP address associated with it. > > > > Ian > > > > ) > > > > > > > Cheers, > Anthony > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anthony.Golia@MorganStanley.com
2005-Oct-25 14:53 UTC
RE: [Xen-users] veth0 is from netback and vifu.0 isfromthebridge-utils?
On Tue, 25 Oct 2005, Ian Pratt 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: > > peth0 is the physical interface. > > eth0 is the virtual interface dom0 has that is attached to the bridge > and should be configured with an IP address and have routes pointed > through it etc. > > When you run xend it runs network-bridge which creates the bridge, > renames eth0->peth0 and veth0->eth0 and brings the new eth0 back up.kewl, thx Ian. i see network-route doesnt do this. i think thats a good thing. do you forsee that changing?> Best, > Ian > > > > 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 > > > > > > > > On Wed, 14 Sep 2005, Ian Pratt wrote: > > > > > > > > > > It''s effectively a point to point link, allowing domain 0 > > > > to connect > > > > > on to the bridge in the same manner that other domains do. > > > > > (before, packets to domain 0 were short-cutted and came off the > > > > > bridge directly, which could lead to traffic from other domains > > > > being stalled > > > > > if a lot of traffic was destined to user space in dom0. > > > > > > > > thx. what''s the diff betwn the two (veth0 and vifu.0) ? > > > > > > vifX.0 is the end of the virtual ''cross-over cable'' that''s > > connected > > > to the bridge. veth0 is the end that''s effectively the domain''s > > > virtual NIC, and hence has the IP address associated with it. > > > > > > Ian > > > > > > ) > > > > > > > > > > > > > Cheers, > > Anthony > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > >Cheers, Anthony _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users