What is Verbosity?

Verbosity, as it relates to OpenVPN (and Chameleon), is the amount of data captured in the logs for debugging and troubleshooting purposes. This information is not only useful for our support team in assisting customers with issues, but could also be useful for advanced users in personal debugging endeavors.

The default verbosity level in the VyprVPN app is Log level 3. This is sufficient to capture most critical information. As a general rule, the higher you set the verbosity, the more system resources will be required to record that information. This could result in decreased VPN performance. Therefore, we recommend you only adjust it from the default if necessary, resetting it back to Log level 3 when you finish testing.

You can adjust the verbosity level in the Advanced tab of the VyprVPN desktop apps. An explanation of the different levels of verbosity is below. In addition to it's own information, each level contains information from the previous levels as well.


Log level 0: Only fatal errors are recorded.

Log level 1: Default informational messages, link errors from main event loop, errors from encrypt/decrypt, TLS control channel errors, hostname resolve errors, compression errors, packet replay errors, TCP stream error requiring restart, server import option errors, multi-client server errors, event.[ch] errors, push/pull errors, packet_id persist errors, fragmentation errors, and bad struct alignments.

Log level 2: Data & control channel handshakes, socket and TUN/TAP close, http proxy control packets, struct argv errors.

Log level 3: Low frequency info from tls_session routines, simulated outage info from gremlin module, print message after key generation, routes added and deleted (don't mute), debugging info from TUN/TAP driver, certain restart messages, push/pull info, ifconfig pool info, user/pass auth info, point-to-multipoint low-freq debug info, plugin calls, --management info, arming of scheduled exit, route quota exceeded messages, socket/tun/tap buffer sizes, messages related to --port-share option, and packet filter informational messages.

Log level 4: All parameters on program initiation, options compatibility string, miscellaneous low-frequency debug info, DHCP options binary string, mbuf.[ch] routines, PACKET_TRUNCATION_CHECK, packet filter dropped a packet, point-to-multipoint packet drops, medium frequency multi messages, x509-track attributes on connection, medium frequency init messages, terse MTU info, MD5 hash of option compatibility string, low-freq packet-id debugging info, and medium-freq packet-id debugging info.

Log level 5: Print 'R' or 'W' to stdout for read/write.

Log level 6: TCP/UDP reads/writes (terse), TUN/TAP reads/writes, TAP-Windows driver debug info, and client NAT debug info.

Log level 7: Data channel encryption keys, data channel key source entropy, low frequency info from reliable layer, fragment debugging info, freq win32 I/O debugging info, MTU debugging info, medium-freq multi debugging info, MSS adjustments, adaptive compression state changes, <connection> list info, parms & env vars passed to scripts, routing table and adapter list, verbose route.[ch] output, no TLS state for client, Win32 semaphore waits (low freq), Win32 semaphore waits, test_file() calls, --management debug info, verbose plugin calls, socket.[ch] debugging info, PKCS#11 actions, verbose struct alignment info, PACKET_TRUNCATION_CHECK verbose, PING send/receive messages, port share proxy debug, AUTO_USERID debugging, information on key selection for data channel, parse_line() errors in argv_printf %sc, detailed info from crypto.c routines, packet-id debugging info, packet filter dropped a broadcast packet, and packet filter debugging, must also define PF_DEBUG in pf.h.

Log level 8: Detailed description of each handshake, limited info from tls_session routines, interval.h debugging info, scheduler debugging info, verbose info from gremlin module, detailed info from reliable routines, and detailed info from event waits, debug info from mtcp.c.

Log level 9: Detailed info from TLS routine, compression info, all tun/tcp/udp reads/writes/opens, before/after encryption packet content, when no data channel send-key exists, packet-id persist debugging info, link reads/writes with greater verbosity, TCP stream debug info, win32 I/O debugging info, and PKCS#11 debugging.

Log level 10: Traffic shaper info.

Log level 11: Win32 registry debugging info and OpenSSL locks.

Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request
Powered by Zendesk