IPsec support for Diffie Hellman groups higher than 16 in SG UTM. Group 16 is getting to be a bit weak for todays environment.

I'd be nice if you would include WireGuard in your suite of server-side VPN protocols in your UTM line.

When clients connect via the SSL Remote Access VPN, you should have the option to assign IP Addresses via an internal DHCP server and not only from the UTM Virtual IP Pool. This is currently available with PPTP and L2TP over IPsec but not with SSL VPN. Companies need to have more control over the IP addresses and leases assigned to clients that connect via the SSL VPN.

Currently, the Amazon VPC setup does not support the new Transit Gateway in AWS. When you attempt to import via config file or secret key it errors out with a Regex error.

I went up the whole chain of premium support and the GES Engineer let me know it currently isn't supported.

As Transit Gateway is the future of Inter VPC & S2S networking this would be nice to have supported.

We have a large number of VPN users and not a day goes by when I don't get an email from a user claiming they got a new phone and need a new QR code and also they forgot their password so could I just go ahead and reset their account for them? Life would be simpler if there was a Forgot Password option where it would send them a password reset link. The process would also delete their OTP Tokens so they would get a new QR code after resetting their password.

MacOS users with the newest version of Tunnelblick are starting to experience compatibility issues with the current OpenVPN version used by SSL VPN.

Customer is requesting to have restriction for the machine to log in on remote access vpn if it do not have any sophos agent installed on it. For your assistance please

i am getting a lot of rouge traffic trying to connect to my SSL VPN - black listing and white listing IP's, IP ranges or ISP's would be good

i know that it's secure and chances are they will never get in - though all the extra protection helps and if a flaw was ever found in openvpn this would help

We have setup the Sophos UTM from the AWS Marketplace (ver 9.603). We have configured it with MFA access so that when we connect using the VPN clients we need to provide our MFA code. We need to do this every time we connect which can be a bit of a hassle for our VPN users. I would be great if sophos supports session timeouts when connecting with MFA which would allow reconnects within a timeout without having to enter MFA again.

Related support post: https://community.sophos.com/products/unified-threat-management/f/general-discussion/114185/sopohos-utm-mfa-session-timeout/409858#409858

It would be extremely useful to add the possibility to assign a static IP address to clients connecting with VPN SSL. It works with IPsec and L2TP but not with SSL. With a static IP address for each user, we would be able to allow them a specific acces to internal ressources. Thanks.

Would like to see support for IKEv2 in AWS appliance.

Currently there is a limit of 50 configs in OpenVPN GUI.
There are already prereleases of the original OpenVPN GUI which remove those limit and add nested configurations.

I would like to see that in Sophos UTM SSL VPN Client too.

APIPA range over route based VPN

Microsoft have been working on their Intune Solution which includes a way to configure a VPN policy that is deployed. There are a number of "Connections" available from other vendors by Sophos are not present. It would be great if Sophos would create a "UWP VPN plug-in" which will allow us to be able to configure VPN's via this. If using Autopilot in the future too a VPN maybe required if not in the office and this same configuration is used.

The default behaviour of the SSL VPN client is to truncate the log file on OpenVPN startup. Want to have the option to append in stead of truncate.

Currently it's not possible to configure site-2site ipsec Connection with networks which are already configured in static Routing. It doesn't matter if the ipsec Networks are smaller than the static route Networks. The ipsec deamon results in an error message like: "cannot route -- route already in use for "

It should be possible to setup a site-2-site tunnel with subnetwork ranges, which are already configured and covered by a static route.

An option to get a updated DNS Server for Linux VPN Clients. Currently the OpenVPN option only sets the DNS Server for Windows Clients.

possibility to add DNS to every different VPN Users group.