Allied Telesis AR800 Series User Manual
Page 13

Patch 86231-10 For Rapier Switches and AR800 Series Modular Switching Routers
13
Patch 86231-10 for Software Release 2.3.1
C613-10328-00 REV J
The following additional enhancements have been added to this previously
released PCR:
•
The Set STP page now correctly displays the Bridge Priority, and not the
root.
•
The Priority field in the Add STP and Set STP pages now accepts five
characters instead of four.
•
The STP Monitoring page now displays the correct ports in the STP.
•
The STP pages now lock correctly when no ports are selected.
DVMRP hold-down routing was not working correctly. This issue has been
resolved.
Executing the RESET IP command left BGP peers in the DISABLED state.
BGP was not aware when an IP interface changed state and consequently
BGP got out of syncronisation with IPG. Multiple IP Routemap entries
failed if the first entry had a different match type to the following entries.
BGP peer update transmission was not operating correctly. A BGP peer that
was in the ESTABLISHED state would still try to make TCP connections to
its peer. These issues have been resolved.
Some FTP packets handled by the firewall were forwarded with incorrect
sequence numbers, causing FTP sessions to fail. This issue has been
resolved.
When passing 64-bit counters in an SNMP packet, only the lower 32 bits
were passed. Now the full 64 bits of the counter will be returned if all are
required.
The Rapier was not detecting invalid checksums in ICMP echo request
packets. This issue has been resolved. ICMP echo request packets with
invalid checksums are now dropped and the ICMP inErrors and inDiscards
counters are incremented.
Locally generated ICMP messages, that were passed out through a firewall
interface because they were associated with another packet flow, had their
source address changed to that of the associated packet flow and were also
forwarded with incorrect IP checksums. This only occurred when there was
no NAT associated with the packet flow. This issue has been resolved.
The TOS field in IP packets was not being processed by IP POLICY filters
with an identifier greater than 7. This issue has been resolved.
PCR: 02083
Module: OGM/GUI
Network affecting: No
PCR: 02102
Module: DVMRP
Network affecting: No
PCR: 02111
Module: BGP
Network affecting: No
PCR: 02128
Module: FIREWALL
Network affecting: No
PCR: 02150
Module: CORE, SNMP
Network affecting: No
PCR 02151
Module: IPG
Network affecting: No
PCR: 02167
Module: FIREWALL
Network affecting: No
PCR 02172
Module: IPG
Network affecting: No