Re: [XenPPC] xend and routes

2006-12-11 Thread poff
>> 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

Re: [XenPPC] xend and routes

2006-12-11 Thread poff
> 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

Re: [XenPPC] xend and routes

2006-12-11 Thread poff
> 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-p

Re: [XenPPC] xend and routes

2006-12-11 Thread Jimi Xenidis
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/ sys

Re: [XenPPC] xend and routes

2006-12-11 Thread Jimi Xenidis
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 swap

Re: [XenPPC] xend and routes

2006-12-09 Thread poff
> 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 ne

Re: [XenPPC] xend and routes

2006-12-08 Thread poff
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... __

Re: [XenPPC] xend and routes

2006-12-07 Thread Jimi Xenidis
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. Afte

Re: [XenPPC] xend and routes

2006-12-07 Thread poff
> 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

[XenPPC] xend and routes

2006-12-06 Thread Maria Butrico
We have several JS21, all with two ethernet interfaces, both interfaces in use.For example this is what things look like when we boot one such blade with the latest xen and linux for xen and before starting xend. cso89:~ # ifconfig ifconfig eth0 Link encap:Ethernet HWaddr 00:11:25:C9: