Allied Telesis AT-WA1104G-10 User Manual
Page 17

Features in 291-08
17
Version 291-10
C613-10488-00 REV G
CR00017226
IPsec
2
If an IPsec tunnel with no encryption (NULL) was negotiated in AlliedWare
over NAT-T, the ESP packets did not contain an RFC 3948 compliant
checksum. This means that some vendors may have discarded packets sent
by the AlliedWare peer over such a tunnel.
This issue has been resolved.
Note the null encryption is useful for debugging the traffic over an IPsec
tunnel and should not be used in a working IPsec solution.
Y
Y
Y
Y
Y
Y
-
-
-
-
-
CR00017227
IPsec
2
An IPSec checksum recalculation error occurred with UDP traffic when the
ESP encapsulation was added.
This issue has been resolved.
Y
Y
Y
Y
Y
Y
-
-
-
-
-
CR00017255
Switching
2
Previously, trunk members were given the STP state in hardware of port 1,
instead of having the STP state of the lead port in the trunk. The software
state (as displayed with the command show stp port) was correct.
This issue has been resolved.
-
-
-
Y
Y
Y
Y
Y
-
-
-
CR00017256
Switching
2
When using multi-homed IP interfaces on a VLAN, it was possible that L3
hardware switching would stop for all multi-homed interfaces on that
VLAN, if one of the multi-homed interfaces was removed or went into an
administratively down state.
This issue has been resolved.
-
-
-
-
-
-
-
-
Y
Y
-
CR00017337
Switching
2
It was possible to set up a classifier that matched MPLS frames at layer 2,
but the switch would not correctly match these MPLS frames against the
classifier.
This issue has been resolved. The switch now correctly matches MPLS
frames against such a classifier.
-
-
-
-
-
-
-
-
Y
Y
-
CR
Module
Level
Description
AR4
00
AR7
x5
AR7
x0S
Rap
ier i
Rap
ier w
AT
-8800
A
T-8
600
A
T-8
700
XL
x900
-48
A
T-
99
00
A
T-9
800