On Wed, Dec 29, 2010 at 8:53 PM, Russell Seymour
<russell.seymour@xxxxxxxxxxxxxxxxxxx> wrote:
Good afternoon,
I have a host on which I am running Xen. I have succesfully created a new
guest machine and I can connect to it using routed networking. I am not
able to used bridged due to restrictions with my hosting company.
You can use bridge networking with a custom bridge not connected to
any dom0's eth, and making dom0 a router/firewall for domUs. If you're
familiar with managing router/firewall, this setup is actualy easier
to manage.
One example of such setup is virbr0 created by libvirt (bridge + nat).
This server has a connection to my VPN on interface tap0. I would like to
add another interface to each of my virtual machines on this VPN network
which means that I need to be able to route over the tap0 interface (I
think). However I have not been able to accomplish this and searching
around the internet has not provided me with a complete answer. If anyone
has any pointers on this please can you forward them on?
You can try :
- create a bridge manually on dom0 (call it brtap0 or whatever)
- put tap0 on that bridge (you can use openvpn's --up argument to do
this automatically, see openvpn's manual)
- add another interface on domU's config, but specifically use
"script=vif-bridge" on that vif's definition, and put it on the same
bridge
That way you should be able to use both route and bridge networking.
