RV082 VPN to ASA5500 device crashes when keep-alive enabled

[marco.senft]

Hello all.

We have several RV082s here which are intended to connect to a central ASA5510 firewall. The VPNs are configured and do work basically, however in our test environment the RV082s kept crashing after an apparently unpredictable amount of time (sometimes after several days or even weeks). All the RV082 have the newest firmware installed (v4.1.0.02-tm).

When further investigating the issue, I found out that the crashes can be reproduced when enabling the keep-alive option on the RV082. When powering up the RV082, they boot, start up the VPN, and then they crash a few seconds after the tunnel has been established (one or two pings usually get through). When crashing, the RV082 becomes completely unreachable, ie no ping, no webinterface etc.

There is a note in the firmware release notes saying that enabling the keep-alive option would not work the way it should. However it seems that enabling that option lets the router completely crash after its next reboot. This makes the keep-alive option basically worthless, however we need this since the routers will get installed at remote sites with no personnel available there.

Is there any way to enable the keep-alive option without making the routers crash immediately after startup?

Thanks & cheers

[Te-Kai Liu · Accepted solution]

Is the RV082 configured to forward all traffic to the ASA? If so, there is a special beta firmware that attempts to fix the issue. However you would have to call the Support Center to create a ticket first.

http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html

[marco.senft]

Thanks for your quick response. And yes, the RV082 is indeed configured to forward all traffic to the ASA. BTW there is another annoying bug in the config interface that resets the route mask to 255.255.255.0 even if it is configured to something else (like 0.0.0.0).

Since the remote site is being serviced tomorrow, I need this special firmware as quick as possible. I will contact the Support Center and hope to get the firmware in time.

Thanks for your assistance!

[Te-Kai Liu]

The incorrect netmask issue you mentioned is fixed in that firmware as well.