KB45360 - Wildcard * for port range in VPN ACL no longer works in 9.1R16

After upgrading to 9.1R16, certain VPN ACL policies no longer work
Resources that are covered by a wildcard  port number cannot be accessed and the request times out
Resources where the port number is specified, a subnet range is given or a port range works fine
The issue is not present in 9.1R15 or 9.1R14

Example: 
tcp://192.168.2.80:80 = PASS
tcp://192.168.2.80:* = FAIL
tcp://192.168.2.80:70-90 = PASS
tcp://192.168.2.80/24 = PASS

Iptable forwarding rule for resource configured with protocol://ip:* or protocol://ip was not getting added, which was resulting in denying the access to the end resource.

Pulse Secure Engineering team has validated and fixed this issue, which will be available in the upcoming release (9.1R17)