Allied Telesis 86241-06 PCR Module FR Network affecting No, PCR Module Ipsec Network affecting No

16Patch Release Note

PCR: 02313 Module: IPV6 Network affecting: No

The SHOW IPV6 INTERFACE command now shows the address lifetime aging status that is determined by the DECREMENT parameter in the ADD IPV6 INTERFACE command. The default valid and preferred address lifetimes have been changed to 30 days and 7 days respectively.

PCR: 02320 Module: IPV6 Network affecting: No

The interface address preferred lifetime was not operating correctly. This issue has been resolved.

PCR: 02321 Module: FR Network affecting: No

A fatal error occurred when the command SET FR=0 LMI= was executed if the LMI was already set to ANNEXA, ANNEXB or ANNEXD. This issue has been resolved.

PCR: 02326 Module: IPv6 Network affecting: No

A fatal error occurred when a PING was executed over an IPV6 tunnel that had previously been deleted. Also, packet forwarding with link-local addresses was not working correctly. These issues have been resolved.

PCR: 02327 Module: IPG/FIREWALL Network affecting: No

In some situations, multihomed interfaces caused the Firewall to apply NAT and rules incorrectly when packets were received from a subnet that was not attached to the receiving interface. This issue has been resolved.

PCR: 02328 Module: BGP Network affecting: No

BGP was not sending a withdraw message to a peer for a withdrawn or replaced route when the new best route came from that peer. This issue has been resolved.

PCR: 02330 Module: IPv6 Network affecting: No

A buffer leak was occurring in IPv6 fragmentation. This issue has been resolved.

PCR: 02331 Module: IPG, ETH Network affecting: No

IP is now informed when an Ethernet interface goes up or down, after a 2.5 second delay.

PCR: 02332 Module: IPSEC Network affecting: No

The sequence number extracted from the AH and ESP header was in the wrong endian mode, which caused an FTP error with IPSEC anti-replay. This issue has been resolved.

PCR: 02334 Module: FIREWALL Network affecting: No

It is now possible to set the domain name of the SMTP server to none (0.0.0.0) with the SET FIREWALL POLICY SMTPDOMAIN command, even if a server name has not previously been specified.

Patch 86241-05 for Software Release 2.4.1 C613-10340-00 REV E