4 | Patch Release Note |
PCR: 03402 | Module: IPG | Level: 2 |
IP routes deleted from the route cache occasionally caused a fatal error. This issue has been resolved.
PCR: 03405 Module: STREAM | Level: 2 |
The reconnection to the stream printing TCP port failed after a single successful connection was made. This issue has been resolved.
PCR: 03407 | Module: IPG | Level: 3 |
The default for the PROXYARP parameter in the SET IP INTERFACE command for a VLAN interface was OFF. The default is now ON.
PCR: 03410 Module: VLAN, CORE | Level: 3 |
If a patch was running with a major software release, after a VLAN was added at the command line, the VLAN was not shown as UP. This issue has been resolved.
PCR: 03412 | Module: FIREWALL | Level: 3 |
FTP data transfers did not succeed for some types of NAT. Also, the presence of flow control TCP flags meant that some TCP control packets were not recognised. These issues have been resolved.
PCR: 03413 | Module: BGP | Level: 2 |
BGP was updated according to the most recently added route. BGP now updates to reflect the best available route, regardless of when it was added.
PCR: 03415 | Module: FIREWALL | Level: 2 |
When using a policy routing rule, the firewall did not translate the source
IP address of a broadcast packet correctly. This issue has been resolved.
PCR: 03416 | Module: SWI | Level: 3 |
Previously, the ADD SWITCH L3FILTER MATCH command was accepted if the TYPE parameter was not specified. This command now requires the TYPE parameter, and an error message will be returned if the TYPE parameter is not specified.
PCR: 03424 Module: DHCP | Level: 2 |
When static DHCP was set to the first IP address in a range, that range would stay in the Reclaim mode. This issue has been resolved.
PCR: 03426 | Module: IPV6 | Level: 3 |
If the valid and preferred lifetimes of an IPv6 address for a given interface were set to infinity, they were not included in the dynamic configuration. This issue has been resolved.
PCR: 03429 Module: SWI, VLAN | Level: 3 |
The SHOW VLAN command was displaying a port that did not exist. This issue has been resolved.
Patch
