TMS zl Module Release Notes ST.1.1.100330

24
Software Fixes in Releases ST.1.0.090213 - ST.1.1.100330
Release ST.1.1.100226
PR_40301 — GRE Tunnel displayed GREv2 Error in tcpdump when attempting to verify
the connectivity with a ping packet.
PR_40313 — When adding a RADIUS server, the administrator can specify a NAS-ID that
accepts a script as input allowing code injection to RADIUS Web interface page.
PR_40319 — In the log file, log entries with the following message IDs may truncate the
username: 1213, 1214, and 1204. Other information, such as the user's IP address and login
time are displayed correctly.
PR_40321 — When a RADIUS authentication fails, the log entry with message ID of 4579
displays the wrong user IP address. The username is displayed correctly
PR_40340 — A trusted administrator is not prevented from adding thousands of RADIUS
server entries in the Web browser interface. The maximum number of RADIUS servers that
can be added is now 10.
PR_40380 — Importing certificates in VPN incorrectly shows the text as Self-signed
certificate rather than IPsec certificate.
PR_40568 — In the Web browser interface for VPN, when retrieving an IPsec certificate
using the same private key as a previous certificate, an error would be returned. Steps to
reproduce:
1. SCEP Server installed and configured.
2. CA was retrieved from SCEP server.
3. Go to VPN-> Certificates -> IPsec Certificates
4. Retrieve an IPsec certificate with Private Key ID: test
5. Try to retrieve another certificate using the same ID for private key : test
6. After waiting 10 seconds a message error is displayed:
The IPsec certificate could not be retrieved within the timeout
Instead of this message, a more appropriate error message is displayed indicating to the user that
the same private key ID cannot be used.
PR_40895 — The Clear DF bit cannot be set for an IPsec policy. When the option Clear DF bit
is selected as DF Bit Handling in Step 4 of IPsec policy wizard, an error message is displayed
saying that this option is invalid
PR_40903 — When an L2TP Policy exists and is disabled, traffic continues passing through
the tunnel. The L2TP Policy must be deleted. L2TP policies were removed as they were no
longer required - IPsec policies provide the needed functionality.