SmallNetBuilder

Some days ago I got two RV220W devices to test VPN perfomance and got the strange results. I built site to site VPN , IPSec preshared key.
A) AES 256/SHA512/DH Group 1536 Incoming speed Mbit/s 17,07 Outgoing-34,14
B) AES 256/SHA1/DH Group 1024 Incoming speed Mbit/s 33,83 Outgoing 77,66
C) AES 128/SHA1/DH Group 1024 Incoming speed Mbit/s 34.69 Outgoing 78,00

I did not expect to see assymetric speed.
Suppose Cisco knows why? :)

Usin the latest firmware atm (1.0.4.17) the router seems fairly stable to me..

However, I would really not recommend this router to anyone..
Looking at the firmware change log, the firmware still contains many bugs..

The VPN functionality is close to impossible setting up (I have not managed to do so for now)..

Cisco has not provided any VPN client for Mac OS X users, and the IPsec VPN is not compatible with iPhone/iPad (which was the main reason why i bought this router)..

If you do not need VPN functionality, you should definitely not buy this router..
If you really need VPN functionality that badly, you should definitely go for a more professional solution..

I chose this router because of the Cisco brand.. However, it looks like they have ditched their Small Business series..

TBH this router could have been great except for allowing Team F1 to develop the firmware for this device.

Issues:

Frequent Random Reboots
DHCP Server slow at times.
WebGUI Very Laggy.

I have spent a lot of time trying to configure this device on my own and with CISCO tech support. My case was eventually escalated level 3 (i think).

Problem 1:

When accessing https://WAN_IP/portal/sslvpn portal, text fields were grayed out and login button was disabled.

Solution: We eventually figure out that URL is CASE SENSITIVE
You must use https://WAN_IP/portal/SSLVPN for it to work properly.

Problem 2:
I am using Windows 7 x64 OS and no matter what I tried I I continuously received the message "Error Virtual Passage Installation Failed!" I built numerous virtual machines and confirmed that Virtual Passage driver works on WIndows XP and WIndows 7 x86, but NOT on x64.


Here is a final response from CISCO tech:
--------------------------
This is a valid issue that has been root caused. The SSL VPN driver file (.sys file) has a self signed Cisco signature but it should have Microsoft signature to get around the below Windows error.
This will be fixed for the upcoming MR2 release. We are investigating whether a work around to the below installation issue is available with the current firmware.
--------------------------

(Firmware Version: 1.0.3.5).

Bought this 6 months ago to add VPN capability to my small manufacturing business. Newtwork-wise I'm an above avg small biz owner, programming for 40 years, and can build basic networks and PCs from scratch.

Would not recommend this router. If I were doing it over would buy separate VPN firewall router and hook it up to wireless access points. Probably would not buy Cisco after this experience.

Cisco tech support eventually taught me how to configure the VPN for my business. It took about 12 phone calls and 6-8 hours on the phone. Half the people I talked to gave me bad advice, or didn't understand the problem. I do sales all day, of fairly technical things and know how to explain problems.

I have had the same experience express by others about the buggy firmware. Have tried 1.0.1.0 and 1.0.2.4 but my unit only runs on 1.0.0.26. The others are buggy and the menus are incomplete no matter which browser I use.

I find the menus not intuitive relative to other routers I've set up. The DCHP Client table doesn't give as much info as a linksys home router.

We are also still experiencing some problems getting Windows computers to share database files over mapped drives in Windows inside the firewall. We've tried mapping the drives with windows names and with static IP addresses. The system seems to clog up now and then, and rebooting solves the problem, but we can't always reboot the whole network while the business is running. I'm not an expert in this particular aspect of networking, and am not confident calling Cisco tech support, so I'll probably try a professional IT person.