Md Mooktakim Ahmed
2006-Mar-23 23:38 UTC
[Xen-users] network-route and vif-route setup help
Hello, I have a dedicated server with 1and1.co.uk. Worst mistake i made. But i''ve committed to this now. What i have is a dedicated server with centos 4.2 installed. I install Xen 3.0 from the redhat installer. it installs fine. I boot into xen. But i loose my internet connection. It seems 1and1 drops my network whenever the switch sees a MAC address other then my eth0''s MAC address. So bridge network is not possible. I did try network-route and it boots up fine. I still have my internet connection. But the problem is my IP''s. It seems 1and1 won''t sell me a subnet of IP''s. When i want an ip they will give me a random ip. They are not continious range. So thats another problem. The problem with network-route is that there is no documentation (atleast i couldn''t find any). There are some information in the mailing lists. What i want is for each domU''s to have their own public IP''s. i want to install a firewall in dom0 and block everything except ssh. I tried shorewall. i can create an alias interface with an IP that i own. Since there isn''t much howto''s on network-route i don''t exactly know what should go in each domU''s configs. I want to specify an IP for each domU. I also want to set the gateway. my network is a bit strange. My IP is 82.165.27.12 for dom0. but the gateway is 10.255.255.1. the netmask is 255.255.255.255. This works for dom0. But when i try to add the default gatway to 10.255.255.1 on one of the domU i get network is unreachable. I really don''t know what to do here. I would like to be able to run few domU''s. I would appreciate any help. Thank you. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yura Pismerov
2006-Mar-24 00:49 UTC
Re: [Xen-users] network-route and vif-route setup help
Ask them if they could give you a set of IPs from the same subnet. It does not have to be a continuous block, but it has to be a set from 82.165.27/24 (or whatever subnet they use). Then you could assign those IPs as alias interfaces to your primary address (on the NIC), set up your domUs with IPs form gray space (eg. 192.168.xxx.yyy) and try to use 1:1 NAT (via iptables in dom0) from those internal addresses to the public ones. Md Mooktakim Ahmed wrote:> Hello, > > I have a dedicated server with 1and1.co.uk. Worst mistake i made. But i''ve committed to > this now. > What i have is a dedicated server with centos 4.2 installed. > > I install Xen 3.0 from the redhat installer. it installs fine. I boot into xen. But i > loose my internet connection. > > It seems 1and1 drops my network whenever the switch sees a MAC address other then my > eth0''s MAC address. So bridge network is not possible. > > I did try network-route and it boots up fine. I still have my internet connection. But > the problem is my IP''s. > > It seems 1and1 won''t sell me a subnet of IP''s. When i want an ip they will give me a > random ip. They are not continious range. So thats another problem. > > The problem with network-route is that there is no documentation (atleast i couldn''t > find any). There are some information in the mailing lists. > > What i want is for each domU''s to have their own public IP''s. i want to install a > firewall in dom0 and block everything except ssh. > I tried shorewall. > > i can create an alias interface with an IP that i own. > > Since there isn''t much howto''s on network-route i don''t exactly know what should go in > each domU''s configs. I want to specify an IP for each domU. I also want to set the > gateway. > > my network is a bit strange. My IP is 82.165.27.12 for dom0. but the gateway is > 10.255.255.1. the netmask is 255.255.255.255. > This works for dom0. > > But when i try to add the default gatway to 10.255.255.1 on one of the domU i get > network is unreachable. > > I really don''t know what to do here. > I would like to be able to run few domU''s. > I would appreciate any help. > Thank you. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Yuri Pismerov, System Administrator Armor Technologies (Canada) Inc. P: 905 305 1946 (x.3519) http://www.armorware.net Privacy Protection Guaranteed! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Your default route for your 82.x network is a 10.x address? What is the subnet mask of that 82.x network? -- Jason The place where you made your stand never mattered, only that you were there... and still on your feet On Thu, 23 Mar 2006, Md Mooktakim Ahmed wrote:> Hello, > > I have a dedicated server with 1and1.co.uk. Worst mistake i made. But i''ve committed to > this now. > What i have is a dedicated server with centos 4.2 installed. > > I install Xen 3.0 from the redhat installer. it installs fine. I boot into xen. But i > loose my internet connection. > > It seems 1and1 drops my network whenever the switch sees a MAC address other then my > eth0''s MAC address. So bridge network is not possible. > > I did try network-route and it boots up fine. I still have my internet connection. But > the problem is my IP''s. > > It seems 1and1 won''t sell me a subnet of IP''s. When i want an ip they will give me a > random ip. They are not continious range. So thats another problem. > > The problem with network-route is that there is no documentation (atleast i couldn''t > find any). There are some information in the mailing lists. > > What i want is for each domU''s to have their own public IP''s. i want to install a > firewall in dom0 and block everything except ssh. > I tried shorewall. > > i can create an alias interface with an IP that i own. > > Since there isn''t much howto''s on network-route i don''t exactly know what should go in > each domU''s configs. I want to specify an IP for each domU. I also want to set the > gateway. > > my network is a bit strange. My IP is 82.165.27.12 for dom0. but the gateway is > 10.255.255.1. the netmask is 255.255.255.255. > This works for dom0. > > But when i try to add the default gatway to 10.255.255.1 on one of the domU i get > network is unreachable. > > I really don''t know what to do here. > I would like to be able to run few domU''s. > I would appreciate any help. > Thank you. > > > _______________________________________________ > 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
Ralf Steenbock
2006-Mar-24 09:59 UTC
Re: [Xen-users] network-route and vif-route setup help
Hello, Md Mooktakim Ahmed schrieb:>It seems 1and1 drops my network whenever the switch sees a MAC address other then my >eth0''s MAC address. So bridge network is not possible. > >I did try network-route and it boots up fine. I still have my internet connection. But >the problem is my IP''s. > >I had the same problems with my new provider a few days ago. For me it is working when I set echo 1 >/proc/sys/net/ipv4/ip_forward echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp in /etc/xen/scripts/network-route. /etc/xen/scripts/vif-route is unchanged. domUs have to be configured with the public IPs you got from your provider like the following: vif = [ ''ip=your.public.domu.ip'' ] ip="your.public.domu.ip" netmask="your.domu.net.mask" gateway="your.providers.gateway.ip" After restarting you should see a line like the following in the output of "ip r" in your dom0: your.public.domu.ip dev vif1 scope link src your.public.dom0.ip I hope that I did not forget anything. Good luck Ralf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andreas Jellinghaus
2006-Mar-24 10:07 UTC
[Xen-users] Re: network-route and vif-route setup help
Md Mooktakim Ahmed wrote:> I did try network-route and it boots up fine. I still have my internet > connection. But the problem is my IP''s. > > It seems 1and1 won''t sell me a subnet of IP''s. When i want an ip they will > give me a random ip. They are not continious range. So thats another > problem.why? use proxy arp, so your machine accepts the ips on the local interface, and then use point to point configuration with your xen0 ip on all interfaces on xen0 and point to point routes for each xenU''s domain. the xenU would simply have it''s own ip point to point xen0 ip which it would use as default gateway. no need to use networks at all, only point to point stuff. I guess your 1and1 upstream is also some ip with pointopoint config.> my network is a bit strange. My IP is 82.165.27.12 for dom0. but the > gateway is 10.255.255.1. the netmask is 255.255.255.255. > This works for dom0.yes, normal hosting provider config. you only have an ip, and you have a default gateway pointopoint''ed.> But when i try to add the default gatway to 10.255.255.1 on one of the > domU i get network is unreachable.no, the domU needs to use your dem0 ip as gateway in pointopoint fashion. Good luck! Regards, Andreas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi> It seems 1and1 drops my network whenever the switch sees a > MAC address other then my eth0''s MAC address. So bridge > network is not possible.Wrong. First, it should work perfectly as long as only dom0 is up. (dom0 should get the MAC of your peth0.) Then you can use ebtables to rewrite packets on peth0, so that 1and1 only sees ONE MAC. I have done this for 3 IPs: Bridge chain: PREROUTING, entries: 6, policy: ACCEPT -p IPv4 -d $mac -i peth0 --ip-dst $2 -j dnat --to-dst 0:16:3e:0:16:1 -p ARP -d $mac -i peth0 --arp-ip-dst $2 -j dnat --to-dst 0:16:3e:0:16:1 -p IPv4 -d $mac -i peth0 --ip-dst $3 -j dnat --to-dst 0:16:3e:0:16:2 -p ARP -d $mac -i peth0 --arp-ip-dst $3 -j dnat --to-dst 0:16:3e:0:16:2 -p IPv4 -d $mac -i peth0 --ip-dst $4 -j dnat --to-dst 0:16:3e:0:16:3 -p ARP -d $mac -i peth0 --arp-ip-dst $4 -j dnat --to-dst 0:16:3e:0:16:3 Bridge chain: OUTPUT, entries: 0, policy: ACCEPT Bridge chain: POSTROUTING, entries: 6, policy: ACCEPT -p IPv4 -s 0:16:3e:0:16:1 -o peth0 --ip-src $2 -j snat --to-src $mac -p ARP -s 0:16:3e:0:16:1 -o peth0 --arp-ip-src $2 -j snat --to-src $mac -p IPv4 -s 0:16:3e:0:16:2 -o peth0 --ip-src $3 -j snat --to-src $mac -p ARP -s 0:16:3e:0:16:2 -o peth0 --arp-ip-src $3 -j snat --to-src $mac -p IPv4 -s 0:16:3e:0:16:3 -o peth0 --ip-src $4 -j snat --to-src $mac -p ARP -s 0:16:3e:0:16:3 -o peth0 --arp-ip-src $4 -j snat --to-src $mac And I boot my domUs with ip = $2, mac = 00:16:3e:00:16:01 ip = $3, mac = 00:16:3e:00:16:02 ip = $4, mac = 00:16:3e:00:16:03 works perfectly.> my network is a bit strange. My IP is 82.165.27.12 for dom0. > but the gateway is 10.255.255.1. the netmask is 255.255.255.255. > This works for dom0.this is really a bit strange, as the system should have no idea in that case how to reach the gateway. I have simmilar problems, as I also have IPs in different subnets. That means, that in my original setup, every traffic between my doms is going through the providers router. Hence nonsense. But I am going to solve this another way: I will give the dom0 and every domU a second IP in the same 10.x.x.x network. Packets to and from 10.x.x.x will be dropped at peth0. Then I will add routes manually to route the public ip of any dom over the private ip of that dom. The doms can then reach each other over their private AND public ips directly. (And I can attach an tap device using openvpn to connect my own computer to that bridge for administration.) Regards, Steffen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Md Mooktakim Ahmed
2006-Mar-28 21:24 UTC
Re: [Xen-users] network-route and vif-route setup help
Sorry about the delay everyone. I had some email troubles for the last week. its all back to normal now. Jason: The subnet for all my ip''s is 255.255.255.255 Yura Pismerov: If i use 1:1 NAT, then from inside the domU''s i will have to have a different IP''s then outside. i would like to have the same ip''s as outside if thats possible. Andreas Jellinghaus: I never heard of point to point. I don''t know what it is. All the information i could find in google wasn''t too helpful, lots of ppp or PPPoE stuff. I did find it in ifconfig man page though. Is there a howto anywhere? especially with xen? Or maybe you could write a small howto maybe? Steffen Heil: with 1and1 i get disconnect when i start xend. Which means dom0 doesn''t even get a chance to work. So all the domU''s don''t work either. I think xend start the bridge with FFFFFFFFFFFF as MAC and then does a transfer. I think thats what kills the connection. the switch drops the connection whenever it seems a different MAC. I have read about ebtables though. reading as many howto''s on it as i can. Ralf Steenbock: Your reply seems promising. So I''ll paste it here again:> I had the same problems with my new provider a few days ago. For me it > is working when I set > > echo 1 >/proc/sys/net/ipv4/ip_forward > echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp > > in /etc/xen/scripts/network-route. /etc/xen/scripts/vif-route is > unchanged. domUs have to be configured with the public IPs you got from > your provider like the following: > > vif = [ ''ip=your.public.domu.ip'' ] > ip="your.public.domu.ip" > netmask="your.domu.net.mask" > gateway="your.providers.gateway.ip" > > After restarting you should see a line like the following in the output > of "ip r" in your dom0: > > your.public.domu.ip dev vif1 scope link src your.public.dom0.ip > > I hope that I did not forget anything. > Good luck > > Ralfwhat i don''t understand is the "ip r" output. the src part. In the config the src ip address wasn''t specified. So does this get generated automatically? or did you mean public.dom0 for the ip= (not the one in vif)? Once again, thanks to everyone who replied. And sorry for the delay in reply, totally unintentional. On Fri, March 24, 2006 3:52 am, Jason wrote:> Your default route for your 82.x network is a 10.x address? What is the subnet mask of > that 82.x network? > > -- > Jason > The place where you made your stand never mattered, > only that you were there... and still on your feet > > On Thu, 23 Mar 2006, Md Mooktakim Ahmed wrote: > > >> Hello, >> >> >> I have a dedicated server with 1and1.co.uk. Worst mistake i made. But i''ve committed >> to this now. What i have is a dedicated server with centos 4.2 installed. >> >> >> I install Xen 3.0 from the redhat installer. it installs fine. I boot into xen. But i >> loose my internet connection. >> >> It seems 1and1 drops my network whenever the switch sees a MAC address other then my >> eth0''s MAC address. So bridge network is not possible. >> >> I did try network-route and it boots up fine. I still have my internet connection. >> But >> the problem is my IP''s. >> >> It seems 1and1 won''t sell me a subnet of IP''s. When i want an ip they will give me a >> random ip. They are not continious range. So thats another problem. >> >> The problem with network-route is that there is no documentation (atleast i couldn''t >> find any). There are some information in the mailing lists. >> >> What i want is for each domU''s to have their own public IP''s. i want to install a >> firewall in dom0 and block everything except ssh. I tried shorewall. >> >> >> i can create an alias interface with an IP that i own. >> >> Since there isn''t much howto''s on network-route i don''t exactly know what should go >> in each domU''s configs. I want to specify an IP for each domU. I also want to set the >> gateway. >> >> my network is a bit strange. My IP is 82.165.27.12 for dom0. but the gateway is >> 10.255.255.1. the netmask is 255.255.255.255. >> This works for dom0. >> >> >> But when i try to add the default gatway to 10.255.255.1 on one of the domU i get >> network is unreachable. >> >> I really don''t know what to do here. >> I would like to be able to run few domU''s. >> I would appreciate any help. >> Thank you. >> >> >> >> _______________________________________________ >> 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 > > >-- Website: http://www.mooktakim.com email: mma@mooktakim.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Md Mooktakim Ahmed
2006-Mar-28 22:13 UTC
Re: [Xen-users] network-route and vif-route setup help
I just tried what you said below. I''m not sure if its working though. I tried bridging one more time and still disconnected from the network. waiting for 1and1 to reconnect me. But i can access serial console. 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? I will send another email detailing if it worked when my connection was reinstated. Ralf Steenbock:> I had the same problems with my new provider a few days ago. For me it > is working when I set > > echo 1 >/proc/sys/net/ipv4/ip_forward > echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp > > in /etc/xen/scripts/network-route. /etc/xen/scripts/vif-route is > unchanged. domUs have to be configured with the public IPs you got from > your provider like the following: > > vif = [ ''ip=your.public.domu.ip'' ] > ip="your.public.domu.ip" > netmask="your.domu.net.mask" > gateway="your.providers.gateway.ip" > > After restarting you should see a line like the following in the output > of "ip r" in your dom0: > > your.public.domu.ip dev vif1 scope link src your.public.dom0.ip > > I hope that I did not forget anything. > Good luck > > Ralf_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Md Mooktakim Ahmed
2006-Mar-29 00:25 UTC
Re: [Xen-users] network-route and vif-route setup help
I got my connection back. It doesn''t work. -bash-3.00# ifconfig eth0 Link encap:Ethernet HWaddr 00:16:3E:7D:2B:63 inet addr:82.165.37.144 Bcast:82.165.37.144 Mask:255.255.255.255 inet6 addr: fe80::216:3eff:fe7d:2b63/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:756 (756.0 b) 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) and ip r: -bash-3.00# ip r 169.254.0.0/16 dev eth0 scope link if i try to add my own default route: -bash-3.00# ip route replace default via 10.255.255.1 RTNETLINK answers: Network is unreachable and even if i use dom0 as default route: -bash-3.00# ip route replace default via 82.165.27.12 RTNETLINK answers: Network is unreachable I just don''t know what to do now. On Tue, March 28, 2006 11:13 pm, Md Mooktakim Ahmed wrote:> I just tried what you said below. I''m not sure if its working though. I tried bridging > one more time and still disconnected from the network. waiting for 1and1 to reconnect me. > But i can access serial console. > > > 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? > I will send another email detailing if it worked when my connection was reinstated. > > > Ralf Steenbock: > > >> I had the same problems with my new provider a few days ago. For me it >> is working when I set >> >> echo 1 >/proc/sys/net/ipv4/ip_forward echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp >> >> in /etc/xen/scripts/network-route. /etc/xen/scripts/vif-route is unchanged. domUs have >> to be configured with the public IPs you got from your provider like the following: >> >> vif = [ ''ip=your.public.domu.ip'' ] ip="your.public.domu.ip" >> netmask="your.domu.net.mask" gateway="your.providers.gateway.ip" >> >> After restarting you should see a line like the following in the output >> of "ip r" in your dom0: >> >> your.public.domu.ip dev vif1 scope link src your.public.dom0.ip >> >> I hope that I did not forget anything. >> Good luck >> >> >> Ralf >> >-- Website: http://www.mooktakim.com email: mma@mooktakim.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Md Mooktakim Ahmed wrote:> inet addr:82.165.27.12 Bcast:82.165.27.12 Mask:255.255.255.255I doubt your net mask. It''s far more likely that your mask is 255.255.255.0, but only your network provider can specify that for sure. You need to double check your mask. -- Randy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Md Mooktakim Ahmed
2006-Mar-29 06:38 UTC
Re: [Xen-users] network-route and vif-route setup help
Thats is what the netmask they gave me when i asked. On Wed, March 29, 2006 1:44 am, Randy Thelen wrote:> Md Mooktakim Ahmed wrote: > > >> inet addr:82.165.27.12 Bcast:82.165.27.12 Mask:255.255.255.255 > > I doubt your net mask. It''s far more likely that your mask is > 255.255.255.0, but only your network provider can specify that for sure. > > > You need to double check your mask. > > > -- Randy > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >-- Website: http://www.mooktakim.com email: mma@mooktakim.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ralf Steenbock
2006-Mar-29 09:43 UTC
Re: [Xen-users] network-route and vif-route setup help
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@lists.xensource.com http://lists.xensource.com/xen-users
Md Mooktakim Ahmed
2006-Mar-29 18:06 UTC
Re: [Xen-users] network-route and vif-route setup help
Here is the output of my domU: -bash-3.00# ifconfig eth0 Link encap:Ethernet HWaddr 00:16:3E:7D:2B:63 inet addr:82.165.37.144 Bcast:82.165.37.144 Mask:255.255.255.255 inet6 addr: fe80::216:3eff:fe7d:2b63/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:756 (756.0 b) 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) -bash-3.00# ip r 169.254.0.0/16 dev eth0 scope link as you can see the route isn''t correct i don''t think. and i can''t add my own route: -bash-3.00# ip route replace default via 82.165.27.12 RTNETLINK answers: Network is unreachable -bash-3.00# ip route replace default via 10.255.255.1 RTNETLINK answers: Network is unreachable I have edited the network-route file: [root@cyclops ~]# cat /etc/xen/scripts/network-route #!/bin/sh #===========================================================================# Default Xen network start/stop script. # Xend calls a network script when it starts. # The script name to use is defined in /etc/xen/xend-config.sxp # in the network-script field. # # Usage: # # network-route (start|stop|status) {VAR=VAL}* # # Vars: # # netdev The gateway interface (default eth0). # antispoof Whether to use iptables to prevent spoofing (default yes). # #=========================================================================== echo 1 >/proc/sys/net/ipv4/ip_forward echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp I am out of ideas. On Wed, March 29, 2006 10:43 am, Ralf Steenbock wrote:> 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@lists.xensource.com > http://lists.xensource.com/xen-users > > >-- Website: http://www.mooktakim.com email: mma@mooktakim.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mooktakim Ahmed
2006-Mar-30 17:43 UTC
Re: [Xen-users] network-route and vif-route setup help
No one has any idea how to solve this? Md Mooktakim Ahmed wrote:> > Here is the output of my domU: > -bash-3.00# ifconfig > eth0 Link encap:Ethernet HWaddr 00:16:3E:7D:2B:63 > inet addr:82.165.37.144 Bcast:82.165.37.144 > Mask:255.255.255.255 > inet6 addr: fe80::216:3eff:fe7d:2b63/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:756 (756.0 b) > > 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > -bash-3.00# ip r > 169.254.0.0/16 dev eth0 scope link > > as you can see the route isn''t correct i don''t think. and i can''t add my > own route: > -bash-3.00# ip route replace default via 82.165.27.12 > RTNETLINK answers: Network is unreachable > -bash-3.00# ip route replace default via 10.255.255.1 > RTNETLINK answers: Network is unreachable > > > I have edited the network-route file: > [root@cyclops ~]# cat /etc/xen/scripts/network-route > #!/bin/sh > #===========================================================================> # Default Xen network start/stop script. > # Xend calls a network script when it starts. > # The script name to use is defined in /etc/xen/xend-config.sxp > # in the network-script field. > # > # Usage: > # > # network-route (start|stop|status) {VAR=VAL}* > # > # Vars: > # > # netdev The gateway interface (default eth0). > # antispoof Whether to use iptables to prevent spoofing (default yes). > # > #===========================================================================> > echo 1 >/proc/sys/net/ipv4/ip_forward > echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp > > I am out of ideas. > > On Wed, March 29, 2006 10:43 am, Ralf Steenbock wrote: >> 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@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> > > > -- > Website: http://www.mooktakim.com > email: mma@mooktakim.com > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- View this message in context: http://www.nabble.com/network-route-and-vif-route-setup-help-t1333567.html#a3674980 Sent from the Xen - User forum at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Molle Bestefich
2006-Mar-30 17:55 UTC
Re: [Xen-users] network-route and vif-route setup help
Mooktakim Ahmed wrote:> No one has any idea how to solve this?Change the subnet mask ;-). Seriously, 255.255.255.255 sounds odd. The smallest usable subnet is 255.255.255.252. Seeing as the lower IP address in the subnet designates the network itself, and the highest IP in the subnet is per definition the broadcast address, 255.255.255.254 doesn''t seem usable, and 255.255.255.255 certainly doesn''t. I''m not an expert, so take it with a grain of salt. I don''t know what your kernel does with it''s routing tables etc. when you choose 255.255.255.255, and I don''t know if perhaps you''re right and you''ve got the correct subnet mask. But it definitely sounds very odd. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Patrick Wolfe
2006-Mar-30 18:10 UTC
Re: [Xen-users] network-route and vif-route setup help
On Wed, 2006-03-29 at 19:06 +0100, Md Mooktakim Ahmed wrote:> -bash-3.00# ip route replace default via 82.165.27.12 > RTNETLINK answers: Network is unreachableSince you are using netmask 255.255.255.255, you need to route to the device, not to the ip address of the other end. Try: ip route add default dev eth0 -- Patrick Wolfe (pwolfe@employease.com) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mooktakim Ahmed
2006-Mar-30 18:13 UTC
Re: [Xen-users] network-route and vif-route setup help
i believe 255.255.255.255 means itself and thats all. No other hosts. it would mean the broadcast is same as the IP. I just want to be able to use some IP''s (which are not in a row) with my domU. For example, i can start eth0:0 and eth0:1 Can i not assign one of these to a domU? Molle Bestefich wrote:> > Mooktakim Ahmed wrote: >> No one has any idea how to solve this? > > Change the subnet mask ;-). > > Seriously, 255.255.255.255 sounds odd. > The smallest usable subnet is 255.255.255.252. Seeing as the lower IP > address in the subnet designates the network itself, and the highest > IP in the subnet is per definition the broadcast address, > 255.255.255.254 doesn''t seem usable, and 255.255.255.255 certainly > doesn''t. > > I''m not an expert, so take it with a grain of salt. I don''t know what > your kernel does with it''s routing tables etc. when you choose > 255.255.255.255, and I don''t know if perhaps you''re right and you''ve > got the correct subnet mask. But it definitely sounds very odd. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- View this message in context: http://www.nabble.com/network-route-and-vif-route-setup-help-t1333567.html#a3675497 Sent from the Xen - User forum at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Md Mooktakim Ahmed
2006-Mar-30 18:38 UTC
Re: [Xen-users] network-route and vif-route setup help
Should i run this inside the domU? or dom0? I''m guessing domU. On Thu, March 30, 2006 7:10 pm, Patrick Wolfe wrote:> On Wed, 2006-03-29 at 19:06 +0100, Md Mooktakim Ahmed wrote: > >> -bash-3.00# ip route replace default via 82.165.27.12 >> RTNETLINK answers: Network is unreachable >> > > Since you are using netmask 255.255.255.255, you need to route to the > device, not to the ip address of the other end. Try: > > ip route add default dev eth0 > > > -- > Patrick Wolfe (pwolfe@employease.com) > > >-- Website: http://www.mooktakim.com email: mma@mooktakim.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mooktakim Ahmed
2006-Mar-30 19:08 UTC
Re: [Xen-users] network-route and vif-route setup help
Incase the email didn''t go to the mailing list i will send it again. Patrick Wolfe: YOU ARE A GENIUS!!> Since you are using netmask 255.255.255.255, you need to route to the > device, not to the ip address of the other end. Try: > > ip route add default dev eth0So thats what happened. To summerise for everyone else. I have a dedicated server. I can''t use bridged network becuase my ISP drops my network whenever the switch sees an unknown MAC. So route is the way to go. Here''s what i did: modify /etc/xen/xend-config.sxp to make sure these are uncommented: (network-script network-route) (vif-script vif-route) comment our the bridge ones. make sure you have in /etc/xen/scripts/network-route: echo 1 >/proc/sys/net/ipv4/ip_forward echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp Setup your dom0 network like normal. You should set the default gateway. My domU config looks like this (the important parts anyway): vif = [ ''ip=domU_IP_HERE'' ] ip = "domU_IP_HERE" netmask="255.255.255.255" gateway="dom0_gateway" The gateway is the dom0 gateway. setup domU''s network so that it has the domU ip. Then add default gateway: ip route add default dev eth0 I put that line in /etc/sysconfig/network-scripts/ifcfg-eth0 for centos. AND THATS IT!!! and it works. Just ONE LAST question please. If i install shorewall do i need to make any changes? like turn on routing in shorewall.conf etc Please let me know. Also will it effect my domU''s if i install shorewall in my dom0? Thanks to everyone for helping!! -- View this message in context: http://www.nabble.com/network-route-and-vif-route-setup-help-t1333567.html#a3676451 Sent from the Xen - User forum at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Md Mooktakim Ahmed
2006-Mar-30 20:45 UTC
Re: [Xen-users] network-route and vif-route setup help
Just have to setup shorewall now. It seems the default 1 interface config bocks everything to the domU''s i keep getting Destination Host Unreachable errors. Has anyone setup shorwall with network-route before? On Thu, March 30, 2006 8:43 pm, Ralf Steenbock wrote:> Hello, > > >> Patrick Wolfe: YOU ARE A GENIUS!! >> >> >> >>> Since you are using netmask 255.255.255.255, you need to route to the >>> device, not to the ip address of the other end. Try: >>> >>> ip route add default dev eth0 >>> >>> > I just came back home with exactly this idea... but Patrick was faster > than me ;-) > > Congratulations! > > > Cheers > > > Ralf > > > >-- Website: http://www.mooktakim.com email: mma@mooktakim.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users