Virtual private networks (VPNs) are a means for connecting to a remote network and making it look like a local one. This means you can connect to your work location and have full access to resources (if so configured on the work side), such as shared printers, work files, etc. There are a number of VPN products freely available; some are kernel-level like openswan and can be fairly difficult to configure. OpenVPN, available at https://openvpn.net/, doesn't require patching the kernel and can be extremely straightforward. Configuration is more difficult if you want to use a lot of its features, but for a quick client/server VPN, you can be up and running in minutes. . The link for this article located at ZDNet.co.uk is no longer available. . Master the quick configuration of OpenVPN for safe remote network connectivity with simplicity and effectiveness.. OpenVPN, VPN Setup, Remote Access, Network Security, Private Networks. . Benjamin D. Thomas
One often-overlooked requirement of a functioning VPN is DNS. For any host-network or network-network VPN, you will be enabling access to machines that are not available on the Internet at large. Unless you want to access machines only by their IP address, you want to have DNS work cleanly. . The easiest way to accomplish this is to create a new domain name for your internal networks. Let's say our company owns , which we use for our external systems. We could create chicago. and atlanta. as internal domain names. We then would run a DNS server internally to support those domains. The link for this article located at TechTarget.com is no longer available. . Establish a detailed procedure for configuring DNS on internal Linux VPNs to facilitate seamless communication across private networks.. DNS Configuration, Linux VPN Setup, Internal Networking, Domain Name Management. . Benjamin D. Thomas
Get the latest Linux and open source security news straight to your inbox.