Filter
Top Products
Juniper Networks NetScreen Release Notes
ScreenOS 5.0.0r9-FIPS P/N 093-1638-000, Rev. A Page 23 of 42
• 02272 – HTTP and HTTPS packets passed through VPN tunnels more
slowly than expected, sometimes to the point of timing out and causing the
device to continually retransmit the packets.
• 02250 – The device sometimes generated an error when you updated a
device and issued the following command with the following arguments:
set interface tunnel.2 nhtb 10.1.2.5 vpn
• 02206 – An Apple Macintosh running Operating System 9 client using the
HTTP protocol failed to connect to the internet while a Juniper NetScreen-
5GT had AV HTTP scanning enabled.
• 02194 – The get log traffic policy command caused a device to fail when
the device contained more than 15,000 VPN tunnels and received ICMP
traffic.
• 02156 – When you enable Scan-MGR, it prevented access to certain web
pages because during the TCP 3-way handshake, the web server advertised a
window size of 0 to the client, preventing the web page window from opening.
• 02094 – The Address Negate feature had no effect on traffic entering the
device through a VPN tunnel with a VPN tunnel policy applied to it.
• 02052 – NAT Traversal (NAT-T) for IPSec did not behave correctly when
both the initiator and responder were behind NAT devices.
• 01793 – A redundant interface incorrectly learned an ARP when no IP
address was configured for the interface.
• 01657 – A redundant VPN did not fail over with a RTO (Run-Time
Operation) synchronization enabled.
• 02041 – The Juniper NetScreen-5000-specific command unset/set
hardware wdt-reset was incorrectly available on all Juniper Networks
security appliances.
• 02412 – The SNMP Get response values were not correct for the ifInOctets
and ifOutOctets statistics.
4.5 Addressed Issues from ScreenOS 5.0.0r5
None.
4.6 Addressed Issues from ScreenOS 5.0.0r4
This section describes issues that addressed in the ScreenOS 5.0.0r4 release.
• 37070 – The initial configuration wizard in the WebUI required a toggled
checkbox to enable switching the mode of the device back and forth from
NAT Mode to Route Mode.