Firmware is due to be released at end of week. The following problems were fixed in firmware version 126.96.36.199: In the VPN > Summary window, the VPN Tunnels Available field sometimes shows an incorrect number. The domain name cannot be entered in the Syslog Server field. Duplicate user names can be entered in the Router Access list. PPTP Passthrough on RVS4000 fails to interoperate with Cisco PPTP server. DHCPv6 server crash issue. IP-based ACL rules could prevent forbidden domains or keywords defined in the Firewall > Internet Access Policy window from functioning correctly. The router allows the saving of invalid LAN IP address. Users can configure and save an invalid character string in the Syslog Server field. Traceroute on the Administration > Diagnostics window does not check for valid input before executing the command. QuickVPN DoS vulnerability. In the Setup > LAN window, the drop-down menu does not list the netmask 255.255.255.252. DNS Cache Poison attack vulnerability. To avoid the DNS Cache Poison attack, RVS4000 now changes the DNS source port number randomly in the network address port translation. Known Issues The following are know issues in firmware version 188.8.131.52: QuickVPN Client running on Windows Vista cannot transfer more than 70MB of file to a remote RVS4000 over a QuickVPN tunnel before the tunnel disconnects. The issue will be fixed in the next firmware version which will be posted on cisco.com. Saving the configuration of port forwarding or port triggering rules causes the router to restart the firewall module which can cause a temporary lockup of the router for 10 to 15 seconds. QoS Rate Control has no effect when IPS is disabled. As a workaround, use QoS Priority instead. DHCP Relay is not supported when multiple VLANs are created. There is a known issue with Windows XP SP2 Firewall. ICMP packets are always dropped by the firewall when the firewall is enabled. This issue causes the QuickVPN client to be unable to establish a tunnel with the remote QuickVPN server successfully. Microsoft has released a patch to fix this issue, which you can get from: http://support.microsoft.com/kb/889527/en-us After you install the patch, the issue should be resolved. You can also fix this issue by upgrading Windows XP to SP3. IPS cannot block eMule 0.48a. During firmware upgrade, the router finishes loading the firmware and reboots before the progress bar shows 100% completion. It is recommended that you wait until the router finishes rebooting before attempting to access the routerâ€™s web-based configuration utility.