|
|
|
|
|
|
|
| Features in |
|
|
| 10 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S | Rapier i |
| Rapier w | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00007178 | RIPng | 2 | The following issues occurred with RIPng: | Y | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| ■ RIPng dropped requests from peers with non |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ for a solicited response, if the routes did not exist on the device, RIPng |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| returned a metric of 0 for them instead of returning a metric of 16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ RIPng performed |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ■ RIPng used the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| request used a non |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| have also used a non |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| These issues have been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00008847 | Install, MIB | 2 | Previously, the MIB objects configFile and createConfigFile would return the | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| current configuration file, and the MIB object currentConfigFile would |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| return 'no such object'. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The objects configFile and createConfigFile |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| now return the boot configuration file. The object currentConfigFile now |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| returns the current configuration file. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00009473 | Classifier | 2 | The output of the show classifier=number command did not show the | Y | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| protocol number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00010654 | Firewall | 2 | When adding a firewall application rule, it was possible to specify FTP as the | Y | Y | Y | Y |
| Y | Y | - |
| - | - | - | Y |
|
|
| application but not specify the command parameter. This meant that the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| rule would allow all FTP commands through, even if action=deny had |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| been specified. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved by making the command parameter |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| mandatory when the application is specified as FTP. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00010951 | PPP | 2 | If the router or switch received an LCP packet with an unrecognised code, | Y | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| it responded with a CodeReject packet of incorrect length that did not |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| respect the established MRU of the peer. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version