Re: [Xen-devel] Setting up virtual network

[Edward Middleton <edward@xxxxxxxxxxxxxxx>]

> ===================================================
> ifconfig on domain0
>
> eth0      Link encap:Ethernet  HWaddr 00:0E:A6:6B:70:CC
>          inet addr:128.100.241.161  Bcast:128.100.241.255  Mask:255.255.255.0
>
> xen-br0   Link encap:Ethernet  HWaddr 00:0E:A6:6B:70:CC
>          inet addr:128.100.241.161  Bcast:128.100.241.255 
>
> ===================================================
> ifconfig on ttylinux
>
> eth0      Link encap:Ethernet  HWaddr AA:00:00:41:24:DF
>          inet addr:10.0.0.2  Bcast:10.255.255.255  Mask:255.0.0.0
>  
To start with a bridge must be on the same network.  If you look at your 
configuration eth0 on the domain0 is on the 128.100.241.0 network and 
you ttylinux is on the 10.0.0.0 network.
> I want to communicate between ttylinux and domain0 So I try to assign an IP to vif1.0 on domain0 
> "ifconfig vif1.0 10.0.0.1" Next I try to "ping 10.0.0.2" from domain0 and "ping 
> 10.0.0.1" from ttylinux.
>  
Think of vif1.0 and eth0 in ttylinux as being the same thing.  They have 
ip 10.0.0.2. What you want to do is remove the domain0 interface eth0 
from the bridge.
brctl delif xen-br0 eth0

bring down the xen-br0 interface

ifconfig xen-br0 down

bring it up with the host interface with 10.0.0.1 ip.

ifconfig xen-br0 10.0.0.1 up

this will put your bridge interface xen-br0 on the same network as 
vif1.0.  You should now be able to ping your ttylinux domain.
next you need to setup the NAT.  Use xen-br0 as though it was a real NIC 
interface to you LAN and all should work.
Edward Middleton


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel