1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RV042 v3 G2G VPN Problems.

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by Sfor, Dec 18, 2012.

  1. Sfor

    Sfor Network Guru Member

    I've been experimenting while trying to replace a RV082 v1 with RV042 v3.

    The cycle goes like that:
    - reverting to factory default
    - entering the base settings (MAC clone, WAN settings, LAN settings)
    - entering VPN tunnels one by one
    To this point everything works fine. All the 8 VPN tunnels connected, right after entering the settings. But at some point all the tunnels stop. I was unable to determine the direct cause. It could be a reboot, a setting change, or something else. In any case all the tunnels are reported as waiting for connection.

    The symptoms:
    - all the tunnels are reported as waiting for connection.
    - the connect button fires the connection procedure, but the tunnel gets back to the waiting for connection state.
    - sometimes there is no indication in the vpn log the connect button did anything. It looks like there were no attempts to create a tunnel.
    - sometimes the vpn log shows a successful negotiation, but all the tunnels remain as waiting for connection.
    - reboot does not help
    - power reset does not help
    - factory reset and reloading the config file saved, when the VPN tunnels were working does not help
    - the VPN unreletad settings do not seem to be the cause

    Apparently, the only effective action seems to be the factory defaults reset and reentering all the settings by hand. In other words to repeat the whole cycle.

    After three such cycles I got tired and shelved the RV042 v3 device, for now.
     
  2. Sfor

    Sfor Network Guru Member

    Well, I did increase the DPD time settings. The futher observations show, after some reboots tunnels are working and after all others they don't.
     
  3. Sfor

    Sfor Network Guru Member

    I did upgrade the firmware to v4.2.2.08. At first the router did not want to obtain the IP adress through DHCP on the WAN1 port. After some tweaking and a few reboots the WAN1 port started to work correctly. It looked like the DHCP was not working for no reason.

    Then the same happened with all the VPN tunnels.

    This somewhat unpredictable behavior made me suspicious, but it seems all is working correctly for a few days, already. Perhaps, the problem has been fixed with the new firmware.
     
  4. Toxic

    Toxic Administrator Staff Member

  5. Sfor

    Sfor Network Guru Member

    I found something about VPN tunnel conectivity there. That's why I decided to test this firmware.
     
  6. Sfor

    Sfor Network Guru Member

    The VPN tunnels are working, more or less.

    Today I noticed a tunnel was reported as connected, but there were no ping to the router on the other side (RV082 v1). I had to use the disconnect button on RV042 v3. Then the tunnel reconnected automatically. It was a a connection made with the tunnel backup with two WANs on the RV082 side.

    With the same tunnel I noticed a problem with VNC file transfer problem. VNC connection works correctly to the moment a file transwer is performed. The VNC connection breakes at that point (with both TightVNC and UltraVNC). With TightVNC and Windows 98 on the other side it was possible to reconnect to the VNC server, but with Ultra VNC on Windows 2000, the server stopped receiving connection, and I had to ask to reboot the remote computer.

    After replacing RV042 v3 with another RV082 v1 the VNC file transfers started to work correctly.

    With VNC file transfers not operational, I decided the router is still too buggy for general use. It is going back to the shelf, until a new firmware appears.
     

Share This Page