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

How to setup VPN tunnel... WRV54G <=> WRV54G ???

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by plooger, May 13, 2005.

  1. plooger

    plooger Network Guru Member

    Ok, I've seen much derision for the WRV54G on this forum relative to NAT-T and QuickVPN, but I'm just trying to setup a simple VPN tunnel between 2 offices.... and both routers are just sitting there with a "Waiting for Connection" message on each router's tunnel setup dialog.

    Are these things capable of establishing a stable VPN tunnel between each other? If so, how? (I'm aware that going to BEFVP41s w/ separate wireless access points are an option; however, I'm wanting to know whether this most basic of configs is possible w/ the WRV54G.)

    Your insight will be MUCH appreciated. (As with others, my project deadline is looming.)

    Thanks in advance...!

    Regs,
    Karl K.

    ------------------------------------------------------------

    Setup...

    Common Setup between offices...

    WRV54G routers running firmware 2.37.1
    Dynamic IP for WAN interfaces, each registered w/ DynDNS.org
    LAN Netmask: 255.255.255.0

    Office-specific setup...

    Office A:
    LAN Network: 10.10.10.0
    Router LAN IP: 10.10.10.1

    Office B:
    LAN Network: 10.10.20.0
    Router LAN IP: 10.10.20.1

    Office A VPN setup....
    Passthroughs enabled
    VPN Tunnel: enabled
    VPN Gateway: disabled
    Local Secure Group: Subnet (10.10.10.0/255.255.255.0)
    Remote Secure Group: Any
    Remote Secure GW: FQDN ({OfficeB}.dyndns.org)
    Encryption: 3DES
    Auth: SHA1
    Key Mgmt [Key Exch]: Auto(IKE)
    Key Mgmt [PFS]: Enabled
    Key Mgmt [Pre-Shared Key]: {string}
    Key Mgmt [Key Lifetime]: 3600
    Status: Waiting for Connection (GGRRRR!!!)

    Office B VPN setup....
    Passthroughs enabled
    VPN Tunnel: enabled
    VPN Gateway: disabled
    Local Secure Group: Subnet (10.10.20.0/255.255.255.0)
    Remote Secure Group: Any
    Remote Secure GW: FQDN ({OfficeA}.dyndns.org)
    Encryption: 3DES
    Auth: SHA1
    Key Mgmt [Key Exch]: Auto(IKE)
    Key Mgmt [PFS]: Enabled
    Key Mgmt [Pre-Shared Key]: {string}
    Key Mgmt [Key Lifetime]: 3600
    Status: Waiting for Connection (GGRRRR!!!)
     
  2. TazUk

    TazUk Network Guru Member

    A couple of things, firstly update the firmware to a later version, v2.37.9 can be downloaded from this site ;) Secondly change the remote secure group at each end from any to the remote subnet. I've got my WRV54G connecting to a couple of BEFVP41's and a WAG54G so a WRV54G to WRV54G should be fine :)
     
  3. DocLarge

    DocLarge Super Moderator Staff Member Member

  4. plooger

    plooger Network Guru Member

    Thanks very much for the replies, Taz & Doc. Unfortunately, my customer required that I run a Linksys-supported firmware version, and so was forced to go the BEFVP41/WRT54G_as_AP combo route.
     
  5. outback_boy

    outback_boy Guest

    wrv54g

    hey everyone,
    I have discovered my downfall for the WRV54G!!!!!!!
    Under Setup, Basic Setup, Internet Setup MTU: was set to Manual. I changed it to Auto after reading someones notes on one of the forums on this site. As soon as I set it to Auto my tunnel connected.
    Oh this was the original firmware, no upgrade, firewall page everything disabled, vpn passthrough Disabled.
    Set your VPN Tunnel to your preference.
     
  6. DocLarge

    DocLarge Super Moderator Staff Member Member

    Glad to help you out, outback.

    I happened to have noticed that a few weeks ago, and that seemed to be the issue with quickvpn for me. It appears that it's just an MTU adjustment to "auto" and quickvpn fires right up, provided all the other conditions in the setup guide a friend and I put together are met...

    Doc
     

Share This Page