Patch | 17 |
PCR: 03524 | Module: OSPF, IPG | Level: 2 |
OSPF disabled RIP unless RIP was activated using the SET OSPF RIP command. This issue has been resolved.
PCR: 03532 | Module: FIREWALL | Level: 3 |
Occasionally the TCP connection was terminated early during an IDENT proxy TCP session. This issue has been resolved.
PCR: 03536 | Module: BGP, TCP | Level: 3 |
Outgoing BGP packets did not have the Internet Work control flags set in the IP TOS bits. This issue has been resolved.
PCR: 03537 | Module: BGP | Level: 3 |
BGP was returning incorrect and/or incomplete bgp4AttrPath MIB entry information. This issue has been resolved.
PCR: 03538 | Module: BGP | Level: 2 |
Configuration information was not exported to BGP peers when BGP was disabled and then
PCR: 03543 | Module: IPG | Level: 2 |
When acting as a DNS relay agent, the device restarted after approximately three hours of heavy load. This issue has been resolved.
PCR: 03544 | Module: HTTP, FIREWALL | Level: 3 |
HTTP proxy was not denying an IP address if its corresponding domain name was specified in a filter, or if a domain name was requested and its corresponding IP address was in the filter. This issue has been resolved.
PCR: 03546 | Module: FIREWALL | Level: 2 |
In a dual policy configuration (a LAN policy and a DMZ policy with common WAN interface) where both policies have enhanced NAT, behaviour changed according to which policy was configured first. Traffic received on the WAN interface, where a matching rule existed in the DMZ policy to NAT the traffic through to the DMZ, was not permitted if the DMZ policy was configured first. A deny event was recorded in the LAN policy. The traffic was permitted if the LAN policy was configured first. Also, with the same rule configured when traffic was sent from the LAN interface to the WAN interface, IP traffic through to the DMZ policy did not have NAT applied correctly when the DMZ policy was configured first. An inwards deny event was recorded in the LAN policy. If the LAN policy was configured first this did not occur. Both of these issues have been resolved. In these situations, behaviour is now independent of the order of configuration.
PCR: 03547 Module: DHCP | Level: 3 |
The range of values for the IPMTU parameter in the ADD DHCP POLICY command was set incorrectly in PCR 03465. The correct range is
Patch
