Allied Telesis 86222-25 - Manual (Page 7)

Patch 86222-25 For Rapier Switches and AR800 Series Modular Switching Routers 7
Patch 86222-25 for Software Release 2.2.2
C613-10319-00 REV X
Sometimes IP flows were not deleted correctly when both directions of the
flow were in use. This issue has been resolved.
When the TX cable was unplugged from a fibre port the operating status
was incorrectly reported as UP. This issue has been resolved.
When replying to a DHCP REQUEST that had passed through a DHCP
relay, the broadcast bit of DHCP NAK messages was not being set. This
issue has been resolved in accordance with RFC2131.
DVMRP was not updating the downstream forwarding state correctly. This
issue has been resolved.
DHCP policies are no longer stored in alphabetical order in the DYNAMIC
CONFIGURATION script because this did not work when the DHCP
INHERIT parameter was used.
When a static ARP was added to a trunk group, a software restart could
occur. This issue has been resolved.
Features in 86222-23
Patch file details are listed in Table 3.
Patch 86222-23 includes all issues resolved and enhancements released in
previous patches for Software Release 2.2.2, and the following enhancements:
Locally generated ICMP packets, such as unreachable messages, were not
passed out through public interfaces when the packet that caused the
message was not recorded by the firewall. This may occur, for example, if
the packet passed between two public interfaces. This issue has been
resolved.
The ARP cache is now updated when a gratuitous ARP request or reply
packet is received.
PCR: 03040 Module: IPG Network affecting: No
PCR: 03065 Module: SWI Level: 2
PCR: 03067 Module: DHCP Level: 1
PCR: 03080 Module: DVMRP
PCR: 03095 Module: DHCP Level: 2
PCR: 03122 Module: SWI Level: 2
Table 3: Patch file details for Patch 86222-23.
Base Software Release File 86s-222.rez
Patch Release Date 16-Jan-2003
Compressed Patch File Name 86222-23.paz
Compressed Patch File Size 947772 bytes
PCR: 02166 Module: FIREWALL Network affecting: No
PCR: 02491 Module: IPG Network affecting: No