4 | Patch Release Note |
PCR: 03741 | Module: FIREWALL | Level: 3 |
The maximum number of firewall sessions had decreased since software release 86s-241. This issue has been resolved.
PCR: 03742 | Module: IPV6 | Level: 2 |
Previously, an incorrect source address was used for router advertisements that were sent over an IPv6 tunnel. The source address of the tunnel (specified by the IPADDRESS parameter of the ADD IPV6 TUNNEL command) was used instead of a link local address. This caused an interoperability problem, which has been resolved. Now, if the specified IP address is not a link local address, then a link local address will be created based on the IPv4 tunnel source address and used for router advertisements.
PCR: 03743 | Module: IP | Level: 3 |
If a ping was active and the IP configuration was reset, subsequent pings were sent out the wrong interface. This issue has been resolved.
PCR: 03744 | Module: PING | Level: 3 |
Executing a ping to the IP address 0.0.0.0 did not return an invalid destination address error message. Also, when the TRACE command was executed for local addresses, it timed out after 90 seconds. These issues have been resolved.
PCR: 03764 | Module: IPG | Level: 3 |
The IP multicast counter did not increment when IGMP, DVMRP and PIM packets were transmitted and received. This issue has been resolved.
PCR: 03766 | Module: FIREWALL | Level: 2 |
The firewall denied streaming data using Windows Media Player 9. This issue has been resolved.
PCR: 03779 Module: DHCP | Level: 2 |
The DHCP client was not honouring a subnet option provided by the DHCP server. This issue has been resolved.
PCR: 03783 | Module: IPG | Level: 3 |
The TIMEOUT and SIZE parameters are only valid for the SET IP DNS CACHE command, but no error message was returned if either parameter was specified for the SET IP DNS command. This issue has been resolved.
PCR: 03784 | Module: IPV6 | Level: 3 |
Fragmentation of IPv6 packets now complies with RFC 2460’s requirement to align packet sizes to 8 octets.
PCR: 03788 Module: DHCP | Level: 2 |
The DHCP server did not send a DHCPNAK message when a previously statically assigned IP DHCP entry was again requested by a client. This issue has been resolved.
Patch
