Allied Telesis 86222-25 manual Patch file details for Patch 86222-19 are listed in Table

16Patch Release Note

PCR: 02276 Module: FIREWALL Network affecting: No

The CREATE CONFIG command did not save the SOURCEPORT parameter to the configuration file when the low value of the source port range was set to zero. This issue has been resolved.

PCR: 02287 Module: IPG Network affecting: No

Existing IGMP groups were not deleted when IGMP was disabled globally or on the associated interface. This gave the groups very high timeout values. This issue has been resolved.

PCR: 02299 Module: VRRP Network affecting: No

If a packet with a destination IP address equal to a VRRP IP address was received when the router didn’t own the IP address, (because it didn’t have an interface with that IP address) the router incorrectly tried to forward the packet and send an ICMP “redirect” message to the source. Now, if such a packet is received, it will be discarded and an ICMP “host unreachable” message will be sent to the source.

PCR: 02304 Module: VRRP Network affecting: No

VRRP used the wrong source IP address in ICMP redirects. RFC 2338 states that the source IP address of ICMP redirects should be the IP address that the end host used when making its next hop routing decision. In the case of a packet sent to a VRRP virtual MAC address, this is the primary VRRP IP address associated with the MAC address, provided such a VR exists and is in the master state. This issue has been resolved.

PCR: 02317 Module: IPG Network affecting: No

The SIZE functionality on the IP filter was not working for IP fragmented packets. This issue has been resolved.

Features in 86222-19

Patch file details for Patch 86222-19 are listed in Table 7:

Table 7: Patch file details for Patch 86222-19.

Base Software Release File	86s-222.rez
Patch Release Date	11-Jun-2002
Compressed Patch File Name	86222-19.paz
Compressed Patch File Size	364584 bytes

Patch 86222-19 includes all issues resolved and enhancements released in previous patches for Software Release 2.2.2, and the following enhancements:

PCR: 02018 Module: OSPF Network affecting: No

When OSPF was calculating routes from an AS external LSA and the AS external router had two next hops with different metrics, the router erroneously added two routes instead of one route with the best metric. This issue has been resolved. Also, when the two equal cost routes were on the same IP interface, but to different next hops, the router sent the packets to the wrong MAC address. This issue has been resolved.

Patch 86222-25 for Software Release 2.2.2 C613-10319-00 REV X