Allied Telesis 86253-07 - Manual (Page 18)

18 SHOW IGMPSNOOPING ROUTERADDRESS Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
If a configuration file had a long file name, the SHOW CONFIG command
displayed the file name using the shortened DOS 8.3 format (where file
names are 8 characters long, with extensions of 3 characters). This issue has
been resolved so that long configuration file names are now displayed using
the DOS 16.3 format (where file names are up to 16 characters long).
When a 4-port ETH PIC card was installed, the output of the SHOW IP
INTERFACE command showed the ETH port as Down, but the link LEDs
on the card were lit. This issue has been resolved. The SHOW command
now shows the correct link status. The link will go down after 90 seconds if
no inbound traffic is received. When inbound traffic is received the link will
come up.
When a tagged port was deleted from a VLAN that was in the default STP,
and the port was then added to the VLAN again, communications were
sometimes not resumed on that port. This issue has been resolved.
ISAKMP did not support the IPSec message option
ID_IPV6_ADDR_SUBNET (RFC 2407, 4.6.2.7). ISAKMP was using the
ID_IPV6_ADDR (RFC 2407, 4.6.2.6) option instead. This issue has been
resolved.
MLD and MLD Snooping accepted MLD Query packets with a hop limit
greater than 1. Duplicate packets were forwarded when the hop limit was
not 1 and the payload was 0::0. This issue has been resolved. MLD and MLD
Snooping now require the hop limit to be 1.
After the SHOW VRRP command was executed, incorrect trigger messages
were entered into the log. This issue has been resolved.
An additional check has been added for unknown GBIC models to
determine if they are copper or fibre.
A fatal error occurred when IPv6 fragmented a packet. Also, when a large
fragmented ICMP echo request packet was received, the reply may not have
been fragmented and so may have exceeded the MTU for the interface it
was sent on. These issues have been resolved.
When BGP imported routes from IP with the ADD BGP IMPORT command,
and there were multiple import choices, the best IP route was not always
imported. This issue has been resolved.
PCR: 03780 Module: INSTALL Level: 3
PCR: 03789 Module: ETH Level: 2
PCR: 03790 Module: SWI Level: 2
PCR: 03798 Module: IKMP Level: 3
PCR: 03801 Module: MLDS Level: 2
PCR: 03806 Module: VRRP Level: 4
PCR: 03809 Module: SWI Level: 2
PCR: 03817 Module: IPV6 Level: 2
PCR: 03826 Module: BGP Level: 2