I have been trying to get the networking working via route however can''t get it running. Here is my domU config kernel = "/boot/vmlinuz-2.6.12.6-xen" ramdisk = "/boot/initrd-2.6.12.6-xen.img" memory = 32 name = "vm01" dhcp ="off" vif = [''mac=AA:00:00:18:98:FB, vifname=vm01''] ip="192.168.1.240" netmask="255.255.255.0" gateway="192.168.1.1" extra="selinux=0 elevator=cfq" disk = [''file:/root/xen/centos.4-2.img,sda1,w'', ''file:/root/xen/centos.swap,sda2,w''] root = "/dev/sda1 ro" /etc/sysconfig/network-scripts/ifcfg-eth0 from inside the domU TYPE=Ethernet DEVICE=eth0 BOOTPROTO=static ONBOOT=yes BROADCAST=192.168.1.255 IPADDR=192.168.1.240 NETMASK=255.255.255.0 NETWORK=192.168.1.0 GATEWAY=192.168.1.1 ifconfig from dom0 eth0 Link encap:Ethernet HWaddr 00:08:A1:50:FA:19 inet addr:192.168.1.250 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::208:a1ff:fe50:fa19/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:38535 errors:0 dropped:0 overruns:0 frame:0 TX packets:33891 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2791353 (2.6 MiB) TX bytes:6028533 (5.7 MiB) 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:44 errors:0 dropped:0 overruns:0 frame:0 TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4670 (4.5 KiB) TX bytes:4670 (4.5 KiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:38529 errors:0 dropped:0 overruns:0 frame:0 TX packets:33928 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2907531 (2.7 MiB) TX bytes:6056688 (5.7 MiB) Interrupt:16 Base address:0xa000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:33891 errors:0 dropped:0 overruns:0 frame:0 TX packets:38538 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6028533 (5.7 MiB) TX bytes:2791599 (2.6 MiB) vm01 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet addr:192.168.1.250 Bcast:192.168.1.250 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:38 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:5 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2692 (2.6 KiB) TX bytes:252 (252.0 b) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14264 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1016201 (992.3 KiB) TX bytes:378 (378.0 b) Sorry but i am confused here on how to get this working. Any help would be appreciated. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Anand, I will say how I did it.. however there can be many other ways.. Firstly, remove the bridging.. by commenting in xend-config.sxp.. and instead have these two lines (network-bridge network-nat) (vif-script vif-nat) then.. as you can understand from the vif-nat script it sets up route and masquerade details in the iptables, for a network with 10.0.1.0/24, somewhere hard coded.. so.. You can have a DHCP configured which can dynamically give address on the Vifx.x (in which case the edit the network-nat and vif-nat... and change the variable dhcp=${dhcp:-yes}) or you can have a static IP .. in which case let the variable to as it is (dhcp=${dhcp:-no} in network-nat and vif-nat scripts).. Restart Xend... (Note : On Debian.. the DHCP server doesnt start.. since there are some issues, you have to start it manually by ' start-stop-daemon --start --quiet --pidfile $DHCPDPID --exec /usr/sbin/dhcpd -q $INTERFACES' , so a manuall start would happen only after vifx.x is UP and hence you need to first start the DomU..) Next is the domU config .. kernel = "/root/DIST/boot/vmlinuz-2.6-xenU" memory = 64 vmid=1 name = "xen0" vif = [ 'mac=00:16:3E:00:00:11' ] disk = ['file:/mnt/fedora1.img,sda1,rw','file:/mnt/fedora1.swp,sda2,rw','file:/mnt/fedora2.img,sda3,rw'] dhcp = "dhcp" hostname="xen0.su.qcd.in" root="/dev/sda1 ro" extra="3" (Note : vif = [ '' ] is also sufficient...) boot into domU.. and configure the eth0.. #ifconfig eth0 10.0.1.10 (anything in 10.0.1.0/24 network) Configure the route #route add -net 192.168.0.0/24 gw 10.0.1.128 (since my dom0 is in 192.168.0.0/24) Now move to dom0... configure the routes, I see that the vif-nat adds a wrong route... hence #route add -net 10.0.1.0/24 gw 10.0.1.128 dev vif1.0 (vif1.0 is assumed to be the frontend device for domU's ethernet..) Configure iptables... two way Source Natting.. regards On 2/6/06, Anand Gupta <xen.mails@gmail.com> wrote:> I have been trying to get the networking working via route however can't get > it running. > > Here is my domU config > > kernel = "/boot/vmlinuz-2.6.12.6-xen" > ramdisk = "/boot/initrd-2.6.12.6-xen.img " > memory = 32 > name = "vm01" > dhcp ="off" > vif = ['mac=AA:00:00:18:98:FB, vifname=vm01'] > ip="192.168.1.240" > netmask=" 255.255.255.0" > gateway="192.168.1.1" > extra="selinux=0 elevator=cfq" > disk = ['file:/root/xen/centos.4-2.img,sda1,w', > 'file:/root/xen/centos.swap,sda2,w'] > root = "/dev/sda1 ro" > > /etc/sysconfig/network-scripts/ifcfg-eth0 from inside the > domU > > TYPE=Ethernet > DEVICE=eth0 > BOOTPROTO=static > ONBOOT=yes > BROADCAST=192.168.1.255 > IPADDR=192.168.1.240 > NETMASK=255.255.255.0 > NETWORK=192.168.1.0 > GATEWAY=192.168.1.1 > > ifconfig from dom0 > > eth0 Link encap:Ethernet HWaddr 00:08:A1:50:FA:19 > inet addr:192.168.1.250 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::208:a1ff:fe50:fa19/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:38535 errors:0 dropped:0 overruns:0 frame:0 > TX packets:33891 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2791353 (2.6 MiB) TX bytes:6028533 (5.7 MiB) > > 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:44 errors:0 dropped:0 overruns:0 frame:0 > TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4670 (4.5 KiB) TX bytes:4670 (4.5 KiB) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:38529 errors:0 dropped:0 overruns:0 frame:0 > TX packets:33928 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:2907531 (2.7 MiB) TX bytes:6056688 (5.7 MiB) > Interrupt:16 Base address:0xa000 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:33891 errors:0 dropped:0 overruns:0 frame:0 > TX packets:38538 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:6028533 (5.7 MiB) TX bytes:2791599 (2.6 MiB) > > vm01 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet addr: 192.168.1.250 Bcast:192.168.1.250 > 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:38 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:5 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2692 (2.6 KiB) TX bytes:252 ( 252.0 b) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:14264 errors:0 dropped:0 overruns:0 frame:0 > TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1016201 (992.3 KiB) TX bytes:378 (378.0 b) > > > Sorry but i am confused here on how to get this working. Any help would be > appreciated. > > -- > regards, > > Anand Gupta > > _______________________________________________ > 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
On 2/6/06, Sanjay Upadhyay <glowfriend@gmail.com> wrote:> > Hi Anand, > I will say how I did it.. however there can be many other ways.. > Firstly, remove the bridging.. by commenting in xend-config.sxp.. and > instead > have these two lines > > (network-bridge network-nat) > (vif-script vif-nat) >Thanks Sanjay for the explanation, however i am looking for using network-route and not nat. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Feb 06, 2006 at 11:57:28AM +0530, Anand Gupta wrote:> I have been trying to get the networking working via route however can''t get > it running.You didn''t actually mention at what point it doesn''t work, so here''s my best guess.> Here is my domU config[...]> ip="192.168.1.240" > netmask="255.255.255.0" > gateway="192.168.1.1"[...]> ifconfig from dom0[...]> eth0 Link encap:Ethernet HWaddr 00:08:A1:50:FA:19 > inet addr:192.168.1.250 Bcast:192.168.1.255 Mask:255.255.255.0[...]> vm01 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet addr:192.168.1.250 Bcast:192.168.1.250 Mask:255.255.255.255It seems to me that your virtual network interface (vm01) and external/real network interface (eth0) are on the same subnet (and even have the same address). This doesn''t make sense to me and I don''t see how routing can work like this. Aside from that, if it were to work, your gateway inside domU should probably be 192.168.1.250 or else domU will not be sending outgoing packets to dom0. -- CJ van den Berg mailto:cj@vdbonline.com xmpp:cj@vdbonline.com sip:8918316@sipgate.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/6/06, CJ van den Berg <cj@vdbonline.com> wrote:> > On Mon, Feb 06, 2006 at 11:57:28AM +0530, Anand Gupta wrote: > > I have been trying to get the networking working via route however can''t > get > > it running. > > You didn''t actually mention at what point it doesn''t work, so here''s my > best guess.Sorry. I can''t ping from domU to dom0.> Here is my domU config > [...] > > ip="192.168.1.240" > > netmask="255.255.255.0" > > gateway="192.168.1.1" > [...] > > ifconfig from dom0 > [...] > > eth0 Link encap:Ethernet HWaddr 00:08:A1:50:FA:19 > > inet addr:192.168.1.250 Bcast:192.168.1.255 Mask: > 255.255.255.0 > [...] > > vm01 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > inet addr:192.168.1.250 Bcast:192.168.1.250 Mask: > 255.255.255.255 > > It seems to me that your virtual network interface (vm01) and > external/real > network interface (eth0) are on the same subnet (and even have the same > address). This doesn''t make sense to me and I don''t see how routing can > work > like this. Aside from that, if it were to work, your gateway inside domU > should probably be 192.168.1.250 or else domU will not be sending outgoing > packets to dom0. >I tried to set the gateway inside domU to 192.168.1.250 and still it doesn''t work. As for the same ip address for both interfaces, i was confused myself until i saw a post on the mailing list which mentioned that using the route method copies the ip of the eth0 to the vif<id>.0 . Same was posted in the wiki as well -> http://wiki.xensource.com/xenwiki/XenNetworking P.S. I see my config for the domU has "192.168.1.1" as gateway, i will change that and post results. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ok here are the results. /etc/sysconfig/network-scripts/ifcfg-eth0 from inside the domU TYPE=Ethernet DEVICE=eth0 BOOTPROTO=static ONBOOT=yes BROADCAST=192.168.1.255 IPADDR=192.168.1.240 NETMASK=255.255.255.0 NETWORK=192.168.1.0 GATEWAY=192.168.1.250 Changed the gateway setting in domU config to 192.168.1.250 route -n from inside domU Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.1.250 0.0.0.0 UG 0 0 0 eth0 still can''t ping from domU to dom0. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Feb 06, 2006 at 06:17:21PM +0530, Anand Gupta wrote:> > You didn''t actually mention at what point it doesn''t work, so here''s my > > best guess. > > Sorry. I can''t ping from domU to dom0.[...]> I tried to set the gateway inside domU to 192.168.1.250 and still it doesn''t > work.Probably because dom0 is answering the ping on eth0 because that''s the first route it will find to reply to the address 192.168.1.240. In other words, you are probably missing a route somewhere.> As for the same ip address for both interfaces, i was confused myself until > i saw a post on the mailing list which mentioned that using the route method > copies the ip of the eth0 to the vif<id>.0 . Same was posted in the wiki as > well -> http://wiki.xensource.com/xenwiki/XenNetworkingAh, I read the vif-route script now and I see that it uses proxy_arp. So it does indeed make sense. -- CJ van den Berg mailto:cj@vdbonline.com xmpp:cj@vdbonline.com sip:8918316@sipgate.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Feb 06, 2006 at 06:22:53PM +0530, Anand Gupta wrote:> Ok here are the results.[...]> route -n from inside domU > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 > 0.0.0.0 192.168.1.250 0.0.0.0 UG 0 0 0 eth0 > > still can''t ping from domU to dom0.The route output in dom0 would complete the picture. -- CJ van den Berg mailto:cj@vdbonline.com xmpp:cj@vdbonline.com sip:8918316@sipgate.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/6/06, CJ van den Berg <cj@vdbonline.com> wrote:> > The route output in dom0 would complete the picture. >Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Shouldn''t the vif-route be adding the route in dom0? On 2/6/06, Anand Gupta <xen.mails@gmail.com> wrote:> > On 2/6/06, CJ van den Berg <cj@vdbonline.com> wrote: > > > > The route output in dom0 would complete the picture. > > > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 > eth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 > eth0 > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 > eth0 > >-- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Feb 06, 2006 at 06:58:43PM +0530, Anand Gupta wrote:> Shouldn''t the vif-route be adding the route in dom0?Yes it should. It seems the vif script is not seeing the ip parameter. I suggest you try moving the ip= and gateway= parameters into the vifparameter. (Assuming you''re are running 3.0.1) -- CJ van den Berg mailto:cj@vdbonline.com xmpp:cj@vdbonline.com sip:8918316@sipgate.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/6/06, CJ van den Berg <cj@vdbonline.com> wrote:> > On Mon, Feb 06, 2006 at 06:58:43PM +0530, Anand Gupta wrote: > > Shouldn''t the vif-route be adding the route in dom0? > > Yes it should. It seems the vif script is not seeing the ip parameter. I > suggest you try moving the ip= and gateway= parameters into the vif> parameter. (Assuming you''re are running 3.0.1) >This is what i use in the config file (yes i have 3.0.1) vif = [''mac=AA:00:00:18:98:FB, ip=192.168.1.240, gateway=192.168.1.250, vifname=vm01''] when i try to start the domU, i get the following error: Error: Invalid vif option: gateway Without the gateway option it boots up. Now i can ping dom0 from inside domU. However can''t go beyond dom0. Any ideas ? route -n from dom0 Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.240 0.0.0.0 255.255.255.255 UH 0 0 0 vm01 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 Thanks for the help so far. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Feb 06, 2006 at 07:14:27PM +0530, Anand Gupta wrote:> On 2/6/06, CJ van den Berg <cj@vdbonline.com> wrote: > > On Mon, Feb 06, 2006 at 06:58:43PM +0530, Anand Gupta wrote: > > > Shouldn''t the vif-route be adding the route in dom0? > > > > Yes it should. It seems the vif script is not seeing the ip parameter. I > > suggest you try moving the ip= and gateway= parameters into the vif> > parameter. (Assuming you''re are running 3.0.1) > > This is what i use in the config file (yes i have 3.0.1) > > vif = [''mac=AA:00:00:18:98:FB, ip=192.168.1.240, gateway=192.168.1.250, > vifname=vm01''] > > when i try to start the domU, i get the following error: > > Error: Invalid vif option: gateway > > Without the gateway option it boots up. Now i can ping dom0 from inside > domU. However can''t go beyond dom0. > > Any ideas ?Sorry, my bad. gateway is of course not interface specific. Try this: vif = [''mac=AA:00:00:18:98:FB, ip=192.168.1.240, vifname=vm01''] gateway="192.168.1.250" -- CJ van den Berg mailto:cj@vdbonline.com xmpp:cj@vdbonline.com sip:8918316@sipgate.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/6/06, CJ van den Berg <cj@vdbonline.com> wrote:> > On Mon, Feb 06, 2006 at 07:14:27PM +0530, Anand Gupta wrote: > > On 2/6/06, CJ van den Berg <cj@vdbonline.com> wrote: > > > On Mon, Feb 06, 2006 at 06:58:43PM +0530, Anand Gupta wrote: > > > > Shouldn''t the vif-route be adding the route in dom0? > > > > > > Yes it should. It seems the vif script is not seeing the ip parameter. > I > > > suggest you try moving the ip= and gateway= parameters into the vif> > > parameter. (Assuming you''re are running 3.0.1) > > > > This is what i use in the config file (yes i have 3.0.1) > > > > vif = [''mac=AA:00:00:18:98:FB, ip=192.168.1.240, gateway=192.168.1.250, > > vifname=vm01''] > > > > when i try to start the domU, i get the following error: > > > > Error: Invalid vif option: gateway > > > > Without the gateway option it boots up. Now i can ping dom0 from inside > > domU. However can''t go beyond dom0. > > > > Any ideas ? > > Sorry, my bad. gateway is of course not interface specific. > > Try this: > > vif = [''mac=AA:00:00:18:98:FB, ip=192.168.1.240, vifname=vm01''] > gateway="192.168.1.250" >Yes thats what i am doing. Ping from domU to dom0 works, but can''t go beyond dom0 as i posted earlier. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Feb 06, 2006 at 08:11:44PM +0530, Anand Gupta wrote:> On 2/6/06, CJ van den Berg <cj@vdbonline.com> wrote: > > Try this: > > > > vif = [''mac=AA:00:00:18:98:FB, ip=192.168.1.240, vifname=vm01''] > > gateway="192.168.1.250" > > > > Yes thats what i am doing. Ping from domU to dom0 works, but can''t go beyond > dom0 as i posted earlier.Well then either the routing table in domU is still missing something or proxy_arp is not working properly in dom0. Can you post the domU routing table? -- CJ van den Berg mailto:cj@vdbonline.com xmpp:cj@vdbonline.com sip:8918316@sipgate.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/6/06, CJ van den Berg <cj@vdbonline.com> wrote:> > On Mon, Feb 06, 2006 at 08:11:44PM +0530, Anand Gupta wrote: > > On 2/6/06, CJ van den Berg <cj@vdbonline.com> wrote: > > > Try this: > > > > > > vif = [''mac=AA:00:00:18:98:FB, ip=192.168.1.240, vifname=vm01''] > > > gateway="192.168.1.250" > > > > > > > Yes thats what i am doing. Ping from domU to dom0 works, but can''t go > beyond > > dom0 as i posted earlier. > > Well then either the routing table in domU is still missing something or > proxy_arp is not working properly in dom0. > > Can you post the domU routing table? >route -n from inside domU Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.1.250 0.0.0.0 UG 0 0 0 eth0 As per advise from Patrick, i did the following: In dom0 arp -s 192.168.1.240 00:08:a1:50:fa:19 pub (00:08:a1:50:fa:19 being the mac address for eth0) Now from inside domU i can ping outside dom0. However shouldn''t the vif-route script be doing this automatically ? -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Though this question is not related to the existing thread... still i am posting here. I was going through the vif- scripts in /etc/xen/scripts and find that they have log lines which should be logging information somewhere. However when i look in my /var/log/xend.log (debug enabled), i don''t see those log entries. If it doesn''t log in there, where does it log it then. Confused... -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/6/06, Anand Gupta <xen.mails@gmail.com> wrote:> > I was going through the vif- scripts in /etc/xen/scripts and find that > they have log lines which should be logging information somewhere. However > when i look in my /var/log/xend.log (debug enabled), i don''t see those log > entries. If it doesn''t log in there, where does it log it then. >Ok i found the file. Its /var/log/xen-hotplug.log. Now with the default vif-route script i am seeing this usage: ifdown <device name> usage: ifdown <device name> usage: ifdown <device name> usage: ifdown <device name> usage: ifdown <device name> usage: ifdown <device name> Is this normal ? In the script i see the part with ifdown is ifdown ${vif} Does this mean its not getting called properly during shutdown of the domain ? -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/6/06, Anand Gupta <xen.mails@gmail.com> wrote:> > Ok i found the file. Its /var/log/xen-hotplug.log. >hmm... there was a mistake in my post. The log content is only found in the above file when i remove the priority from the log command. logger: unknown priority name: daemon.ifconfig vm01 192.168.1.250 netmask 255.255.255.255 up. /etc/xen/scripts/vif-route logger: unknown priority name: daemon.ifconfig done, interface up. /etc/xen/scripts/vif-route The above was caused by the following entries in the vif-route script ifconfig ${vif} ${main_ip} netmask 255.255.255.255 up echo 1 >/proc/sys/net/ipv4/conf/${vif}/proxy_arp ipcmd=''a'' log "ifconfig ${vif} ${main_ip} netmask 255.255.255.255 up" Placing the priority of debug back, makes the log entry dissapear :( -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users