RV082 & IPSEC (QuickVPN) passthrough

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by Bryanba, May 28, 2007.

  1. Bryanba

    Bryanba LI Guru Member

    It doesn't appear the RV082 (firmware 1.3.5) is passing IPSEC through for QuickVPN 1.1.

    I've got an RV082 as my main router in my home. I use it to establish VPNs to my customer sites. I've got an older WRT54G (version 1, firmware 4.21.1) wireless router that I connect to the RV082 that is non-secured wireless acess (for visitors who just need internet access). It's connected via the WAN port and gets it's WAN address from the RV082.

    I'm trying to test a QuickVPN connection from a laptop wirelessly connected to the WRT54G. I can connect to the destination router and establish a tunnel (or so it says it's connected).. But when I try to RDP a computer on the destination LAN it fails to connect. When trying to ping anything on the destination LAN I get the dreaded "Negotiating IP Security" message.


    I disconnect the RV082 from my cable modem and connect the WRT54G directly to the cablemodem.. The same test works just fine. Seems to be a problem wtih the RV082. ???? IPSEC passthrough is enabled on the router.

    The destination router is also a RV082, running firmware 1.3.4. HTTPS is enabled on this router.

    Any ideas ?

  2. Toxic

    Toxic Administrator Staff Member

    Ok so there are 2 RV082's in the equation? can you confirm if you have QVPN clients setup on both routers?
  3. Bryanba

    Bryanba LI Guru Member

    1- One RV082 at the customer site.
    2- One RV082 at my home.
    3- One WRT54G at my home connected to #2 RV082.
    4- Wireless laptop wirelessly connected to #3 WRT54G.

    I'm trying to establish a QVPN tunnel from #4 to #1. QVPN client accounts exist on #1 RV082. QVPN connects, authenticates, activates policy, and connects with connection dialog displaying on screen. However can NOT connect to any resources on destination lan.

    Remove #2 RV082 and connect #3 WRT54G directly to cablemodem.. Connects just as above, and *CAN* connect to resources on destination lan, including Windows RDP.

    So.... removing #2 RV082 from the equation allows the tunnel to work. No other configurations changes or equipment changes were made.

  4. Toxic

    Toxic Administrator Staff Member

    the problem is you are double nat'd behind two NAT devices.

    have a look at this. you will need to port forward to the WRT54G
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice