RV042 Firmware v1.3.12.6-tm Release Note

6/11/2008

Changes:

1. Support Trend Micro ProtectLink Gateway service, which requires the purchase of 
a license key (i.e. LBATMPG05 or LBATMPG25).
2. Fixed a UDP Port 0 DoS vulnerability issue.
3. Upgraded the OpenSSL library from version 0.9.6d to 0.9.6e to address some 
vulnerability issues. 
4. When remote management and HTTPS are both enabled on the Firewall page, the 
HTTP-based remote management is no longer available. Users have to use 
https://<Router WAN IP>:[port number] or https://<Router WAN IP> for remote management.   
5. Support 50 QuickVPN users.


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 will be fixed by a future 
release of QuickVPN Client.

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

---------------------------------------------------------------------------------------
RV042 Firmware v1.3.10 Release Note

10/23/2007 (beta testing)

Issues Fixed:
1. Fixed an IPSec NAT-T issue that the main mode initiator does not change UDP port to 
4500 in the 5th packet as required by RFC 3947.
2. Fixed a problem that users in the LAN cannot access a non-standard FTP service.
3. Increase the maximum password length to 64 to match with the help page.
4. Support the % sign in the router's password.

---------------------------------------------------------------------------------------
RV042 Firmware v1.3.9 Release Note

10/11/2007

Enhancement:
1. This new firmware supports the change of the CPU from IXP425BB to IXP425ABB.

Issues Fixed:
1. Fixed a problem that occasionally users in the LAN cannot completely download a large 
file from the internet.
2. Fixed an IPSec Tunnel Re-key Negotiation issue (with the Pluto 1.1 fix.)
3. Fixed an issue with QuickVPN Client showing incorrect tunnel status. RV042 will present 
its LAN IP to QuickVPN Client so the Client can use it to detect whether the tunnel is 
truly established by ICMP ping.
4. Updated the default number of QuickVPN users supported from 5 to 10 in the help page 
of VPN Client Access.
5. Updated the help page of Bandwidth Management.
 
----------------------------------------------------------------------------------------
RV042 Firmware v1.3.8.2 Release Note

2/15/2007

Issues Fixed:

1. Fixed a bug in the Network Address Translation (NAT) that may prevent computers in 
the LAN from accessing the internet. This problem occurred to firmware v1.3.8.1 only.

-----------------------------------------------------------------------------------------
RV042 Firmware v1.3.8.1 Release Note

2/05/2007

Enhancements:
1. Support RV016-like Bandwidth Management. 
2. Support RV016-like Port Management with the exception that VLAN is not supported.
3. RV042 will first check if its wan ip address changes before it tears down the IPSec 
tunnel and reconnect.
4. Removed the 45-minute VPN retry limit when Keep Alive is enabled.
5. In the Access Rules Editing page, a new field "Enter Policy Name" was added. On the 
same page, a scheduling option of 24 hours was added.
6. Enhanced the security of QuickVPN by supporting self-generated certificate on the router. 
Several functions (buttons) were added to the Certificate Management section on the VPN 
Client Access page. Administrator can generate new certificate, export certificate for 
admin backup, export certificate for QuickVPN clients, and import certificate for admin. 
The router's certificate needs to be delivered to all QuickVPN users and placed in the 
install directory of QuickVPN Client, e.g. C:\Program Files\Linksys\Linksys VPN Client\. 
This way the QuickVPN client will only trust these certificates placed in its local 
directory and will not be deceived by a hacker in the middle to connect to a hostile computer. 
With QuickVPN Client v1.1.0 or newer, when the client encounters a certificate that is 
not trusted, the client will pop up an warning message, suggesting the user quit the 
connection attempt. The export and import functions can be used when the admin wants to 
reset the router to factory default, but does not want to re-distribute the certificate 
to all of the QuickVPN users.
7. Support Windows Workgroup over QuickVPN tunnel.

Issues Fixed:
1. Fixed the TCP Window Scaling issue with Windows Vista.
2. Fixed an issue with MTU. After the VPN tunnel is established, changing MTU setting from 
Manual mode to Auto mode will cause on-going tunnel connection not able to transmit VPN 
traffic correctly.
3. Fixed the known issue that the local DNS Server's IP address does not get passed to 
DHCP clients.
4. Updated the maximum number of entries for protocol binding from 30 to 100 in the 
Dual WAN help page.
5. Support the new PeanutHull DDNS service. The option, PeanutHull, was renamed to 
Oray.netPeanutHullDDNS on the DDNS setting page. The help page for DDNS was updated as well. 
(Note: In China, the specification of PeanutHull DDNS service was changed on Oct. 1st, 2006. 
Old PeanutHull DDNS client will not work after Oct. 1st.)
6. Fixed a compatibility issue (firmware v1.3.8 and v1.3.7.13 only) with some cable modems 
that will cause the router to reboot.
7. Fixed an issue (firmware v1.3.8 only) with firmware upgrade, which requires a power reset 
for https to function properly.
8. Fixed an issue (firmware v1.3.8 only) with Port Management when changing a port's priority 
from Low to High.

**If firmware upgrade should fail using the Web UI, a TFTP utility can be used to load 
the v1.3.7.2 firmware into the router. You could then upgrade the firmware to the latest 
version using the Web UI.**  
