RV082 Firmware Revision History

v1.1.6.11		2005/04/28
1.	Improve the connectivity to Quick VPN client. 
Reason: in rare case especially setting up both Group VPN and Quick VPN client, the Quick VPN client may sent IPSec requested packet to RV082 very quickly after the SSL negotiation completed. It caused RV082 failed to establish Quick VPN connection in time. 
2.	Solve the problem that remote user failed to ping RV082s WAN IP even if the Block WAN Request disabled. This problem occurred only on v1.1.6.10 and PPPoE connection type. 
Reason: It was the side-effect when changing PPPoE subnet mask to 255.255.255.255 in v1.1.6.10. When remote user pinged to WAN IP, the icmp packets be acted as broadcast and rejected by RV082s firewall. This bug was fixed in v1.1.6.11.

v1.1.6.10		2005/04/12
1.	Solve the problem that Quick VPN client failed to connect to RV082 when dual WANs linked and set RV082 as load-balance mode.
2.	On [Setup] -> [Network] page, Change back the LAN Subnet Mask to support Class C only.
 
3.	Change the subnet mask of PPP(PPPoE and PPTP) connection to 255.255.255.255.
Reason: attempt to solve the routing problem when using dual WANs in BellSouth network.
 


v1.1.6.9		2005/03/13
1.	On [Setup] -> [Network] page, support Class A, Class B, and Class C subnets on the LAN side. (Only for test purpose)
 
2.	Solve the IPSec with IP-Range problem that RV082 did not exactly restrict IP addresses in IP-Range which user set to use IPSec tunnel.
3.	Provide following functions they are used in Australia only.
(1)	Add a hidden page vpntest.htm to let user set multiple local networks.
Reason: to support on-net/off-net environment requested from Telstra.
(2)	Add and option "Binding static route 0.0.0.0/0 at specific interface" on vpntest.htm. This option used to control the fail-over behavior within WAN1 and WAN2. If this option enabled, and a static route 0.0.0.0/0/matric<15 is set for WAN1(WAN2), in case WAN1(WAN2) connection is dropped, the original WAN1(WAN2) traffic will not be redirect to WAN2(WAN1). This behavior is requested from Telstra.
Notice: When using this functionality, you need:
a.	Disable the NSD(Network Service Detection)
b.	The Remote Security Gateway configured in WAN2(WAN1) IPSec tunnel should be static IP address. 
 
(3) The connection type -- Heart Beat Signal is removed in this version. 

v1.1.6.8		2005/01/01
1.	Modify PPPoE Magic number for connecting to some special ISPs especially in China.
2.	Solve a Peanut Hull DDNS problem. If user follows steps as below, Peanut Hull will not update status automatically. (step 1) Set Dual-WAN mode and configure Peanut Hull on both WAN-1 and WAN-2. (step 2) Change mode from Dual-WAN to DMZ. (step 3) Browse DDNS page.

v1.1.6.7		2004/12/27
1.	Solve the problem that HTTPS did not really enabled until pressing Save Setting button on Firewall page.

v1.1.6.6		2004/12/17
1.	Add following warning message if user used the same username for both WAN1 and WAN2 Peanut Hull settings.
"The username you registered from Peanut Hull can be used only for one dynamic IP, and you can't use the same username for WAN1 and WAN2."
2.	Modified the H.323 ALG in order to improve the data translation for Netmeeting v3.0 

v1.1.6.5		2004/12/14
1.	Solve the problem that DDNS status of both WAN1 and WAN2 shown "updated successfully" even if one of them did not connect to internet.
2.	Solve the problem that multicast-pass-through did not work over PPPoE connection.  
 

v1.1.6.4		2004/12/07
1.	Support "Peanut Hull" DDNS Service 
2.	Solve a Quick VPN Client problem that router may reboot itself if attacked by SSLv2 abnormal packets.
3.	Fix IPSec issue when using Manual keying mode
4.	Fix IPCompression issue that TCP traffic can not pass

v1.1.6.3		2004/11/03
1.	The HTTPS is Enabled by default.
 
2.	Solve the problem that RV082 PPPoE did not work with the Westell ADSL modems connecting to BellSouth in USA.
3.	Fixed a bug that IPSec Manual mode did not work when changed settings of SPI.
4.	Modified the DDNS program in order to avoid the problem that the status "DDNS function is disabled or No Internet connection" shown on 	[DDNS] page even if the update was successful.

v1.1.6.2		2004/09/20
1.	***** Notice: This firmware is used for Beta test only.
2.	Fixed a bug: Occasionally, the Linksys QuickVPN client function may not work properly if multiple VPN clients connected behind one 		router.
	Note: This problem was found when VPN client abnormally dropped the connection but not inform the server(RV082). The server will keep 		the connection until 5 minutes aging time out. But if the user re-login within 5 minutes, it may be unexpectedly kicked out by 		server(RV082).
3.	Add an option to support "3322.org" DDNS service.
4.	Add a rectangle button to choose descending/ascending order on [System Log] page
5.	Improve the Protocol binding functionality.
6.	Shut down WAN interfaces and send PADT packet if necessary before restarting router.
7.	Fix bug: Gaming or MSN sessions may be dropped when using MS Outlook receive/transmit function.
	Note. This problem was found when users playing LineageII and using MS-Outlook. When clicking on Transmit/Receive of Outlook, LineageII 	will be disconnected

v1.1.6.1		2004/09/03
1.	***** Notice: This firmware is used for Beta test only.
2.	Fixed a bug that Linksys QuickVPN client function can not work over PPPoE connection.
3.	Provide a PPTP Server functionality for testing. It allows up to 5 users to connect to RV082 by using PPTP.
4.	Add following feature used in Australia:
	When configuring RV082s [Domain Name] as "DN",
	the DNS server IP addresses got from ISP will not be added to routing table.
5.	Print message "--- System is up! ---" to System Log when system booted up.
6.	Fixed a bug: on [DHCP] -> [Setup] page, the Static IP can not be configured. This bug was found in v1.1.5.3.


v1.1.5.3		2004/08/06
1.	***** Notice: This firmware is used for Linksys QuickVPN client test only.
2.	Expose the [VPN Client Access] page.
	(It was hidden in previous page)
3.	If multiple VPN clients login as the same user name, the last user will kick out the previous user.
4.	The maximum number of VPN Client Users user can configure is 5.
5.	When clicking Save Settings button for FIRST configuration of VPN Client, the confirm message will be pop-out to inquire you about 	changing LAN IP Address if the current LAN IP address is still the default 192.168.1.x. You can choose Yes to change LAN IP Address to 	avoid IP conflict if VPN Client is also using 192.168.1.x. The new LAN IP Address will be shown in the confirm message. Otherwise, you 	can choose No, so the LAN IP Address will not be changed automatically. But when IP conflict, the VPN Client will not be allowed to 	connect to RV082.
	Notice: Before choosing Yes to change LAN IP, you should write down the new LAN IP address shown on confirm message, so that you can 	access router by it.
 
6.	For solving the problem that VPN client failed to change password, change the status message "Version=1" to "version=1" of first 	request packet.
7.	Add on-line help of HTTPS and VPN Client Access
 
 
8.	The [Log] -> [Traffic Statistic] page was removed

v1.1.5.2		2004/07/20
1.	***** Notice: This firmware is used for Linksys QuickVPN client test only. 
2.	Add a VPN client aging mechanism to avoid off-line client occupied the VPN service.
3.	Fixed IPSec pass-through bug to support multiple IPSec clients.
4.	Fixed a bug that multiple accounts created with the same username.
5.	Fixed a bug that can not delete Linksys QuickVPN client by username.
	This problem caused vpn client can not reconnect to router.
6.	Attempt to solve following problem:
	The StopConnection URL does not return a Status Message when successfully stopping a 	connection.
7.	Provide full-range configurable Remote Management Port
 
8.	Add a new page: [Log] -> [Traffic Statistics], but this page is just a prototype for 	review.
 
9.	Allow NSD to work in Smart-link Backup mode.
 
10.	Modify Dual-WAN, IPSec, routing and PPPoE modules for reliability issue.
11.	Change the style of bandwidth value setting from pop-up menu to typing.
 
12.	Fixed a IPSec NetBIOS broadcast bug.

v1.1.5.1		2004/07/07
1.	***** Notice: This firmware is used for Linksys QuckVPN testing only.
2.	Provide HTTPS service, and add an HTTPS enable/disable option on the [Firewall] 		setting page.
3.	Add a hidden page [vpn_clients.htm] for configuring VPN Client Users.
4.	Provide connectivity with new Linksys QuickVPN client.
	Steps:
	(1)	Enable the HTTPS service from [Firewall] page.
	(2)	By defaults, go to http://192.168.1.1/vpn_clients.htm to set VPN client 		users.
	(3)	From remote PC, runs the Cisco VPN client to connect to the RV082.
		If successful, the green phrase [Online] will be shown on VPN Summary page, 		or else, shows red [Offline]
		 


v1.1.5		2004/06/19
1.	In [Port Triggering] setting, allow users to configure port number as 0
2.	Solve a problem that failed to transmit packets form WAN1 to DMZ port if users 	configured WAN2 port as DMZ. This problem 	occurred in v1.1.2 through v1.1.4.
3.	Improve the compatibility of IPSec pass-through functionality


v1.1.4		2004/06/02
1.	In [service management] setting, allow users to define port range overlapped with well-known ports in list.
2.	In Dual WAN mode, allow users to connect WAN1 and WAN2 to the same remote gateway, even if to the same physical address.
3.	In Dual WAN mode, solve the problem that failed to install DNS server in LAN.
4.	Solve the IPSec client-to-gateway handling problem occurs in v1.1.3
5.	Solve the Remote management problem that failed to use port 8080 occurred in v1.1.3 and v1.1.3.1

v1.1.3.1		2004/05/25
1.	This version is only for test purpose. It attempts to solve the DNS problem in Argentina.

v1.1.3		2004/05/21
1.	Fixed a fatal DNS handling bug occurs in v1.1.2. 
This bug made DNS related functions, such as IPSec DNS Resolved, DNS
Name Lookup and DNS proxy, worked abnormally. 

v1.1.2		2004/05/19
1.	Solved the IPSec problem that tunnel connected but failed to transfer data.
2.	Enlarge the maximum NAT concurrent sessions to 20000.
3.	Using the cramfs file system to enlarge the system memory.
4.	Solved the problem that the WAN interface goes up and down unexpectedly when heavy loaded.
5.	Modified DNS module in order to solve a DNS problem occurred when connects to specific Name Server.
6.	Support the Transparent Bridge mode.
Purpose: Installing RV082 dose not need to change legacy network settings.
   

7.	Allow users to specify DMZ port as an IP addresses range.
 

8.	Support the Network Service Detection functionality. 
Purpose: It detects the connectivity between Router and specified host. 
It will log messages or remove connection when connection dropped. 
 

9.	Support the Protocol Binding functionality. It allows users to specify IP or/and service passing through the specified WAN port.
 

10.	Remove the Bandwidth Threshold options. Because it got hard to understand when it working together with the Protocol Binding.
 

11.	Support the VLAN setting. The stations on the different VLAN group can not communicate with each other.
For example: port1~4 set VLAN group as VLAN1, and port5~8 set as VLAN2. The port 1~4 users can access internet and communicate each other, but they can not communicate with port 5~8 users.
 
12.	On [Firewall -> General] page, added Restrict Web Features options to block Java/Cookies/ActiveX/etc,.
 

13.	On [Firewall -> Content Filter] page, added Website Blocking by Keywords options.
 

14.	Support the DNS Resolved functionality. It allows users to specify the IPSec Remote Security Gateway IP as a DDNS name.


v1.1.1		2004/03/17

1.	Solve the DPD (Dead Peer Detection) interoperability problem with CISCO IOS
2.	MTU implementation changed as follows:

	(1)	<PPPoE is On & MTU=AUTO>
-	RV082 should be adjusted the MTU to Specified MRU size which is known through PPP negotiation.
-	If no notify MRU from the Peer, it should be 1492bytes as default.
-	If IPSec is used on PPPoE, set MTU size Current MTU- 60 bytes as default if PPPoE is used in conjunction 	with IPSec.
	(2)	<DHCP is On & MTU=AUTO>
-	If No Active IPSec tunnel, MTU should be 1500 automatically as default.
-	If There is Active IPSec Tunnels, set MTU size Current MTU- 60 bytes as default.
-	Affect above behavior to following case.
					>DHCP
					>Static Address
3.	Decrease the NAT aging time.
 		Purpose: To avoid the WAN connection dropped due to NAT table full

v1.1.0		2004/03/03
	1.	Fixed a bug that Factory Default function did not work in v1.0.12 only  
	2.	Modify the IPSec Keep-alive and connect-on-demand functions internally.
		Purpose: To reduce the overhead of RV082 system

v1.0.12		2004/02/18
	1.	Solve a problem that Microsoft trace route(tracert) did not pass through
		RV082.
	2.	Solve a problem that failed to use XDCC transfer in IRC software.
	3.	Support DPD(Dead Peer Detection) functionality.
		Note: Dead Peer Detection(DPD) is a mechanism used to detect a dead 
		IKE peer. When DPD is enabled, and only if both peers provide DPD mechanism, periodic HELLO/ACK 		messages will be sent through the tunnel in order to prove liveliness. Once a dead peer found, RV082 		will disconnect the tunnel so that connection can be re-established if needed. The DPD message 		interval can be changed from the Interval field. (Reference document: draft-ietf-ipsec-dpd-04.txt)


v1.0.11		2004/01/15
1.	Support "NAT Loopback" functionality. 
	Purpose: It allows LAN-side users accessing LAN-side server by 
	typing WAN IP address.
2. 	Support IPSec interoperability with SSH Sentinel VPN Client in both Main and 			Aggressive 	modes.  Purpose: It allows users using SSH client to connect to RV082 		through Group VPN 	tunnel(Aggressive mode).
	Note: Older firmware worked with SSH only in Main mode. 
3.	Web-UI modification:
	Added 3 pre-defined service ports, PPTP(1723), IPSec(500) and 
	L2TP(1701), in Service list on the "Setup -> Forwarding" screen.
	Purpose: It allows user to host PPTP server at LAN network by   	   	configuring this Forwarding page.


v1.0.10		2004/01/06
1.	Support NetBIOS over IPSec functionality
2.	Web-UI modification:
	Added NetBIOS broadcast option on VPN Advanced page.
	Note: the default setting is Disabled
	Modified on-line help contents for NetBIOS broadcast option

v1.0.9		2004/01/01

1.	Fixed following Web-UI bug that only existed in v1.0.8:
	On DHCP Setup page, DHCP server can not be disabled

2.	Web-UI modification:
	Added on-line Help contents about Microsoft XP/2000 VPN Client on Client to 			Gateway(Group VPN) help page.


v1.0.8		2003/12/24

1.	Web-UI modification: Add Static IP setting on DHCP Setup page. 
	Add DNS Server setting on DHCP Setup page.
	Add Microsoft XP/2000 VPN Client option on VPN Client to Gateway GroupVPN 			setting page.	

		Note: This option is used for Dynamic IP (e.g. PPPoE or DHCP) users which 		using Microsoft VPN client. The difference between Microsoft and other VPN client 		is that Microsoft client does not support Aggressive mode and FQDN/UserFQDN ID 			options. Add/Modify on-line Help contents on DHCP and Port Management pages.


v1.0.7		2003/12/02

1.	Modified the UPnP function for passing the test of UPnP Certification Test 
	Tool

v1.0.6		2003/11/26

1.	Solved an IPSec interoperability problem with Cisco VPN Concentrator. To accept 		more UDP/TCP ports when IKE Phase-1 negotiation
2.	Solved a problem that some kind of PPPoE password may be saved as incorrect value 		under Windows2000/98 environment. 
3.	Fixed a bug that SNMP sysUpTime did not report the correct time.
4.	Web-UI modification:
	Enlarge the max. length of PPPoE username/password settings from 20 to 60 			characters
	On Advanced Routing page, allow users to modify the value of Destination IP on 		exist entry. (This style are applied on all of the pages which use Add to list 		button)
5.	DHCP server modification: 
	Do not assign unused IP address to client

v1.0.3		2003/10/17

1.	Add internal check points for auto-test use. It is only used at manufacturing 	stage.
2.	Change the default snmp sysName from RV082_<random mac> to RV082_<LAN_mac>
3.	Initialize the phrase of snmp sysDescr as RV082 VPN Router
