Juniper Networks | NetScreen Release Notes |
|
|
•01998 – You could not save the set console aux disable command into the device configuration.
•01739 – Ping operations would not work if fast aging out of MAC addresses did not occur when a PC migrated from one Juniper
•01635 – The system failed when an H323 recomputed a UDP checksum; the UDP packet lengths sometimes were too consistent with the IP lengths.
•01584 – If a virtual routing instance acted as the ABR (area border router), then the routing instance did not advertise
•01523 – An OSPF virtual routing instance sometimes unexpectedly dropped routes.
4.2Addressed Issues from ScreenOS 5.0.0r8
•40292 – A potential
•39458 – You could not configure 16 concurrent
•39087 – In certain circumstances, the first attempt to access a TCP application through a Juniper
•38193 – A Juniper
•37933, 37945 – If a number of different attacks entered the Juniper
•36708 – You could not view the traffic logs for a Vsys if you entered the Vsys as a root admin user.
•36670 – You could create more VLANs on a Juniper Networks security appliance than the number of VLANs the device officially supported. However, doing this sometimes caused unexpected results. Refer to the specifications sheet for your NetScreen product to learn how many VLANs it supports.
•36494 – Upon startup, Juniper Networks security appliances using PPPoE sometimes generated a warning message informing that the interface gateway command was invalid. This is a result of the gateway changing
ScreenOS | P/N | Page 13 of 42 |