Sorry, I couldn't answer this at work and my VPN to the server is not working right now so I can't get to my network scripts.
The network-route script is simply xen not using a bridge. The vif-route script is supposed to assign an ip address to the dom0 vif interface attached to the domU. I had to tweak this alittle to work and gave my example in the post. In the domU I created a /etc/sysconfig/network-scripts/ifcfg-eth0 to assign an IP on the same subnet as the vif interface in dom0. To ensure the vif name was consistent I added the vifname parameter in place of the bridge parameter in the config file for the domU.
I searched for and read the python scripts to find the available parameters for the config files since the documentation does not list them all. You have to test though because some of the variables I tried to use didn't work.
I hope this information helps, let me know if you have more questions.
From: Kees Cook [mailto:kees@xxxxxxxxxxx]
Sent: Tuesday, November 08, 2005 10:00 PM
To: Max E Baro
Subject: xen networking
Hi! I saw your post about getting routed networking working on Xen, and
I have been tearing my hair out trying to get it to work. It's the
weirdest damn thing: I can ping, but TCP just totally fails to be
noticed. I can see the packets coming in via tcpdump, but it's like the
kernel is just ignoring them.
Is there any chance you could share with me your host and client network
scripts? I tried what you suggested here:
But still no luck. :(
Kees Cook @outflux.net
Xen-users mailing list