Difference between revisions of "VPN via the TUN/TAP device"
(Added to Networking category) |
m (removed redundant header, added some interlinking) |
||
| Line 1: | Line 1: | ||
| − | + | This article describes how to use VPN via the TUN/TAP device inside a [[VE]]. | |
== Kernel TUN/TAP support == | == Kernel TUN/TAP support == | ||
| Line 5: | Line 5: | ||
To allow VE #101 to use the TUN/TAP device the following should be done: | To allow VE #101 to use the TUN/TAP device the following should be done: | ||
| − | Make sure the '''tun''' module has been already loaded on the hardware node: | + | Make sure the '''tun''' module has been already loaded on the [[hardware node]]: |
<pre> | <pre> | ||
# lsmod | grep tun | # lsmod | grep tun | ||
Revision as of 13:38, 26 February 2007
This article describes how to use VPN via the TUN/TAP device inside a VE.
Contents
Kernel TUN/TAP support
OpenVZ supports VPN inside a VE via kernel TUN/TAP module and device. To allow VE #101 to use the TUN/TAP device the following should be done:
Make sure the tun module has been already loaded on the hardware node:
# lsmod | grep tun
If it is not there, use the following command to load tun module:
# modprobe tun
You can also add it into /etc/modules.conf to make sure it will be loaded on every reboot automatically.
Granting VE an access to TUN/TAP
Allow your VE to use the tun/tap device:
# vzctl set 101 --devices c:10:200:rw --save
And create the character device file inside the VE:
# vzctl exec 101 mkdir -p /dev/net # vzctl exec 101 mknod /dev/net/tun c 10 200 # vzctl exec 101 chmod 600 /dev/net/tun
Configuring VPN inside VE
After the configuration steps above are done it is possible to use VPN software working with TUN/TAP inside VE just like on a usual standalone linux box.
The following software can be used for VPN with TUN/TAP:
- Virtual TUNnel (http://vtun.sourceforge.net)
- OpenVPN (http://openvpn.sourceforge.net)
