Juniper Networks | NetScreen Release Notes |
|
|
•02709 – When you set a manual VPN authentication setting to NULL on a Juniper Networks security appliance, the device failed because a Null length is invalid.
•02707 – When performing an
•02699 – When multiple interfaces belonged to different Vsys had the same IP address and subnet mask, VPN traffic to these subnets could pass to the wrong Vsys.
•02609 – The primary Juniper
•02694 – ScreenOS did not send discovered SCREEN occurrences to Security Manager when Security Manager imported a configuration from a device.
•02692 – The DIP (Dynamic IP) allocation failed and halted traffic entering the device, requiring the DIP allocation mechanism to be reset every two hours.
•02688 – The CLI provided no maximum value check for BGP hold time entered on a device, incorrectly allowing you to enter any value for the hold time. If the value was greater than the maximum hold time setting of 65,525, the device incorrectly accepted the value, and the output from the get hold- time command incorrectly displayed it as a negative number.
•02687 – Traffic shaping did not work properly when the traffic shaping policies traversed a
•02685 – You could not unset the sql alg using the unset flow
•02679 – Some devices generated multiple logs for information associated with the self log.
•02670 – When a Juniper
•02668 – A VPN tunnel incorrectly displayed two different ESP sequence numbers which are associated with two different ASICs on the Juniper
•02664 – Packets were sent out with the MAC address of the inactive VSI instead of the active VSI address in an
•02663 – You could not manage two of the secondary IP addresses on an interface of the Juniper
•02660 – After importing a CA (Certificate Authority) certificate into a device and then rebooting the device, the device removed the certificate.
ScreenOS | P/N | Page 17 of 42 |