TMS zl Module Release Notes ST.1.1.100330

Software Fixes in Releases ST.1.0.090213 - ST.1.1.100330

Release ST.1.1.100226

■ PR_18145 — In the Web browser interface, if a VLAN is added with an invalid IP address in

the range 224.0.0.0 -254.255.255.255, an error is returned stating: VLAN could not be

added. Failed to add VLAN IP address. but the VLAN is actually added, but not

associated to any zone. In the CLI, the error message only states: Error: Failed to set

VLAN IP address.

■ PR_37988 — Upgrading to an ST.1.1.XXXXXX release from any ST.1.0.YYYYYY release, the

TMS zl Module may report Unknown SW update status even though the software update

is still successful. This issue has been addressed in the ST.1.1.100226 software. As a result,

future updates from an ST.1.1.100226 image to a newer image will not have this issue.

■ PR_38705 — RIP: Connected VLANs are not sent correctly when Ripv1-v2 is set. The TMS

zl Module does not send the connected VLANs to another router (R1), when RIP version has

been set as v1-v2.

■ PR_38775 — Using the Command Line Interface, there is no mechanism to disable PIM

globally. The Web browser interface must be used instead.

Firewall

■ PR_2614/PR_4193 / PR_4276 / PR_16778 — In the Web browser interface, the ability to

see whether IPS is enabled or disabled on an access policy basis was added.

■ PR_11023 — Log messages tracking the login and logout of authenticated users are not

generated by the firewall.

■ PR_11874 — On the Firewall > Access Policy > Unicast page in the Web browser interface,

when adding a policy, there is an advanced tab that allows for limit settings and the valid

range for entries in connections, Kilobytes, packets, and seconds are not listed.

■ PR_12607 — ICMP replay will generate a log entry even when the setting is disabled.

■ PR_40627 — The TFTP ALG wasn't invoked with the allow tftp firewall policy but it is

invoked with the allow any firewall policy.

IPS/IDS

■ PR_3020 — Added the following note to the IPS signature download page to help setup

access policies correctly:

Note: To download signatures there must be an Access Policy that allows TCP/443 access

from Self to the signature server. If using a proxy server, there must be an Access Policy that

allows TCP/proxy-port access from Self to the proxy server.