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@lists.xensource.com http://lists.xensource.com/xen-users
Timo Benk
2006-Apr-04 08:43 UTC
Re: [Xen-users] [SOLVED] vif-route/networking-route question
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@gmx.de> 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@lists.xensource.com > 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@lists.xensource.com http://lists.xensource.com/xen-users