03.03.2013 Views

6.3.0r10 Release Notes - Juniper Networks

6.3.0r10 Release Notes - Juniper Networks

6.3.0r10 Release Notes - Juniper Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ScreenOS 6.3.0 <strong>Release</strong> <strong>Notes</strong><br />

32<br />

• 547117—Packets were dropped by anti-spoofing screening option on the backup NSRP<br />

firewall.<br />

• 547750—[IPv6] UDP checksum was zero.<br />

• 547943—[NS5000] The increasing CPU4 drop counters affected the MGT3 platform<br />

only.<br />

• 548054—ISG and NS5000 platforms dropped pass-through ESP fragmented packets<br />

with total size around 1700 bytes.<br />

• 548294—When the set flow reverse-route clear always command was configured, the<br />

packet did not get arp resolved and was queued twice.<br />

• 548449—Firewall displayed a Trace dump when get config command was run with<br />

OSPFv3 and IPv6 enabled.<br />

• 549614—Firewall failed when details for a peer gateway in a manual VPN configuration<br />

were accessed.<br />

• 549816—Under certain circumstances, the firewall core dumped and rebooted<br />

unexpectedly.<br />

• 558643—With FIPS enabled, device failed to boot after upgrading to 6.3r5.<br />

Routing<br />

• 441711—RIPv2 failed to advertise routes to the neighbors after few hours of operation<br />

in a hub-and-spoke VPN setup.<br />

• 533910—RIP updates with more than 825 routes were dropped.<br />

• 535615—OSPF neighbor on the VPN tunnel went down when the OSPF neighbor<br />

session was incorrectly formed on the loopback interface rather than the tunnel<br />

interface.<br />

• 543671—BGP peering failed when force-reconnect option was enabled under certain<br />

configuration conditions.<br />

• 544754—Inter-area route was not removed from routing table even though an intra-area<br />

route was learnt and existed in the OSPF database.<br />

Security<br />

• 540983—SYN packet sent to the server by the firewall after triggering the SYN-proxy<br />

had an incorrect checksum.<br />

VoIP<br />

• 530047—SIP ALG was unable to handle the SIP calls that needed cross vsys policy<br />

search.<br />

VPN<br />

• 508798—Firewall utilized very high memory when VPN was configured.<br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!