|
|
|
|
|
|
|
| Features in |
|
|
| 16 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR400 | AR7x5 | AR7x0S | Rapier i |
| Rapier w | AT8800- |
| x90048- | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016985 | ATM | 2 | If a PPP instance was destroyed after an attached ATM channel had been | Y | - | - | - |
| - | - | - |
| - | - | - | - |
|
|
| modified using the set atm channel command, the router rebooted. The |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| router could also reboot if an ATM channel was deleted under similar |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| circumstances. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00016989 | IPsec | 2 | AlliedWare IPsec would not interoperate with Microsoft Windows Vista | Y | Y | Y | Y |
| Y | Y | - |
| - | - | - | - |
|
|
| VPN clients. This was because Microsoft changed the IPSec behaviour in |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Vista such that Vista's private local IP address is sent as the local |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| identification instead of an FQDN. When an IPSec tunnel between |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| AlliedWare and Vista was brought up, the hosts could not communicate. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. AlliedWare IPsec can now communicate with |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| peers that send their private local IP address as the local identification. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00017081 | Classifier | 2 | The show classifier command did not allow users to display only the | - | - | - | - |
| - | - | - |
| - | Y | Y | - |
|
|
| classifiers that had their IP source address and MAC source address |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| parameters set to dhcpsnooping. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. For example, the command show classifier |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ipsa=dhcpsnooping now displays those classifiers that have their IP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| source address set to dhcpsnooping. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Also, it is no longer possible to create two identical classifiers with DHCP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| snooping parameters. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00017093 | Firewall | 2 | When the router was acting as a firewall and performing DNS relay, it used | Y | Y | Y | Y |
| Y | Y | - |
| - | - | - | Y |
|
|
| the local IP interface private address as the source address for some packets |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| that it sent out the public interface. When the router acts as a DNS relay, it |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| receives DNS requests from the private interface and sends a new packet |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| on the public interface. These new packets were given the wrong address. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. Such packets now have their source address |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| set to the public interface address as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version