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.

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

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.

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

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.

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.

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.

Would like to see support for IKEv2 in AWS appliance.

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.

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.

possibility to add DNS to every different VPN Users group.

For example, for WAN 1, I will let sales group to VPN to access certain areas of the network, For WAN 2, I will only let those road warriors to access a more restricted area of the network instead of using 1 WAN link that gets filtered by the UTM level. My previous vendor, Watchguard, do have such function, except that Sophos has a higher throughput.

The HTML5 VPN Portal works for almost all platforms exept iOS. It would be great if you could add support for RDP/VNC connections on iOS devices.

The user portal in the UTM is not able to deliver the complete certificate chain. It is missing intermediate certificate due to which our VPN Portal is categorized B on online SSL Testing websites.

To connect more than one location to a microsoft azure environment it is neccesary to build route based IPsec connections. In future Microsoft azure will be a important solution platform, so many customer will use this solution.

Currently there is no option to add an IP list in allowed ipv4.Network resources. This feature was there in Cyberoam. Post migration to Sophos, it wasnt possible.
Request to add this feature, so that ACL will be more sophisticated at Firewall Level.

It would be good if notifications could include failed VPN connection attempt.

Currently there's no way to isolate specific SSL VPN users in Sophos. While a Firewall rule can be set to access the whole service there isn't a way to allow users A, B & C access from any network but limit user D to only a specific IP or range.

my uses sometime connect but cant access network resources - they try again a couple of hours later and it works

the net says there are issues with windows 10 and these are mostly fixed with openvpn version 2.4

as version 2.4 has just come out it may be worth waiting until 2.4.5 for any bugs to be fixed but to schedule this into the UTM development pipeline