I have two RV320, and one RV325. All of them have the same symptoms, as they share firmware.
IPSec VPN functionallity is completely broken after trying to reboot from within VPN. No client can connect to IPSec VPN. PPTP can connect, but there's no traffic, so useless too. The router nevers reboots.
I'll explain the situation:
The RV320/RV325 is behind a first stage firewall that has ports 500 and 4500 opened, and I use IPSec VPN to stablish connection with the internal LAN. It works OK with TheGreenBow client and Shrew Soft client. I have a PPTP client too for an Android phone, and is working OK too.
If I try to reboot the router through WEB from within VPN, the router never reboots, but VPN gets immidiately disconnected and no other client is allowed to connect again. So basically it locks clients out. The only way to get the VPN working again is to open an external port in the 1st stage firewall for managing the Cisco Router. The Web GUI is running normally and everything appears as if no reboot command would have been issued, but VPN does not work at all in any of the 3 routers. Then, reboot the router from "outside" the VPN simply works as it should and actually works. And again I have to close the direct port on 1st stage firewall, for security.
When VPN breaks, the log on router can see the client from VPN as ALLOW, but no connection is actually made and the firewall and routing iptables rules on router do not appear logged.
Firmware on all 3 routers is v1.4.2.17 (2017-10-30, 15:50:18)
I already have three RV130 that where substituted with these big brother routers. I never had this issue with the RV130, so I could reboot normally from within its VPN.
I consider this a serious issue, as it breaks completely the VPN functionallity, and remotely I have to expose the router to reboot it.
Anyone with the same symptoms?
Is there anything that can be done to actually reboot the router from within VPN, and can be scripted?
As the RV320 is still an alive product, will it be fixed in a next firmware release?
