01-19-2012 11:37 AM
Hey
We've been using the RV042 routers for years now and have been happy with the gateway to gateway functionality. We typically create 1 to 5 tunnels for our supported customers, all small businesses. Since the new version of RV042 came out several months ago, we've been having tunnel disconnection problems. Then, the tunnels re-negotiate and reconnect.
We've tweked the settings the best we could but the tunnels with the new RV042s drop.
We have proven that these are not line drops and have this issue at at least three locations, all with the new RV042.
We have upgraded to the latest firmware available, RV0XX-v4.1.0.02-tm.bin, to no avail.
I've read other posts like this and have heard that there may be a beta firmware rev that can fix this ?
Please help.
Thanks
JOR
Has anyone seen a fix for this tunnel dropping issue ? The latest firmware version, v4.1.1.01-sp (Dec 6 2011 20:03:18) Does not correct the issue. dor
Joe So, who did you call to get this fixed ?
I still have no resolution and am investigating other vendor products.
Message was edited by: John O'Rourke
04-30-2012 05:30 PM
Hello Joe,
The SPI applies to all traffic going through the firewall. The VPN policies kick in after the traffic goes through the SPI.
Hope this helps.
Regards,
Nagaraja
05-01-2012 06:48 PM
Dear Nagaraja
I had search many thread about the dropping connection problem.
https://supportforums.cisco.com/message/3550430
https://supportforums.cisco.com/message/3516307
https://supportforums.cisco.com/message/3546267
As this thread. Tekliu has replied the workaround to fix this.but cant did by myself.
05-09-2012 10:11 AM
I have been working on what sounds like the same problem for a couple of weeks. Finally I got a suggested solution from adelano@cisco.com:
"To change the timeout value for TCP/UDP session on the RV042, you may access the hidden interface via the following URL:
https://
Log into your router as normal. Then enter (or copy/paste) f_general_hidden.htm following the routr IP address. This accesses TCP and UDP timeout paramenters that are not accessible from the regular General menu.
I set the TCP timeout @ 86400 (24 hrs) and the UDP to the maximum allowable value (300). Based on several hours of testing, this seems to solve the problem.
05-09-2012 07:30 PM
I Checked.
Thats the cisco eng'r did on my devices.!!!
08-09-2012 06:19 AM
Hi everybody!!
the solution is:
https://
Change 1800 seconds (30 minutes) to 28800 seconds (8 hour).
Good Luck
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide