openvpn | private VPN server | VPN library

I need some suggestions for best practicality, security and maintainability

The scenario is:

• We have a private VPC with some servers,
• We have users that can access server A and A only
• Some users can access A, and B.
• Other only B and so on.

They need to access to theses servers from home and office.

The current idea is having a multiuser OpenVPN server with IPTables blocking access to the servers that the user can't access

Is there another option using AWS tools (VPCs,Security Groups, ACLs, Load Balancers, or others)?

Or other solutions better than this one?

Draw of current arch:

• One boundary server that does the bridge from the open world to the Private VPC (With OpenVpn and IPTables)
• 5 servers inside the private VPC
• 10 Users with different levels of access

Thanks

If I try to execute this code in bash shell will work fine:

I would like to know if it is a good idea to use 16384 bit key length for openvpn CA on pfsense and the main differences between this a 8192bit and a 4096bit. Which is the best of these?

Tech: *Windows * CMD * PyCharm

Desired Behavior: I want to run pycharm main.py

Error:

'pycharm' is not recognized as an internal or external command, operable program or batch file.

What I've tried: I added pycharm to my PATH, restarted my computer

Note: When I run echo %PATH%, I can actually see that PyCharm is the last item of the path!

I have a Compute Engine instance running Ubuntu 20.04 on the Google Cloud Platform.

I want to be able to connect to it over port 102. For this purpose, I opened this port by adding a rule in the 'Firewall' section under 'VPC Network'. The rules are shown below:

This VM instance is running an OpenVPN server with an IP address 10.8.0.1. I want to be able to connect to it from a Windows PC which acts as a VPN client (IP: 10.8.0.3).

I used the following command in Windows PowerShell to check if the port was accessible: Test-NetConnection 10.8.0.1 -Port 102 . The output is as shown below:

As you can see, it is able to ping but not connect via port 102.

I have checked and confirmed that the network rules set on the VPC applies to the VM instance in question, so that shouldn't be the problem. Also, the port 102 has been opened on the Client PC as well. This can be confirmed from the output of nmap -p 102 10.8.0.3 from the Virtual Machine Terminal:

So, why is the VM not reachable over port 102? Any help would be appreciated.

I need to build an Android 9 image which includes some prebuilt APKs (OpenVPNForAndroid, in this specific case).

The APK, downloaded from f-droid, includes some libraries that are loaded dynamically. I've added it to the image with the Android.mk file below; the app is installed and starts normally, but fails when I try to connect with this error:

I am working with the latest Manjaro with the kernel: x86_64 Linux 5.10.15-1-MANJARO.

I am connected to my company network via VPN. For this I use SNX with the build version 800010003.

When I start a Docker container (Docker version 20.10.3, build 48d30b5b32) which should connect to a machine from the company network, I get the following message.

So, I've got an interesting one - Cloudformation allows the use of Mustache templates (via Pystache) to build configuration files via AWS::CloudFormation::Init (They bury this a few paragraphs down, but it's there).

This is useful to me, as I need to write out some of the network details to create a config file for an OpenVPN server. So far, so good.

But here's where it gets tricky - AWS likes CIDR notation (and I need to use the same parameter for AWS resources and for this). But OpenVPN likes to use the older IP Range and Netmask format. I'm currently trying to find a good way to convert this. I can either use CloudFormation functions or try to find a way to do the transformation in Mustache.

I can get the IP Range using a combination of Fn::Select and Fn::Split to pull the first half of the CIDR, but deriving the netmask currently has me stumped.

Example so far

I have a VM running OpenVPN with client-to-client disabled and I need some specific forwarding rules. IP forwarding on the VM is turned on.

The OpenVPN base network is 172.30.0.0/16 and that is further subdivided into /24 subnets with their own rules.

172.30.0.0/24 should have access to all the clients. The rest should not. I have 2 subnets defined at the moment; 172.30.0.0/24 and 172.30.10.0/24.

Following the suggestion at the bottom here; https://openvpn.net/community-resources/configuring-client-specific-rules-and-access-policies/ - I set up my rules as follows;