A VPN binds isolated networks with tunnels over the Internet network. A tunnel encrypts and encapsulates network frames.

• frames are hidden (data and header, including routing info)
• encapsulation sets tunnel ends as source and destination
• only traffic volume is visible. But you can send dummy frames

Slitaz can build such tunnels out of the box (without additional packages) with menu system / netbox. You need on remote server:

• a user account
• a ssh access
• pppd launch rights (group rights or setuid bit)
• remote stations know how to route frames to the tunnel (peer is the default router or is running routing protcols such as rip, ospf, …)

• launch system / netbox
• select VPN tab
• fill Peer and update Route(s) fields. Routes are the local area networks on peer side you want to reach. You only need to update Local IP and Remote IP when you create multiple tunnels. They are tunnel end IP points
• click Send Key and enter password
• click Connect

• This tunnel should not be used for real time traffic like VoIP. Based on TCP, the tunnel tries to avoid data loss instead of respecting timing. VoIP should use UDP based tunnels
• Only the Slitaz box can see the remote network. Other stations on the lan can't, until you add your lan routes to peer (assuming Slitaz is the default router or is running routing protcols)

The openssh package is available on the mirror and provides TCP based tunnels:

 # yes y | tazpkg get-install openssh 

See http://www.openbsd.org/cgi-bin/man.cgi?query=ssh&sektion=1#SSH-BASED+VIR…

The openvpn package is available on the mirror:

 # yes y | tazpkg get-install openvpn 

See documentation at http://openvpn.net/

The vpnc package is available on the mirror:

 # yes y | tazpkg get-install vpnc 

See documentation at http://www.unix-ag.uni-kl.de/~massar/vpnc/

SliTaz packages search tool shows every VPN supported by SliTaz: http://pkgs.slitaz.org/search.sh?tags=vpn