[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen and OpenVPN


  • To: "Kai Wembacher" <kai@xxxxxxxxxxxxx>
  • From: "Nicholas Lee" <emptysands@xxxxxxxxx>
  • Date: Mon, 14 Aug 2006 10:03:20 +1200
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 13 Aug 2006 15:04:02 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=g95jQ3RarsFLDWpLHq/DM0P8QokG6+cHlyPlU2zPYoObpK23Rvq6pqqGGbQAiFa+Hlvi5iJdXE6UxFSNiVB4HRsBkKk7Iu5WDy6/DMNrk+k582tZAsZJwa/oXll311zRdhqkO6NOadqPPrzKRDC8xfpCeNqjRC6d1EWrFuAFtdk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

This is really something for the openvpn mailing list as Xen doesn't really affect it.

Personally I use the push "route 10.1.0.0 255.255.255.0" command, the make sure the other domUs have the appropriate routing:

        up route add -net 192.168.1.0/24 gw  10.1.0.1
        down route del -net 192.168.1.0/24 gw  10.1.0.1

in /etc/network/interfaces, were 10.1.0.1 is the openvpn server host.

NAT is not really needed in a private network situation.



Nicholas
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.