TMS zl Module Release Notes ST.1.2.101122

Known Issues

Release ST.1.1.100226/ST.1.1.100330

■ PR_15088 — The connection for DNS will have a high timeout value in some circumstances

when a customer uses a DNS address object and performs a modification to the address

object content. Customer will see a high timeout when doing show connections and can use

the no connections command to remove any problematic sessions.

■ PR_15293 — A lot of firewall logs are generated for normal management activities. Showing

this log will lead a user to thinking the firewall is blocking legitimate traffic.

■ PR_15471 — The TMS zl Module web browser interface and TMS zl Module CLI have

different validations for custom protocols via services. The TMS zl Module web browser

interface does not allow protocol 0, while NIMv2 and the TMS zl Module CLI do allow

protocol 0 (hopopt). In addition, protocol 0 is displayed as ALL in the TMS zl Module web

browser interface and any in the TMS zl Module CLI. There is also a difference in the way

port range is handled if the start and end range have the same value.

■ PR_15698 — TMS zl Module is not reachable after Management VLAN setup until a ping

from module through gateway. This seems to be a problem with the TMS zl Module not having

its default gateway in its ARP cache and only occurs when there is no traffic going through

the TMS zl Module, but you are attempting to manage it from a remote subnet. It also appears

that sending data through the TMS zl Module (i.e. data traffic that a TMS zl Module would

normally see) corrects the issue as well.

■ PR_40092 — A log message from the FTP-ALG has the source and destination fields

swapped. The log message is:

FTP-PASV cmd response came without request, dropping packet srczone=

INTERNAL src=10.1.5.190 srcport=3303 dstzone=external dst=10.1.30.180

dstport=21 proto=TCP.

The src, srcport and dst, dstport are swapped in this log message.

■ PR_40853 — Log mid=1005 missing srczone and dstzone information.

time="2009-05-21 14:15:05" severity=info pri=6

fw=ProCurve-TMS-zl-Module id=fw_l2l3_attack msg="Reassembly is

currently disabled" srczone=UNKNOWN_ZONE src=88.1.20.151 srcport=0

dstzone=UNKNOWN_ZONE dst=88.1.10.7 dstport=0 proto=TCP subf-

amid=intergritycheck mtype=attack mid=1005

■ PR_41293 — The log message for mid=617 incorrectly reports TCP information for ICMP

packets:

time="2009-06-02 22:20:15" severity=warning pri=5

fw=ProCurve-TMS-zl-Module id=fw_access_control ruleid=10 msg="FW: tcp

sequence number translation failed, packets dropped" srczone=INTERNAL

src=192.0.20.100 dstzone=INTERNAL dst=192.0.10.100 proto=ICMP rcvd=0

rcvdsc=0 sent=36 sentsc=0 srcnatport=0 destnatport=0 destnati-

paddr=0.0.0.0 subfamid=accessdeny mtype=access_control mid=617

srcnatipaddr=0.0.0.0