|
|
|
|
|
|
|
| Features in |
|
|
| 34 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S | Rapier i |
| Rapier w | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016662 |
| - | This software release supports the new | - | - | - | - |
| - | - | - |
| - | Y | - | - |
CR00016891 |
|
| of the switch, see “Support for the new |
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00017335 |
|
| on page 92. |
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00017937 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016913 | PPP | - | This enhancement enables the PPPoE client to establish a session promptly | Y | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| after a restart or power cycle. This is done by sending a PPPoE Active |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Discovery Terminate (PADT) frame in response to a frame received with an |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| unknown PPPoE session ID. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00017197 | SSH, User, | - | SSH sessions to the router or switch can now be authenticated via RADIUS. | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
| RADIUS |
| The router or switch attempts to authenticate an SSH user via RADIUS if the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| user to be authenticated is not configured in the local user database and |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| the router or switch has RADIUS configured. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00017395 | Firewall | - | This enhancement enables the firewall to establish accurate MSS | Y | Y | Y | Y |
| Y | Y | - |
| - | - | - | Y |
|
|
| (Maximum Segment Size) values for TCP sessions without using the MTU |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| discovery process. MTU discovery depends on ICMP error packets, so does |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| not work in networks that do not forward ICMP error packets. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| To enable this feature, use the command: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| enable firewall policy=name adjusttcpmss |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The adjusttcpmss parameter enables the firewall to adjust the MSS value |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| stored inside incoming TCP SYN packets, to reflect the lower of the two |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| MTU values on the ingress and egress interfaces. Normally, for example, if |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| a TCP SYN packet arrives from an interface with an MTU of 1500 and leaves |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| on an interface with an MTU of 1000, the MSS inside the SYN packet will |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| remain at 1460. When this feature is enabled, the MSS will be adjusted to |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 960 because the firewall knows that the egress interface has a smaller |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| MTU. Note that the firewall does not change the original MSS value if it is |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| already lower than the values of the ingress and egress interfaces. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| To disable this feature, use the command: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| disable firewall policy=name adjusttcpmss |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This feature is disabled by default. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version