Re: [XenPPC] xend and routes
On Dec 8, 2006, at 6:24 PM, poff wrote: We have had a couple network configuration mysteries, (including setting 'network-bridge netdev=eth0') due to CSO usage of eth1 as default/extenal adapter, rather than eth0. Probably the xen scripts would have worked without mods if eth0 1 were swapped... I think the problem is that the bridge favors the default route, so I do not think swapping would work. -JX ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] xend and routes
On Dec 9, 2006, at 4:16 PM, poff wrote: BTW: If you would like to have DomUs to have access to the outside world then you also want to make sure you have ip forwarding turned on: # echo 1 /proc/sys/net/ipv4/ip_forward forever change IP_FORWARD= from no to yes in /etc/sysconfig/ sysctl 'ip forwarding' is not necessary - I think bridging handles DomU packets without involving Dom0 network stack. For CSO the other issue is ip addresses for DomUs - viz 9.2... vs 192.168... are the addresses routable or not? the following reflects my understanding of how things work, wich could be completely wrong, so here goes. you have a machine that has 2 NICs (eth0 and eth1) on 2 Networks (192.x and 9.x). If this machine would like 192.x machines to acces the 9.x network the ip_forwrding is necessary. Using the kernel-bridge you have _extended_ the eth0/192.x to the DomUs so it is no different than if it was another machine hooked into eth0. The default Xen scripts seem to have hooked the bridge onto the default route somehow and things get a little wonky. -JX ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] xend and routes
If this machine would like 192.x machines to acces the 9.x network the ip_forwrding is necessary. Right - I was thinking of DomU access to only 192.x. For machines on 192.x to access 9.x, you need forwarding... ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] xend and routes
I think the problem is that the bridge favors the default route, so I do not think swapping would work. On my victim JS21, eth0 is the default, and xen scripts work as written. However, in this case, DomU accesses the 9.2x network, rather than 192.x ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] xend and routes
If this machine would like 192.x machines to acces the 9.x network the ip_forwrding is necessary. Right - I was thinking of DomU access to only 192.x. For machines on 192.x to access 9.x, you need forwarding... On the other hand... CSO is setup with 192.168.0.1 as router/gateway (on the 'king node', cso3). DomUs in CSO blades would gain access to the outside through the king rather than ip_forwarding on the local blades. (talking w/ M. Banikazemi) ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] xend and routes
BTW: If you would like to have DomUs to have access to the outside world then you also want to make sure you have ip forwarding turned on: # echo 1 /proc/sys/net/ipv4/ip_forward forever change IP_FORWARD= from no to yes in /etc/sysconfig/sysctl 'ip forwarding' is not necessary - I think bridging handles DomU packets without involving Dom0 network stack. For CSO the other issue is ip addresses for DomUs - viz 9.2... vs 192.168... are the addresses routable or not? ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] xend and routes
We have had a couple network configuration mysteries, (including setting 'network-bridge netdev=eth0') due to CSO usage of eth1 as default/extenal adapter, rather than eth0. Probably the xen scripts would have worked without mods if eth0 1 were swapped... ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] xend and routes
cso89:~ # netstat -rn netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 9.2.78.10.0.0.0 255.255.255.255 UH0 0 0 eth0 9.2.78.00.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 9.2.78.10.0.0.0 UG0 0 0 eth0 0.0.0.0 9.2.78.10.0.0.0 UG0 0 0 eth1 The next to last route is bogus and interferes with the proper operation of the machine as far as the network goes. I am not sure what the first route in the list above is all about, but seems strange as well. In any case it was not there before. Not clear how this happened, but can fix the problem by deleting the eth0 gateway, 'route del ...' Multiple gateways occur when a second gateway is added without deleting the original gateway, eg with 'route add gw...' However, in this case, the eth0 should not have been added, as you point-out. ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] xend and routes
I'm no expert on this stuff but I'll give it a try: On Dec 6, 2006, at 1:51 PM, Maria Butrico wrote: Notice that the machine name, cso89 corresponds to ip address 9.2.78.89 and is on eth1. Notice also that there is a default route from the machine, the last one, in the table above. After we start xend this is the network interface table. [snip] vif0.1Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 The vif is usually vifDomID.ethN. The vif that is selected to use is based on the original default route, but things get confused because its the wrong interface then you selected. I believe (completely by inspection) that you want to change the following in xend-config.sxp: (vif-script vif-bridge) to be: (vif-script vif-bridge vif=0) This should force the selection you want and may get the routes correct. BTW: If you would like to have DomUs to have access to the outside world then you also want to make sure you have ip forwarding turned on: # echo 1 /proc/sys/net/ipv4/ip_forward forever change IP_FORWARD= from no to yes in /etc/sysconfig/sysctl -JX ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
