Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am curious about VPNs, whether I need one, how hard it would be to set up, &c. So far I have found nothing. Im using Slackware64 14.1 and I would appreciate any suggestions. TY.
The key notion of VPN, versus other crypto strategies, is that its presence is transparent to operating-system users and their applications. The VPN connection appears as a router "just like any other," and it is accessed as though it were a physical device at some local IP-address. But, it isn't. All traffic routed through it to the remote subnet is encrypted. Once the so-called "tunnel" is established, you simply use it.
OpenVPN is a very nice system, readily available on all operating-systems and platforms. I like it because (a) it uses "SSL-style" authentication, and (b) because it runs as a user-land process, relying on the host operating system only to provide "tunnel" or "tap" virtual network interfaces.
When, you, instead, try to rely upon the "IPSec" stacks that are built-in to this or that operating system, you are rather at the mercy of both operating-system implementation teams. With OpenVPN, "one copy of OpenVPN is talking to a copy of itself," and the OSes each have only a very small, ancillary, part to play.
The only important thing to remember about VPN is ... "do it the right way." That is to say, use digital certificates, not "pre-shared secrets == passwords."
Although, like all crypto, VPN can be nigglingly annoying to set up the first time, once set up it is tremendously convenient. The VPN acts as a virtual, secure, gateway to a remote network of your choosing. You, and your client software, don't have to consciously think about the cryptographic security that is transparently going on. Anyone can connect to anything (if the rules of the VPN connection allow it), without having to do anything special on their part to secure the communications.
Last edited by sundialsvcs; 04-14-2016 at 12:34 PM.
In a nutshell a Virtual Private Network (VPN) is a way to tie computers or discrete networks together over the internet. The typical business case is for an employee to access their work resources from home or join separate office networks together. For the home user it is a way to keep their local communications secure and encrypted. One example would be using free wifi at a cafe or downloading whatever using BitTorrent.
There are free and pay VPNs as well as you can setup your on i.e. OpenVPN as described above. Whether you need one or not depends on what how you use the internet.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.