Allied Telesis AR440S Примечание к выпуску - Страница 6
Просмотреть онлайн или скачать pdf Примечание к выпуску для Программное обеспечение Allied Telesis AR440S. Allied Telesis AR440S 14 страниц. 54266-02 patch release note
Печатать страницу
6
Features in 54266-02
PCR: 40621
Module: PING
In previous releases, ping poll commands only required entry of the first
three characters of the Source IP Address (sipaddress) parameter. For
example, add ping poll=1 ip=192.168.2.10 sip=192.168.2.1. Subsequent
releases required entry of the first four parameters. This issue has been
resolved, so that it is once again possible to enter just the first three
characters.
PCR: 40646
Module: OSPF, IPG
For both RIP and OSPF, the router was adding a route with it own IP
address for NEXTHOP address. This issue has been resolved.
PCR: 40658
Module: L2TP
L2TP did not handle a change to its peer's UDP source port. If the tunnel
went through a NAT box and that NAT box was reset, then it was possible
for the remote port to change. L2TP should be able to handle this case and
update the tunnel accordingly. A similar problem occurs when a IPsec
NAT-T session (in transport mode) is re-negotiated. IPsec NAT-T uses port
translation to distinguish between multiple clients behind a NAT box. If the
IPsec session is renegotiated then the translated source port that IPsec
passes to L2TP will change. L2TP must be able to handle this case, if it
doesn't then the session will be lost. This issue has been resolved.
PCR: 40668
Module: FFILE
The router would not respond to the setting of the maxqueueseverity
parameter when configuring logging. This issue has been resolved.
PCR: 40728
Module: IPNAT
When IP NAT was configured, a router reboot could occur if a TCP RST
packet was received in which the ACK flag and at least one other flag had
been set. This issue has been resolved.
Level 3
PCR: 31225
Module: IPG
While the router was set with a CIDR interface address, when it received an
ECHO request with a network broadcast destination address for a class C
network, the router sent the ECHO reply packet. Also, the router forwarded
the ECHO request packet using a broadcast MAC address. These issues
have been resolved.
Patch Release Note
Level: 2
Level: 2
Level: 2
Level: 2
Level: 2
Level: 3
Patch 54266-02
C613-10417-00 Rev B