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
   # 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.

Xen-ppc-devel mailing list

Reply via email to