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] [SOLVED] vif-route/networking-route question

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] [SOLVED] vif-route/networking-route question
From: Timo Benk <timo.benk@xxxxxx>
Date: Tue, 4 Apr 2006 10:43:03 +0200
Delivery-date: Tue, 04 Apr 2006 01:44:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: 20060401134914.83060156.timo.benk@xxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: RoundCube Webmail/0.1b
The following solved my problem:

Enabling proxy_arp on the outgoing interface in dom0:
# echo 1  > /proc/sys/net/ipv4/conf/eth0/proxy_arp

Greetings,
-timo

On Sat, 1 Apr 2006 13:49:14 +0200, Timo Benk <timo.benk@xxxxxx> wrote:
> Hi,
> 
> i set up dom0 to use vif-route and network-route instead of bridging
> with eth0 = 172.48.0.128/12.
> 
> I created two domU\'s, xen-dom1 with vif = [ \'ip=172.48.0.101\' ] and
> xen-dom2 with vif = [ \'ip=172.48.0.101\' ].
> 
> As expected, vif-route sets two static routes for vif7.0 and vif2.0:
> 
> ---<snip>---
> 172.48.0.101 dev vif7.0  scope link  src 172.48.0.128
> 172.48.0.102 dev vif2.0  scope link  src 172.48.0.128
> 172.48.0.0/12 dev eth0  proto kernel  scope link  src 172.48.0.128
> default via 172.48.0.1 dev eth0
> ---<snip>---
> 
>>From within dom0 i can:
> - ping 172.48.0.101
> - ping 172.48.0.102
> - ping 172.48.0.1 (which is an external machine)
> 
>>From within 172.48.0.1 i can:
> - ping 172.48.0.128
> - ping 172.48.0.101  does not work
> - ping 172.48.0.102  does not work
> 
>>From within xen-dom1 i can:
> - ping 172.48.0.101
> - ping 172.48.0.102
> - ping 172.48.0.128
> - ping 172.48.0.1   does not work
> 
>>From within xen-dom2 i can:
> - ping 172.48.0.101
> - ping 172.48.0.102
> - ping 172.48.0.128
> - ping 172.48.0.1   does not work
> 
> vif-route does not set /proc/sys/net/ipv4/ip_forward to 1 as
> expected ([1]), so i does that by myself.
> 
> Any ideas why i cannot reach 172.48.0.1 from within domU?
> 
> Greetings,
> -timo
> 
> [1]http://lists.xensource.com/archives/html/xen-users/2006-02/msg00030.html
> 
> --
> Timo Benk
> Fax:   +49-(0)12120-152802
> Mobil: +49-(0)178-8066638
> PGP Public Key: http://vs241071.vserver.de/timo_benk_gpg_key.asc
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
-- 
Timo Benk
Fax:   +49-(0)12120-152802
Mobil: +49-(0)178-8066638
PGP Public Key: http://vs241071.vserver.de/timo_benk_gpg_key.asc



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

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-users] [SOLVED] vif-route/networking-route question, Timo Benk <=