SFOS v19 improves supported SSLVPN concurrent tunnels by 4-5x.
As a result, there is a change in the configuration of SSLVPN IPv4 lease range. SFOS v19 uses IP subnet value, however, earlier versions used IP range and subnet.
Migration will convert the IP range and subnet config from old versions to subnet value in v19.
SSLVPN Global config:
Admin has to update IP lease range from IP address to subnet once after migration to avoid error like "You must enter a network IP address." on global settings update.
On upgrading to SFOS v19, some users may notice that SSL VPN is connecting but resources are not accessible over SSLVPN for the following conditions:
As v19 changes the limited IPv4 lease range to the larger subnet, users who have got the IP addresses outside the limited range will be restricted by Firewall rule to access the resources.
Update the IP host object of limited range to a;sp include the new IP range (subnet).
Alternatively, you can start using system host available for SSLVPN IPv4 lease ##ALL_SSLVPN_RW.
More details on How to configure remote access SSL VPN with Sophos Connect client.
Yes, it's getting updated as we speak.
how can changing DHCP scope from range to mask only improve SSL VPN performance??
Alok said: Migration will convert the IP range and subnet config from old versions to subnet value in v19.
you write, it will migrate based range AND subnet
what will happen to a V18 DHCP Server with lets say 192.168.1.5-192.168.1.10 Mask 255.255.255.224 (/27)
it could be 192.168.1.0/28
Why is this not mentioned in Release notes?? https://docs.sophos.com/releasenotes/index.html?productGroupID=nsg&productID=xg&versionID=19.0
It's not mentioned that Range has been removed. There is only written that something has been added.
Prior to v19 also we use to take subnet mask as input along with IP lease range, which will be used during migration. We are not going to convert range into subnet during migration.
thank you for that extra screenshot. do you think, it would be helpful to add this to release notes?