RV016 Firmware v3.0.0.19-tm Release Note

3/21/2009

Changes:

1. Administrative username can be configured on the Setup>Password page.
2. Fixed an issue with intermittent VPN connection.
3. Fixed an issue with logging unauthorized login attempts.
4. Fixed an issue with ProtectLink Gateway service caused by importing an old 
   configuration file.
5. Fixed an issue with verifying the SSL certificate of the ProtectLink Gateway 
   license server. 

6. Fixed a DHCP server issue, where not all DHCP clients in the LAN can get an IP address.
7. Fixed a Dual-WAN Failover issue with SIP.
8. Fixed an issue with invalid Daylight Saving Dates.
9. The source port of DNS queries is now randomized by the NAT.
10. QuickVPN service will limit the maximum number of connection requests - a protection 
    mechanism against Denial of Service (DoS) attack.

11. QuickVPN service will prevent brute-force password attack by a 5-minute timeout 
    following 5 successive password errors within one minute.
12. SSLv2 is disabled for enhanced security.
13. Router will log a message when the ProtectLink URL queue is almost full, warning users 
    that URL blocking might occur if the URL Overflow Control in the ProtectLink>Web Protection 
    page is in the default setting. When the URL queue returns to empty, router will log 
    a message indicating that the temporary URL overflow has disappeared. 
14. Support DMZ Range in addition to the current DMZ Subnet function.


Known Issues:

1. QuickVPN Client v1.2.8 on Windows Vista cannot work properly when the Vista PC uses 
   a wireless adapter to connect to the network. The issue was fixed by QuickVPN Client v1.2.11.

2. Windows Firewall needs to be enabled on Windows Vista in order for QuickVPN Client 
   to function properly. This is due to the fact that IPSec service on Vista is disabled 
   when Windows Firewall is disabled.   

3. QuickVPN Client v1.2.6 on Vista does not work properly when the Server Address is 
   a DDNS domain name. This issue was fixed by QuickVPN Client v1.2.8. 

4. There is a known issue with Windows XP SP2 Firewall - ICMP packets are always dropped 
   by the Firewall when the Firewall is enabled. The issue will cause the QuickVPN Client 
   not being able to establish a tunnel with the remote QuickVPN Server successfully. 
   Microsoft has released a patch to fix this issue. Once you install the patch, the issue 
   should be resolved. 
   http://support.microsoft.com/kb/889527/en-us

5. Port 60443 is a special port used for QuickVPN and cannot be used for remote management.
   Similarly port 1723, which is used for PPTP, cannot be used for remote management.
 
