Viscosity is an OpenVPN client for Mac, providing a rich Cocoa graphical user interface for creating, editing, and controlling VPN connections. Normally, the cmd script will use the information provided above to set appropriate firewall entries on the VPN TUN/TAP interface. Since OpenVPN provides the association between virtual IP or MAC address and the client's authenticated common name, it allows a user-defined script to configure firewall access policies with regard to the client. Viscosity is an OpenVPN client for Mac, featuring a rich Cocoa graphical user interface for creating, editing, and controlling VPN connections. Use Viscosity to easily manage your VyprVPN connections. Viscosity provides a complete OpenVPN solution for Leopard (Mac OS 10.5) and does not require any additional downloads or software. Completely configure connections through a GUI, without knowing how to use the command-line or OpenVPN's configuration. Free and open source Graphical User Interface for OpenVPN that offers quick and easy control of th. Sep 8th 2020, 09:41 GMT. 13,304 downloads; 18.1 MB; Viscosity 1.8.6. An easy to use macOS application that provides you with a rich interface for creating, editing, an. Jul 7th 2020, 12:55 GMT.
- Viscosity 1 7 10 – Graphical User Interface For Openvpn Configuration
- Viscosity 1 7 10 – Graphical User Interface For Openvpn Ubuntu
- Viscosity 1 7 10 – Graphical User Interface For Openvpn Server
windows 8.1 pro viscosity does not connect to Openvpn server
- Posts:1
- Joined: Wed Feb 11, 2015 8:54 am
I do have OpenVPN Connect installed as well and that works fine, and I have tried viscosity before and after installing OpenVPN connect and OpenVPN GUI.
Feb 10 03:50:58: State changed to Connecting
Feb 10 03:50:58: 1.5.3 (1300)
Feb 10 03:50:58: Running on Microsoft Windows 8.1 Pro
Feb 10 03:50:58: No associated network adapter was found, creating one. This process may take up to a minute or two.
Feb 10 03:50:58: State changed to Creating...
Feb 10 03:50:58: Failed to create adapter.
Feb 10 03:50:58: Network adapter created. Proceeding with connection attempt
Feb 10 03:50:58: State changed to Connecting
Feb 10 03:50:58: Bringing up interface...
Feb 10 03:50:58: A dev-node for this connection was not found in the configuration file. Viscosity will attempt to connect without one.
Feb 10 03:50:58: Checking reachability status of connection...
Feb 10 03:51:00: Connection is reachable. Starting connection attempt.
Feb 10 03:51:00: OpenVPN 2.3.6 Windows-MSVC [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Dec 2 2014
Feb 10 03:51:00: library versions: OpenSSL 1.0.1j 15 Oct 2014, LZO 2.06
Feb 10 03:51:04: Control Channel Authentication: using 'C:Program FilesCommon FilesViscosityOpenVPNConfigtlawson1ta.key' as a OpenVPN static key file
Feb 10 03:51:04: Attempting to establish TCP connection with [AF_INET]############:443 [nonblock]
Feb 10 03:51:05: TCP connection established with [AF_INET]############:443
Feb 10 03:51:05: TCPv4_CLIENT link local: [undef]
Feb 10 03:51:05: TCPv4_CLIENT link remote: [AF_INET]############:443
Feb 10 03:51:05: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Feb 10 03:51:06: [OpenVPN Server] Peer Connection Initiated with [AF_INET]############:443
Feb 10 03:51:09: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:26: block-ipv6 (2.3.6)
Feb 10 03:51:09: There are no TAP-Windows adapters on this system. You should be able to create a TAP-Windows adapter by going to Start -> All Programs -> TAP-Windows -> Utilities -> Add a new TAP-Windows virtual ethernet adapter.
Feb 10 03:51:09: State changed to Disconnected
- Posts:992
- Joined: Sun Jan 03, 2010 3:27 am
Either the drivers have no installed correctly or there is a conflict with them. Please try the following:
Uninstall Viscosity
Restart your computer (it is important this is done).
Log back into your computer and disable any other TAP devices (like the standard OpenVPN one)
Disable any AV products for a few minutes.
Reinstall Viscosity and then attempt to connect again.
See how this goes.
Regards,
Eric
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Description
OpenVPN MI GUI is a Windows graphical user interface for the OpenVPN client management interface.
It is based on the OpenVPN GUI by Mathias Sundman (version 1.0.3 from August 2005) which is shipped with OpenVPN, but had large parts of the backend adapted by Boris Wesslowski from Inside Security GmbH, commissioned by Conergy AG.
OpenVPN versions 2.1.x, 2.2.x are supported. OpenVPN 2.3.x too, but not all new features are supported yet.
Purpose
The original OpenVPN GUI encounters the following problems especially in enterprise or high security environments:
- Users have no administrative rights, but unprivileged users do not have enough permissions to add and delete routes.
- The GUI will exit on user logout closing all VPN tunnels and preventing e.g. remote VNC logins by an administrator.
- The OpenVPN service wrapper can start one or more OpenVPN instances with enough rights, but the GUI has no control over them.
- OpenVPN running as a service can not request passwords for certificates or user authentication data from the user directly or through the GUI.
The OpenVPN MI GUI talks to the management interfaces of OpenVPN instances started through the service wrapper and can overcome the above problems.
Differences
The major differences to the original GUI are:
- Handling of OpenVPN clients was replaced with management interface support including port and state auto detection, input reassembly, command queueing, log display, password requests...
- Proxy settings support was removed since it can't be passed on to OpenVPN over the management interface.
- Byte count displays were added to status windows.
startandstopcommand line options were added for batch script use.
Requirements
OpenVPN MI GUI will read but not modify your OpenVPN configuration file(s). The following configuration options are required:
Where the must be different for every configuration file so each instance of OpenVPN can be controlled through it's own port. You can for example start at 1194 and add 1 for every configuration file you add.
Additionally, using auth-nocache is recommended, or you may want to consider using management-forget-disconnect and management-signal.
Only the management option is actually required, if neither user authentication nor certificate passwords are in use you may omit the rest, including the management-hold option.
Viscosity 1 7 10 – Graphical User Interface For Openvpn Configuration
Like the original GUI the MI GUI can be configured on the command line or with global registry settings which must be initialized by an administrator.
Known issues
If OpenVPN configuration files are added, removed or changed while the MI GUI is running it may run into an inconsistent state. Since in such cases the OpenVPN service wrapper has to be restarted to activate the changes an additional restart of the MI GUI is usually not necessary.
When an OpenVPN instance exits the OpenVPN service wrapper will still be running and will not restart the missing instance. The OpenVPN MI GUI tries to avoid this, but cases remain where it can happen. The missing cancel button in the user authentication dialog is an example of a workaround of a case where OpenVPN would exit.
Using management-forget-disconnect with OpenVPN version 2.1.x will lead to problems due to a known bug in the included pkcs11-helper.
At system boot the MI GUI may be started before the OpenVPN service is running, this will trigger an error message.
The OpenVPN service may also be unavailable after the system was in standby or suspend mode. You may want to use the do_not_check_service option and NSSM to handle this case.
Screenshots
Viscosity 1 7 10 – Graphical User Interface For Openvpn Ubuntu
Minimal setup with 1 configuration and disabled configuration edit menu item on Windows XP:
Setup with 10 configurations, change password feature and OpenVPN service control menu on Windows 7 (1 active connection):
Status and user authentication windows on Windows 7:
Download
OpenVPN MI GUI consists of a single executable file.
The OpenVPN MI GUI talks to the management interfaces of OpenVPN instances started through the service wrapper and can overcome the above problems.
Differences
The major differences to the original GUI are:
- Handling of OpenVPN clients was replaced with management interface support including port and state auto detection, input reassembly, command queueing, log display, password requests...
- Proxy settings support was removed since it can't be passed on to OpenVPN over the management interface.
- Byte count displays were added to status windows.
startandstopcommand line options were added for batch script use.
Requirements
OpenVPN MI GUI will read but not modify your OpenVPN configuration file(s). The following configuration options are required:
Where the must be different for every configuration file so each instance of OpenVPN can be controlled through it's own port. You can for example start at 1194 and add 1 for every configuration file you add.
Additionally, using auth-nocache is recommended, or you may want to consider using management-forget-disconnect and management-signal.
Only the management option is actually required, if neither user authentication nor certificate passwords are in use you may omit the rest, including the management-hold option.
Viscosity 1 7 10 – Graphical User Interface For Openvpn Configuration
Like the original GUI the MI GUI can be configured on the command line or with global registry settings which must be initialized by an administrator.
Known issues
If OpenVPN configuration files are added, removed or changed while the MI GUI is running it may run into an inconsistent state. Since in such cases the OpenVPN service wrapper has to be restarted to activate the changes an additional restart of the MI GUI is usually not necessary.
When an OpenVPN instance exits the OpenVPN service wrapper will still be running and will not restart the missing instance. The OpenVPN MI GUI tries to avoid this, but cases remain where it can happen. The missing cancel button in the user authentication dialog is an example of a workaround of a case where OpenVPN would exit.
Using management-forget-disconnect with OpenVPN version 2.1.x will lead to problems due to a known bug in the included pkcs11-helper.
At system boot the MI GUI may be started before the OpenVPN service is running, this will trigger an error message.
The OpenVPN service may also be unavailable after the system was in standby or suspend mode. You may want to use the do_not_check_service option and NSSM to handle this case.
Screenshots
Viscosity 1 7 10 – Graphical User Interface For Openvpn Ubuntu
Minimal setup with 1 configuration and disabled configuration edit menu item on Windows XP:
Setup with 10 configurations, change password feature and OpenVPN service control menu on Windows 7 (1 active connection):
Status and user authentication windows on Windows 7:
Download
OpenVPN MI GUI consists of a single executable file.
There are two variants: With and without support for changing the password of PEM and PKCS12 certificates. The one with support should be installed in the bin directory of your OpenVPN installation. The other can run from anywhere.
The latest version is 20160308:
- OpenVPN MI GUI executable: 32-bit (70 kB) / 64-bit (75 kB)
- OpenVPN MI GUI executable with certificate password change support, dynamically linked against OpenSSL: 32-bit (83 kB) / 64-bit (86 kB)
German localization:
- OpenVPN MI GUI auf Deutsch: 32-bit / 64-bit
- OpenVPN MI GUI auf Deutsch, mit Unterstützung für Passwortänderung von Zertifikaten, dynamisch gegen OpenSSL gebunden: 32-bit / 64-bit
Czech localization: 32-bit / 64-bit / chpw 32-bit / chpw 64-bit
Italian localization: 32-bit / 64-bit / chpw 32-bit / chpw 64-bit
OpenVPN MI GUI is open source software under the GNU General Public License (GPL).
- OpenVPN MI GUI source code (52 kB)
You can contact the author at bw inside security de.
Changelog
20160308
- Added do_not_check_service option.
- Added italian localization.
20140918
- Added stop_on_exit option and fixed a problem with the stop command.
- Increased possible password size and fixed special character escaping.
- Fixed 64-bit linking to OpenSSL.
- Added czech localization.
20130109
- Moved to MinGW-w64 and added 64-bit support.
20120316
- Fixed a bug in the byte count display beyond 1 GB.
20110902
- Added application manifest to avoid virtualization on Windows 7 and make the program UAC aware.
- Extended 'management ip port' parsing to allow all IPs.
- Included OpenSSL Applink to fix changing passwords with library versions 0.9.8 and newer.
- Increased number of allowed configurations to 25.
20110624
- Added german localization.
Viscosity 1 7 10 – Graphical User Interface For Openvpn Server
20110511
- Initial public release.
Copyright © 2011-2016 Boris Wesslowski, Inside Security GmbH
