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] network-route and vif-route setup help

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] network-route and vif-route setup help
From: Ralf Steenbock <ralf.steenbock@xxxxxxxxxxxx>
Date: Wed, 29 Mar 2006 11:43:21 +0200
Delivery-date: Wed, 29 Mar 2006 13:58:29 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <54628.80.176.88.99.1143591905.squirrel@xxxxxxxxxxxxxxxxxx>
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: <41371.80.176.88.99.1143584007.squirrel@xxxxxxxxxxxxxxxxxx> <54628.80.176.88.99.1143591905.squirrel@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20051002)
Hello,

>So what i see is this, ifconfig says:
>[root@cyclops ~]# ifconfig
>eth0      Link encap:Ethernet  HWaddr 00:40:CA:80:5B:80
>          inet addr:82.165.27.12  Bcast:82.165.27.12  Mask:255.255.255.255
>          inet6 addr: fe80::240:caff:fe80:5b80/64 Scope:Link
>          UP BROADCAST MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>          Interrupt:23 Base address:0xe000
>
>lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          inet6 addr: ::1/128 Scope:Host
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:48 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:4360 (4.2 KiB)  TX bytes:4360 (4.2 KiB)
>
>vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>          inet addr:82.165.27.12  Bcast:82.165.27.12  Mask:255.255.255.255
>          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:5 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:588 (588.0 b)  TX bytes:0 (0.0 b)
>
>
>82.165.27.12 is my main IP. vif1.0 seems to have been assigned the same ip.
>which probably makes sense because of what ip r says:
>[root@cyclops ~]# ip r
>82.165.37.144 dev vif1.0  scope link  src 82.165.27.12
>169.254.0.0/16 dev eth0  scope link
>default via 10.255.255.1 dev eth0
>
>37.144 is my domU ip. not sure exactly whats going on. but it probably means 
>vif1.0 is
>connected on 144? no idea.
>
>and what i have in my domU config:
>vif = [ 'ip=82.165.37.144' ]
>ip = "82.165.37.144"
>netmask="255.255.255.255"
>gateway="10.255.255.1"
>#gateway="82.165.27.12"
>
>the question is here do i use my isp's gateway? (10.*) the one for dom0?
>OR do i use dom0 itself? since we are routing i should use dom0?
>I tried both. the ifconfig and ip r output is the same.
>
>and lastly i used centos for domU too. so my 
>/etc/sysconfig/network-scripts/ifcfg-eth0 is:
>DEVICE=eth0
>ONBOOT=yes
>BOOTPROTO=static
>IPADDR=82.165.37.144
>NETMASK=255.255.255.255
>GATEWAY=10.255.255.1
>
>Is everything correct here?
>
This looks quite similar to my config. This way your domu mac should not
be visible to the switch.
Did you put

echo 1 >/proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp

into /etc/xen/scripts/network-route ?

It is absolutely necessary, because otherwise the server will not
forward packets to domu (first line) and not answer to arp request for
the ip of domu (second line).
Try it again and play with your network settings in domu ("xm console
xxx" with xxx as id of your domu). What is the output of "ifconfig" and
"ip r" in domu?

-- 
Dipl.-Ing. Ralf Steenbock -- EDV-Systementwicklung
Weg am Kötterberg 39, D-44807 Bochum
Tel.:  +49 (0)234 3252043 / +49 (0)177 7550868
www:   <http://www.openlogic.de>


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