Juniper Networks 500, 5200, 208, 204, 5XT, 5400 manual Addressed Issues from Previous Releases

Juniper Networks NetScreen Release Notes

•01985 – You could not schedule a policy using the WebUI.

•01970 – Under certain circumstances, the Juniper Networks security appliance did not send email alerts.

•01943 – When the DHCP payload (information included with the issuance of an IP address from a DHCP server) exceeded 550 bytes in length, the Juniper Networks security appliance was unavailable to send packets associated with the payload because the DHCP relay mechanism did not accept the packets.

4.7Addressed Issues from Previous Releases

This section describes issues addressed in ScreenOS 5.0.0 release prior to ScreenOS 5.0.0r4.

•37027 – The issue described in security advisory NS#54169 was addressed.

•36935 – You could not reset the Juniper Networks security appliance to factory defaults settings if the NSRD wizard failed to connect the device to the Security Manager server.

•36881 – In certain cases, using the pinhole to reset the Juniper Networks security appliance to factory default settings failed.

•36865 – When a serial interface had no IP address, even if it was in the “UP” state, the routing entry pointing to the serial interface stayed inactive.

•36838 – A device failure could occur if the interface information derived for a non-ip packet and received on a 24FE board is invalid.

•36822 – Entering the get policy CLI command sometimes caused the Juniper Networks security appliance to reboot.

•36819 – Under certain circumstances, IP-Spoof packets were incorrectly flagged and dropped.

•36814 – With dialup user group VPN manually configured proxy-id, it could not be used for bi-directional dial-up vpn policy.

•36773 – In Transparent mode, the IP Address Spoof Protection screen option caused the Juniper Networks security appliance to incorrectly drop packets even if the “Generate Alarms without Dropping Packet” option was enabled.

•36766 – (Juniper NetScreen-5GT only) In transparent mode, during the initial connection attempt where the device had no established route to the destination, initial traffic was dropped on occasion by the device when AV scanning was active.

•36736 – A device configured with DHCP and via a configlet was unable to connect to NSM.

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