`brew install openvpn` vs. Tunnelblick for OpenVPN client
According to it's official website:
Tunnelblick is a free, open source graphic user interface
When I used Tunnelblick, it worked flowlessly with MacOS. So I would recommend to go forward to run:
brew cask install tunnelblick
When you choose a software for Mac, if it's included in home brew or home brew cask package list or not is one point to consider. See if it's useful enough or popular enough to be a brew package.
I find the feature comparison from the OpenVPN website quite helpful:
Alternative: OpenVPN open source Tunnelblick program
The open source project has a client for the macOS operating system as well. It is called Tunnelblick and it is less limited in functionality than the OpenVPN Connect Client because it does support the option to connect to multiple OpenVPN servers at the same time. On the other hand, it does miss some features that Connect Client does have as well like Python support for post-auth scripting and other functions that integrate Connect Client with Access Server, like the ability to import connection profiles directly from an Access Server, or the ability to authenticate any valid user on your Access Server and have them connect without having to install a connection profile for each separate user account. This is accomplished on the Connect Client with a universal server-locked profile which is not supported by the OpenVPN GUI program.
This program supports drag and drop to place OpenVPN connection profiles into Tunnelblick. These can be of .conf or .ovpn file extension. You can for example download a user-locked or an auto-login profile from the OpenVPN Access Server web interface, and drag and drop it on the Tunnelblick icon. The tray menu in the system tray will then show you options to use this connection profile – to start or stop the connection. Server-locked profiles are not supported, as mentioned earlier.
This program does support connecting to multiple OpenVPN servers at the same time, but there is a catch. You have to be careful not to implement conflicting routes and subnets when connecting to multiple OpenVPN servers at the same time. Unlike on Windows platform however, you do not need to worry about adding multiple virtual network adapters. These are provisioned automatically.