|
|
|
|
|
|
| Features in |
|
|
| 10 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR44x / AR450 | AR7x5 | AR750S |
| Rapier i |
| ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00011855 | TCP, | 2 | TCP sessions would sometimes “hang” in the Close Wait state. This behaviour | Y | Y | Y |
| - | - | - |
| - | - | - | - |
| UPnP |
| occurred when a UPnP notification session was closed by the control point |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (usually Windows XP, SP2), via a “200 OK” message that contained a |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| “Connection: close” field, that also had the TCP/FIN flag set. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Because these TCP sessions were not closing, eventually all available TCP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| resources could be used up, preventing new TCP sessions from opening. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. Such TCP sessions now close correctly. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00011940 | Switch | 2 | Previously, if all configured IP interfaces were down or had been deleted, | - | - | - |
| - | - | - |
| - | Y | Y | - |
|
|
| broadcast frames were not sent to the switch’s CPU. This meant, for example, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| that VLANs on the switch did not receive PPPoE traffic if all IP interfaces were |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| down. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00011991 | WAN load | 2 | An issue occurred when the router accessed multiple WAN load balancer | Y | Y | Y |
| - | - | - |
| - | - | - | - |
| balancer |
| healthcheck hosts, and was configured as a firewall that performed enhanced |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NAT. Instead of testing the health of each healthcheck host through every WAN |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| LB resource (and therefore over all relevant WAN interfaces), the router only |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| tested through one WAN LB resource. If that one WAN interface lost connectivity |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| to the Internet, the WAN LB incorrectly thought that all WAN LB resources had |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| become unavailable. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. The WAN LB now correctly checks the health of all |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| healthcheck hosts through all WAN LB resource interfaces. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00011992 | Firewall | 2 | When the firewall was enabled, it failed to process some RTSP packets, so clients | Y | Y | Y |
| Y | Y | - |
| - | - | - | Y |
|
|
| behind the firewall failed to load some web pages that used RTSP (TCP port |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 7070). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version