openvpn | OpenVPN is an open source VPN daemon | VPN library

The zip-File contains 2 files:

To resolve this just add this line to gradle.properties:

First that screenshot you provided looks like it is from Power BI Desktop. The on-premises data gateway is unrelated to Power BI Desktop refreshes. So make sure your laptop is connected to OpenVPN when you refresh in Power BI Desktop.

Once you are happy with the report you have built and want to publish it to the Power BI Service you will need to setup an on-premises data gateway so that the scheduled refreshes will be able to talk to your source APIs over OpenVPN. Typically you install the “standard mode” (see the link above for more details) and put it on a Virtual Machine or server which is always running (rather than a laptop which can be shut down at night during the scheduled refresh). But if you don’t need scheduled refresh during hours when your laptop is off, I suppose you could use “personal mode”. Personal mode isn’t recommended generally.

Make sure OpenVPN is connected on the server where the on-premises data gateway software is installed. If this VPN connection disconnects after a few hours then ask your IT team for a better way to get a Virtual Machine which is on the same network as the source API or on a network which has a site-to-site “always connected” type VPN connection.

You will need to install and configure the gateway software, create a data source with credentials for your source API, ensure your user account is a “User” on that gateway data source, then republish the report from Power BI Desktop so it will bind to the gateway data source and use it during refresh.

Currently the username is stored unencrypted. Just decode it as Unicode. This may change in future versions. For encrypted data, the call to Unprotect() would take $entropy as the second argument, not $username.

The second method (datagram with UDP-RECVFROM/UDP-SENDTO) works only in a query/answer mode; a second answer in sequence from the OpenVPN server will not be passed back to the client; and for each query packet a sub process will be forked.

The first method forks a subprocess per "connection" (determined by source port), and - after an initial packet from the client - forwards in both directions. Sub processes will hang "forever", so it is advisable to use the timeout option -T 3600 or so.

The answer lies probably in some kind of security policies in that company.

Maybe their VPN gateway is running an obsolete version of VPN server? Maybe, for the users' UX they're using Java Applet based VPN clients? New browsers don't allow running Java Applets (NPAPI in Firefox was abandoned in 2018).

Why not using other VPN solutions: maybe the cost of implementation (including trainings, auditing, etc) is too high, and the company has mitigated risks in some other ways (for example with strict Internet traffic filtering, allow-lists, Intrusion Detection Systems, etc.)? Maybe there are regulatory limitations, such as FIPS requirement for a VPN solution, which can't be met with popular VPN solutions?

If employees of that company can connect to the Internet without any restrictions (web sites' allow-list) the risk of introducing malware into company LANs is very high while using such outdated browsers. In big companies, such risks are mitigated with additional security controls.

To sum it up: I recommend getting knowledge with that company's internal security policies to get the whole picture.

You can add a more specific route for the IP address that you don't want to go through the VPN and use the net_gateway and vpn_gateway options to specify the gateway for the route.

Here is a minimal example of a pod with OpenVPN client. I used kylemanna/openvpn as a server and to generate a basic client config. I only added two routes to the generated config to make it working. See below: