Book Image

Troubleshooting OpenVPN

By : Eric F Crist
Book Image

Troubleshooting OpenVPN

By: Eric F Crist

Overview of this book

OpenVPN, the most widely used open source VPN package, allows you to create a secure network across systems, keeping your private data secure. Connectivity and other issues are a pain to deal with, especially if they are impacting your business. This book will help you resolve the issues faced by OpenVPN users and teach the techniques on how to troubleshoot it like a true expert. This book is a one stop solution for troubleshooting any issue related to OpenVPN. We will start by introducing you to troubleshooting techniques such as Packet Sniffing, Log Parsing, and OpenSSL. You will see how to overcome operating system specific errors. Later on, you will get to know about network and routing errors by exploring the concepts of IPv4 and IPv6 networking issues. You will discover how to overcome these issues to improve the performance of your OpenVPN deployment. By the end of the book, you will know the best practices, tips, and tricks to ensure the smooth running of your OpenVPN.
Table of Contents (16 chapters)

Logging options


The best source of information when troubleshooting OpenVPN connection and configuration problems is the log file, whether it is on the server or the client. OpenVPN provides a multitude of logging options, allowing an administrator to best gather the data necessary to resolve a problem. This book may be the first comprehensive guide to what is logged by OpenVPN and how best to respond to the messages in that log.

In order to successfully tune the logging of your OpenVPN client or server, it's important to understand what the available logging options are and what impact they will have on the available troubleshooting data. This section will provide a detailed description of every logging option found in the 2.3.11 release of OpenVPN. The following command defines the file where log data will be written out:

--log file

It is suggested the entire path be included, but if --cd is used, or when applying the option from the command line, it's reasonable to use a relative path...