Juniper Networks 5200, 208, 204, 500, 5XT, 5400 manual Juniper Networks NetScreen Release Notes

Juniper Networks NetScreen Release Notes

•37069 – The configuration wizard option in the WebUI that enables you to skip the wizard screens was not present on the initial wizard screen. This option enables you to go directly to the WebUI login window to enter the device to manage it.

•36669 – When 20,000 or more policies were configured on a Juniper Networks security appliance, you experienced a two- to three-minute delay when scrolling through the Policy List page in the WebUI.

•36939 – The Juniper NetScreen-25 and Juniper NetScreen-50 did not support up to eight VLANs as expected and the Juniper NetScreen-20x did not support up to 32 VLANs as expected.

•02259 – In an Active-Active NSRP configuration, the device did not accept traffic that terminated on the device interface in active mode on a different zone than the one with the source IP zone.

•02211 – The IPSec pass-through operation failed because ScreenOS 5.0.0r3 required an incoming policy to work properly.

•02206 – After the AV waited for HTTP get packets and did not receive them after a few seconds, the CSP sent resets to nodes on both sides of the device.

•02175 – By performing a policy search (a scan of a policy group to locate a specified entry), the device failed because ScreenOS improperly initialized policy counters which keep track of policies, and the search improperly returned a null pointer.

•02160 – When the Anti-Virus scan engine scanned large email messages, the device sometimes failed if the amount of time specified by the SMTP scan timeout elapsed before the amount of email data scanned exceeded the Max Content Size limit.

•02156 – When the AV Scan-MGR option enabled in a policy detected a SYN- ACK packet associated with a site with a window size of zero, the device dropped the packet.

•02153 – When trying to establish a GRE tunnel between two PCs with one connected to the Trust interface and the other to the Untrust interface, using policy-based source NAT, the tunnel failed because a GRE tunnel requires fixed source and destination ports and the policy-based source NAT process changes the port values.

•02148 – The device might fail when Vsys traffic changes to the root sys mod when the traffic is en route to a Mapped IP (MIP) object.

•02145 – When SMTP traffic entered the device and combined with the SMTP rcpt command, it sometimes bypassed the Anti-Virus scanning engine.

•02142 – The SSH_MSG_IGNORE message and SSH-1.99- version string were not handled by ScreenOS.

ScreenOS 5.0.0r9-FIPS P/N 093-1638-000, Rev. A Page 24 of 42