RE: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-16 Thread Sean Lair
...@cloudstack.apache.org Subject: [DKIM Fail] Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider Hi PL, You can check the ikev2 support in 4.15+ here: https://github.com/apache/cloudstack/pull/4953 I think a generic VPN framework-provider feature is probably what we need (i.e. to let user

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-11 Thread Rohit Yadav
is available on Debian: https://packages.debian.org/buster-backports/openvpn Regards. From: Pierre-Luc Dion Sent: Friday, June 11, 2021 20:10 To: users@cloudstack.apache.org Cc: dev Subject: Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider Just

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-11 Thread Andrija Panic
think a process like this > could > >> be simpler than what we've right now, and the ovpn download+import > workflow > >> would be easier than what we'll get from either strongswan/current or > >> wireguard. While I like the simplicity of wireguard, which is more like &g

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-11 Thread Pierre-Luc Dion
dual VMs (much like setting up >> ssh key) or use something like TailScale. >> >> >> Regards. >> >> >> From: Gabriel Bräscher >> Sent: Friday, June 11, 2021 19:28 >> To: dev >> Cc: users >> Subject:

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-11 Thread Pierre-Luc Dion
h like setting up > ssh key) or use something like TailScale. > > > Regards. > > > From: Gabriel Bräscher > Sent: Friday, June 11, 2021 19:28 > To: dev > Cc: users > Subject: Re: [DISCUSS] Moving to OpenVPN as the remote access VPN pr

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-11 Thread Rohit Yadav
something like TailScale. Regards. From: Gabriel Bräscher Sent: Friday, June 11, 2021 19:28 To: dev Cc: users Subject: Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider I understand that OpenVPN is a great option and far adopted. I am ++1

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-11 Thread Gabriel Bräscher
I understand that OpenVPN is a great option and far adopted. I am ++1 in allowing Users/Admins to choose which VPN provider suits them best; creating an offering (or global settings) that would allow setting which VPN provider will be used would be awesome. I understand that OpenVPN is a great

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-11 Thread Pierre-Luc Dion
Hello, Daan, I agree we should provide capability to select the vpn solution to use, the question would be, should it be a global setting generic for the whole region or per VPC? I think it should be a global setting to reduce the requirement complexity of a region, but per VPC or

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-11 Thread Hean Seng
If thinking of only Site-to-Site VPN , then OpenVPN and WireGuard is no much different , or even current one is gpod. Only only time setup at router. However if considering of Mobile Client, OpenVPN is more complicated. The only concern now is multiple people in the same public IP need to

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-11 Thread Daan Hoogland
This is a potential religious debate, I think it makes the most sense to try and make the provider optional and let the operator or even the end-user decide. I see how this is an extra challenge, but does it make sense? On Thu, Jun 10, 2021 at 10:24 AM Rohit Yadav wrote: > All, > > We've

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-10 Thread Hean Seng
l Message----- > > > From: Rohit Yadav > > > Sent: 10 June 2021 10:25 > > > To: d...@cloudstack.apache.org; users@cloudstack.apache.org > > > Subject: [DISCUSS] Moving to OpenVPN as the remote access VPN provider > > > > > > All, > > > > &

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-10 Thread Stênio Firmino
enVPN, and then a framework later on. > > > > > > > > > > -Original Message- > > From: Rohit Yadav > > Sent: 10 June 2021 10:25 > > To: d...@cloudstack.apache.org; users@cloudstack.apache.org > > Subject: [DISCUSS] Moving to OpenVPN as the remote acce

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-10 Thread Andrija Panic
--Original Message- > From: Rohit Yadav > Sent: 10 June 2021 10:25 > To: d...@cloudstack.apache.org; users@cloudstack.apache.org > Subject: [DISCUSS] Moving to OpenVPN as the remote access VPN provider > > All, > > We've historically supported openswan and nowadays strongswan

RE: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-10 Thread Alex Mattioli
+1 on OpenVPN, and then a framework later on. -Original Message- From: Rohit Yadav Sent: 10 June 2021 10:25 To: d...@cloudstack.apache.org; users@cloudstack.apache.org Subject: [DISCUSS] Moving to OpenVPN as the remote access VPN provider All, We've historically supported openswan

Re: [DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-10 Thread Rudraksh MK
Hey! I’m personally a strong proponent of Wireguard. A couple years back, implementing a S2S or remote-access VPN with WG was complicated and it still is - but there’s definitely more tooling available these days. There are clients for just about every major platform - desktop and mobile. In

[DISCUSS] Moving to OpenVPN as the remote access VPN provider

2021-06-10 Thread Rohit Yadav
All, We've historically supported openswan and nowadays strongswan as the VPN provider in VR for both site-to-site and remote access modes. After discussing the situation with a few users and colleagues I learnt that OpenVPN is generally far easier to use, have clients for most OS and