TMS zl Module Release Notes ST.1.1.100330

23
Software Fixes in Releases ST.1.0.090213 - ST.1.1.100330
Release ST.1.1.100226
Monitor Mode
■ PR_17758 — In monitor mode, when IPS full inspection is turned on and the FTP ALG is
turned off, sending an FTP copy of the startup configuration to the network fails with a
broken pipe error.
High Availability
■ PR_8325 / PR_14916 — When configured for High Availability, the Rebalance button in the
Web browser interface is not needed for an Active/Standby configuration.
■ PR_10844 — When a Participant joins or leaves a cluster, there is very little detail to the log
entries describing these important events and these events must be inferred.
VPN
■ PR_4983 — A Safestrcopy error would sometimes be shown when editing the first page of
an IPsec policy.
■ PR_10767 — When using RADIUS authentication, the field NAS-Identifier is sent for CHAP
and MS-CHAP authentication requests, but not for PAP requests.
■ PR_15755 — In the Web browser interface for VPN, there are twice the number of pages
listed for the IPsec VPN Tunnels Table as necessary. As an example, if there are 9900 IPsec
SAs, reflected in 99 pages of this table, the pages 100-198 are all blank.
■ PR_38218 — Cannot change a bypass or ignore policy to apply with key exchange method
manual. Workaround: Delete the policy and add a new one.
■ PR_38232 — Moving an IPsec policy to another position may not set it in the desired
position. Workaround: Delete the policy and add a new one in the correct position.
■ PR_38238 — A misleading error occurs when importing an invalid certificate file.
■ PR_38849 — A incorrect log entry is generated when logging in with a user authenticated
by a RADIUS server.
■ PR_39123 — In the Web browser interface, a warning is displayed about the lockout of the
management interface even when IPsec policy is disabled.
■ PR_39897 — The allowed RADIUS IP pool range was too small. It was increased to allow
up to 10,200 IP addresses.
■ PR_40292 — When a user has a local account on the TMS zl Module and has an account
with the same name on the RADIUS server, the user will always be authenticated to the local
account and no attempt is made to access the RADIUS server, even if the user name includes
the realm, as in username@domain.