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

WRV54G to WRV54G VPN Problem

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by leel, Jun 8, 2004.

  1. leel

    leel Network Guru Member

    Good morning, from a brand new user here.

    Has anyone had any luck getting a WRV54G to WRV54G VPN tunnel
    working? I recently bought two to set up a VPN between my home and
    the apartment where I stay during the week. (I commute on the
    weekends). They came with firmware 2.10 and I immediately upgraded
    them to 2.25.2 to take advantage of the FQDN for the remote VPN
    Gateway. Both locations are running ADSL with dynamic IPs, one Sprint
    the other Verizon. I have an account with DynDNS.org and the DynDNS
    agent in the routers seems to work well and keeps the IP updated.


    The problem comes when I try to connect the tunnel. When either router
    gets to "resolving hostname" on the VPN information page, it immediatly
    looses all WAN connectivity. The only way to get WAN connectivity back is
    to reset to factory defaults and redo all the settings.


    Linksys assures me that they have no known issues with this
    firmware...but I have my doubts :roll:


    Just checking to see if anyone else has experienced anything like this....
     
  2. JonAlthoff

    JonAlthoff Network Guru Member

    No known issues? That's a good joke. Something to try just to see if it works. Change the FQDN temporarily to the IP address for each and see if you can connect.
     
  3. frank

    frank Network Guru Member

    :?


    i am also having wrv54g problems. try reading the book war drivers. i found it at several of the large bookstores and it seems to deal with this and several of the linksys wireless routers and the later microsoft os's

    good luck

    frank
     
  4. leel

    leel Network Guru Member

    Actually, I made a lot of progress with this over the weekend. I now have the VPN tunnel connecting using the FQDN and DynDNS.org.

    I think the main problem was that I never did a reset to factory defaults after flashing to 2.25.2 firmware. I upgraded the firmware and immediatly did the setup and nothing would work. I tried resetting to defaults after the firmware upgrade, did the setup and everything came up working immediatly.

    The only issues now are the fact that the only way remote admin works is to forward port 8080 to the routers LAN ip, and I don't like leaving ports open to the world. The routers also seem to choke and hang up on a large file transfer over the VPN tunnel. I tried transferring a 15 MB file and it locked both ends up. I suspect that it may be a packet fragmentation issue, I need to play with the MTU settings on both ends.

    All in all, I am fairly happy with the way it is working right now. Will post more as I make progress, or not, as the case may be.
     
  5. darin

    darin Network Guru Member

    I am working on the same problem. I have 2 WRV54Gs, trying to establish a VPN between verizon DSL and SBC yahoo.

    I have identical configuration pages for the VPN at each end and DDNS via TZ0 (seems to be updating and working fine).

    I can ping between the routers and log both ends. I can access them via remote admin using the FQDN. Latest version of the firmware on both ends (2.25.2).

    VPN stops at "waiting for connection" Logs seem to show port 500 blocked?

    Any help from anyone who has made this work would be greatly appreciated.

    -Darin
     
  6. darin

    darin Network Guru Member

    Logs attached: Thanks again for any help debugging this.

    Index Date From IP Log Message
    ------- ------------------------- --------------- ------------------------------------

    491 Sat Jun 16 14:53:55 2004 192.168.2.1 Jun 16 14:52:58 2004 linksysVA RGFW-CONF: Configuration started (Mode: Activate)
    492 Sat Jun 16 14:53:55 2004 192.168.2.1 Jun 16 14:52:58 2004 linksysVA add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    493 Sat Jun 16 14:53:55 2004 192.168.2.1 Jun 16 14:52:58 2004 linksysVA add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    494 Sat Jun 16 14:53:55 2004 192.168.2.1 Jun 16 14:52:58 2004 linksysVA add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    495 Sat Jun 16 14:53:55 2004 192.168.2.1 Jun 16 14:52:58 2004 linksysVA add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    496 Sat Jun 16 14:53:55 2004 192.168.2.1 Jun 16 14:52:58 2004 linksysVA add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    497 Sat Jun 16 14:53:55 2004 192.168.2.1 Jun 16 14:52:58 2004 linksysVA add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    498 Sat Jun 16 14:53:55 2004 192.168.2.1 Jun 16 14:52:58 2004 linksysVA add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    499 Sat Jun 16 14:53:55 2004 192.168.2.1 Jun 16 14:52:58 2004 linksysVA firewall_config_standard_openrg:1409: RGFW-CONF: Failed
    500 Sat Jun 16 14:53:55 2004 192.168.2.1 Jun 16 14:52:58 2004 linksysVA RGFW-CONF: Configuration completed (Status: Errors)
    501 Sat Jun 16 14:54:16 2004 192.168.2.1 Jun 16 14:53:21 2004 linksysVA RGFW-OUT: ACCEPT (UDP 138.88.110.133:1024->199.45.32.43:53 on ppp0) [31,0]
    502 Sat Jun 16 14:54:17 2004 192.168.2.1 Jun 16 14:53:22 2004 linksysVA RGFW-OUT: ACCEPT (TCP 192.168.2.100:1688->68.94.150.4:80 on ppp0) [0,0]
    503 Sat Jun 16 14:54:17 2004 192.168.2.1 Jun 16 14:53:22 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 218.67.200.230:1025->138.88.110.133:137 on ppp0) [0,0]
    504 Sat Jun 16 14:54:19 2004 192.168.2.1 Jun 16 14:53:24 2004 linksysVA RGFW-OUT: ACCEPT (TCP 192.168.2.100:1689->68.94.150.4:80 on ppp0) [0,0]
    505 Sat Jun 16 14:54:19 2004 192.168.2.1 Jun 16 14:53:24 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 68.94.150.4:500->138.88.110.133:500 on ppp0) [0,0]
    506 Sat Jun 16 14:54:20 2004 192.168.2.1 Jun 16 14:53:25 2004 linksysVA RGFW-OUT: ACCEPT (TCP 192.168.2.100:1690->68.94.150.4:80 on ppp0) [0,0]
    507 Sat Jun 16 14:54:21 2004 192.168.2.1 Jun 16 14:53:26 2004 linksysVA RGFW-OUT: ACCEPT (TCP 192.168.2.100:1691->68.94.150.4:80 on ppp0) [0,0]
    508 Sat Jun 16 14:54:21 2004 192.168.2.1 Jun 16 14:53:26 2004 linksysVA RGFW-OUT: ACCEPT (TCP 192.168.2.100:1692->68.94.150.4:80 on ppp0) [0,0]
    509 Sat Jun 16 14:54:26 2004 192.168.2.1 Jun 16 14:53:31 2004 linksysVA RGFW-OUT: ACCEPT (TCP 192.168.2.100:1693->68.94.150.4:80 on ppp0) [0,0]
    510 Sat Jun 16 14:54:29 2004 192.168.2.1 Jun 16 14:53:34 2004 linksysVA RGFW-OUT: ACCEPT (TCP 192.168.2.100:1694->68.94.150.4:80 on ppp0) [0,0]
    511 Sat Jun 16 14:54:29 2004 192.168.2.1 Jun 16 14:53:34 2004 linksysVA RGFW-OUT: ACCEPT (TCP 192.168.2.100:1695->68.94.150.4:80 on ppp0) [0,0]
    512 Sat Jun 16 14:54:29 2004 192.168.2.1 Jun 16 14:53:34 2004 linksysVA RGFW-OUT: ACCEPT (TCP 192.168.2.100:1696->68.94.150.4:80 on ppp0) [0,0]
    513 Sat Jun 16 14:54:30 2004 192.168.2.1 Jun 16 14:53:35 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 68.94.150.4:500->138.88.110.133:500 on ppp0) [0,0]
    514 Sat Jun 16 14:54:30 2004 192.168.2.1 Jun 16 14:53:35 2004 linksysVA RGFW-OUT: ACCEPT (TCP 192.168.2.100:1697->68.94.150.4:80 on ppp0) [0,0]
    515 Sat Jun 16 14:54:33 2004 192.168.2.1 Jun 16 14:53:38 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 68.20.35.151:1028->138.88.110.133:137 on ppp0) [0,0]
    516 Sat Jun 16 14:54:40 2004 192.168.2.1 Jun 16 14:53:45 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 200.65.192.239:1030->138.88.110.133:137 on ppp0) [0,0]
    517 Sat Jun 16 14:54:49 2004 192.168.2.1 Jun 16 14:53:54 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 68.94.150.4:500->138.88.110.133:500 on ppp0) [0,0]
    518 Sat Jun 16 14:54:56 2004 192.168.2.1 Jun 16 14:54:01 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 62.248.4.83:1258->138.88.110.133:137 on ppp0) [0,0]
    519 Sat Jun 16 14:55:29 2004 192.168.2.1 Jun 16 14:54:34 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 68.94.150.4:500->138.88.110.133:500 on ppp0) [0,0]
    520 Sat Jun 16 14:55:37 2004 192.168.2.1 Jun 16 14:54:42 2004 linksysVA RGFW-IN: BLOCK-RULES (TCP 64.119.152.43:4616->138.88.110.133:445 on ppp0) [0,0]
    521 Sat Jun 16 14:55:39 2004 192.168.2.1 Jun 16 14:54:44 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 68.94.150.4:500->138.88.110.133:500 on ppp0) [0,0]
    522 Sat Jun 16 14:55:40 2004 192.168.2.1 Jun 16 14:54:45 2004 linksysVA RGFW-IN: BLOCK-RULES (TCP 64.119.152.43:4616->138.88.110.133:445 on ppp0) [0,0]
    523 Sat Jun 16 14:55:42 2004 192.168.2.1 Jun 16 14:54:47 2004 linksysVA RGFW-IN: BLOCK-RULES (TCP 138.88.177.97:4776->138.88.110.133:445 on ppp0) [0,0]
    524 Sat Jun 16 14:55:45 2004 192.168.2.1 Jun 16 14:54:50 2004 linksysVA RGFW-IN: BLOCK-RULES (TCP 138.88.177.97:4776->138.88.110.133:445 on ppp0) [0,0]
    525 Sat Jun 16 14:55:46 2004 192.168.2.1 Jun 16 14:54:51 2004 linksysVA RGFW-IN: BLOCK-RULES (TCP 64.119.152.43:4616->138.88.110.133:445 on ppp0) [0,0]
    526 Sat Jun 16 14:55:59 2004 192.168.2.1 Jun 16 14:55:04 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 68.94.150.4:500->138.88.110.133:500 on ppp0) [0,0]
    527 Sat Jun 16 14:56: 6 2004 192.168.2.1 Jun 16 14:55:11 2004 linksysVA RGFW-IN: BLOCK-RULES (UDP 138.88.101.213:1060->138.88.110.133:137 on ppp0) [0,0]
     
  7. leel

    leel Network Guru Member

    darin,

    Sorry to hear you are fighting this too.

    I does appear that your firewall is blocking the tunnel, although
    I am no expert at reading the Linksys logs. I would run them
    past the Linksys tech support folks, as flaky as they can be at times.

    Do you have the VPN passthrough boxes checked on both ends?

    I am having no trouble making the tunnel connect on each end. I
    am still having the problem with the connection choking on large
    file transfers over the tunnel. Even with no activity on the tunnel,
    both ends loose WAN connectivity 2 ~ 3 times per day and require
    a power cycle. After simply powering the routers down and back up,
    the VPN tunnel immediatly reconnects and I have WAN connectivity
    on both ends.

    I really wish that Linksys could get this fixed. I hope their development
    engineers have a better grasp of how this is supposed to work than their
    tech support folks.

    Lee Ligon
    System Support Engineer
    Systems and Networks
    M/A-Com Wireless Systems
    Technical Support Center
    Lynchburg, VA
     
  8. darin

    darin Network Guru Member

    Lee,

    Thanks for the tips. I have found threads on a couple of other sites that list specific setups that have worked for other people, but when I try them no luck. I got one tip on flashing the firmware on the 5100b modem. I haven't tried that yet.

    I'm somewhat suspicious that a minor setting change from DES to 3DES, etc. would make the big difference on connecting. It seems like there is something else going on here (blocked ports, modem issues, firmware). The messages in the log about file exists, confg update completed (with errors) seems troubling.

    I've already spent about 25 hours trying to get these routers to talk. At some point, there going back in their box and back to the store.

    Seems like a simple VPN between 2 offices with DSL would not be such a problem to diagnose.

    -Darin
     
  9. leel

    leel Network Guru Member

    I have no info on the 5100B modem. Is it acting as a NAT router, or just a modem. Is it in bridged mode?

    Just grasping at straws here, like everyone else, it seems!

    Lee
     
  10. darin

    darin Network Guru Member

    After sending the logs to LinkSys Support, they claim that the router must be defective and want me to send it in.

    I really don't believe its a problem specific to one unit and can't get any real diagnostic help from LinkSys.

    Very, very frustrating. My latest log has clear messages about configuration failures. See below:

    Index Date From IP Log Message
    ------- ------------------------- --------------- ------------------------------------
    1 Sat Jun 17 23: 1:47 2004 192.168.2.1 Jun 16 15:12:53 2004 OpenRG RGFW-IN: BLOCK-RULES (UDP 218.160.138.32:1025->138.88.232.96:137 on ppp0) [0,0]
    2 Sat Jun 17 23: 1:49 2004 192.168.2.1 Jun 16 15:12:55 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3379->68.92.121.20:80 on ppp0) [0,0]
    3 Sat Jun 17 23: 1:51 2004 192.168.2.1 Jun 16 15:12:57 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.102:3180->168.144.1.11:443 on ppp0) [0,0]
    4 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:12:58 2004 OpenRG RGFW-CONF: Configuration started (Mode: Activate)
    5 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:12:58 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    6 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:12:58 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    7 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:12:58 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    8 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:12:58 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    9 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:12:58 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    10 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:12:58 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    11 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:12:58 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    12 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:12:58 2004 OpenRG firewall_config_standard_openrg:1409: RGFW-CONF: Failed
    13 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:12:58 2004 OpenRG RGFW-CONF: Configuration completed (Status: Errors)
    14 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG RGFW-OUT: BLOCK-RULES (TCP 192.168.2.100:3381->68.92.121.20:80 on ppp0)
    15 Sat Jun 17 23: 1:53 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG RGFW-IN: BLOCK-RULES (UDP 68.92.121.20:500->138.88.232.96:500 on ppp0)
    16 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG Jun 16 15:13:00 pluto[33]: added connection description "ips0"
    17 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG RGFW-OUT: ACCEPT (UDP 138.88.232.96:500->68.92.121.20:500 on ppp0) [31,0]
    18 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG Jun 16 15:13:00 pluto[33]: listening for IKE messages
    19 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG RGFW-CONF: Configuration started (Mode: Activate)
    20 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG Jun 16 15:13:00 pluto[33]: forgetting secrets
    21 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    22 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    23 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:01 2004 OpenRG Jun 16 15:13:00 pluto[33]: "ips0" #3: initiating Main Mode
    24 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    25 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    26 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    27 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    28 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    29 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG firewall_config_standard_openrg:1409: RGFW-CONF: Failed
    30 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG RGFW-CONF: Configuration completed (Status: Errors)
    31 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG RGFW-CONF: Configuration started (Mode: Activate)
    32 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    33 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    34 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    35 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    36 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    37 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:00 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    38 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:01 2004 OpenRG add_bidir_rule:80: RGFW-CONF: Failed to add rule (File exists)
    39 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:01 2004 OpenRG firewall_config_standard_openrg:1409: RGFW-CONF: Failed
    40 Sat Jun 17 23: 1:54 2004 192.168.2.1 Jun 16 15:13:01 2004 OpenRG RGFW-CONF: Configuration completed (Status: Errors)
    41 Sat Jun 17 23: 1:55 2004 192.168.2.1 Jun 16 15:13:01 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3381->68.92.121.20:80 on ppp0) [0,0]
    42 Sat Jun 17 23: 1:56 2004 192.168.2.1 Jun 16 15:13:02 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3387->68.92.121.20:80 on ppp0) [0,0]
    43 Sat Jun 17 23: 1:56 2004 192.168.2.1 Jun 16 15:13:03 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3392->68.92.121.20:80 on ppp0) [0,0]
    44 Sat Jun 17 23: 1:57 2004 192.168.2.1 Jun 16 15:13:03 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3393->68.92.121.20:80 on ppp0) [0,0]
    45 Sat Jun 17 23: 2: 2 2004 192.168.2.1 Jun 16 15:13:08 2004 OpenRG Jun 16 15:13:08 pluto[33]: "ips0" #4: responding to Main Mode
    46 Sat Jun 17 23: 2: 2 2004 192.168.2.1 Jun 16 15:13:08 2004 OpenRG Jun 16 15:13:08 pluto[33]: "ips0" #4: number of Transform Payloads disagrees with OaG
    47 Sat Jun 17 23: 2: 2 2004 192.168.2.1 Jun 16 15:13:08 2004 OpenRG Jun 16 15:13:08 pluto[33]: "ips0" #4: IP address 68.92.121.20 was added to block-IP G
    48 Sat Jun 17 23: 2: 4 2004 192.168.2.1 Jun 16 15:13:10 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3394->68.92.121.20:80 on ppp0) [0,0]
    49 Sat Jun 17 23: 2: 5 2004 192.168.2.1 Jun 16 15:13:11 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3395->68.92.121.20:80 on ppp0) [0,0]
    50 Sat Jun 17 23: 2: 5 2004 192.168.2.1 Jun 16 15:13:11 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3396->68.92.121.20:80 on ppp0) [0,0]
    51 Sat Jun 17 23: 2: 5 2004 192.168.2.1 Jun 16 15:13:11 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3397->68.92.121.20:80 on ppp0) [0,0]
    52 Sat Jun 17 23: 2: 5 2004 192.168.2.1 Jun 16 15:13:11 2004 OpenRG RGFW-IN: BLOCK-RULES (TCP 4.158.99.155:2956->138.88.232.96:445 on ppp0) [0,0]
    53 Sat Jun 17 23: 2: 5 2004 192.168.2.1 Jun 16 15:13:12 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3398->68.92.121.20:80 on ppp0) [0,0]
    54 Sat Jun 17 23: 2:10 2004 192.168.2.1 Jun 16 15:13:17 2004 OpenRG RGFW-IN: BLOCK-RULES (TCP 4.158.99.155:2956->138.88.232.96:445 on ppp0) [0,0]
    55 Sat Jun 17 23: 2:19 2004 192.168.2.1 Jun 16 15:13:25 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3405->68.92.121.20:80 on ppp0) [0,0]
    56 Sat Jun 17 23: 2:20 2004 192.168.2.1 Jun 16 15:13:26 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3408->68.92.121.20:80 on ppp0) [0,0]
    57 Sat Jun 17 23: 2:20 2004 192.168.2.1 Jun 16 15:13:27 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3409->68.92.121.20:80 on ppp0) [0,0]
    58 Sat Jun 17 23: 2:23 2004 192.168.2.1 Jun 16 15:13:29 2004 OpenRG Jun 16 15:13:29 pluto[33]: "ips0" #5: responding to Main Mode
    59 Sat Jun 17 23: 2:23 2004 192.168.2.1 Jun 16 15:13:29 2004 OpenRG Jun 16 15:13:29 pluto[33]: "ips0" #5: number of Transform Payloads disagrees with OaG
    60 Sat Jun 17 23: 2:24 2004 192.168.2.1 Jun 16 15:13:30 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3410->68.92.121.20:80 on ppp0) [0,0]
    61 Sat Jun 17 23: 2:25 2004 192.168.2.1 Jun 16 15:13:31 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3411->68.92.121.20:80 on ppp0) [0,0]
    62 Sat Jun 17 23: 2:28 2004 192.168.2.1 Jun 16 15:13:34 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3412->68.92.121.20:80 on ppp0) [0,0]
    63 Sat Jun 17 23: 2:28 2004 192.168.2.1 Jun 16 15:13:35 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3413->68.92.121.20:80 on ppp0) [0,0]
    64 Sat Jun 17 23: 2:28 2004 192.168.2.1 Jun 16 15:13:35 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3414->68.92.121.20:80 on ppp0) [0,0]
    65 Sat Jun 17 23: 2:39 2004 192.168.2.1 Jun 16 15:13:45 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.102:3181->168.144.1.11:443 on ppp0) [0,0]
    66 Sat Jun 17 23: 2:41 2004 192.168.2.1 Jun 16 15:13:47 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3421->68.92.121.20:80 on ppp0) [0,0]
    67 Sat Jun 17 23: 2:42 2004 192.168.2.1 Jun 16 15:13:48 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3424->68.92.121.20:80 on ppp0) [0,0]
    68 Sat Jun 17 23: 2:42 2004 192.168.2.1 Jun 16 15:13:49 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3425->68.92.121.20:80 on ppp0) [0,0]
    69 Sat Jun 17 23: 2:46 2004 192.168.2.1 Jun 16 15:13:53 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.102:3182->168.144.1.11:443 on ppp0) [0,0]
    70 Sat Jun 17 23: 2:49 2004 192.168.2.1 Jun 16 15:13:55 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3426->68.92.121.20:80 on ppp0) [0,0]
    71 Sat Jun 17 23: 2:49 2004 192.168.2.1 Jun 16 15:13:56 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3427->68.92.121.20:80 on ppp0) [0,0]
    72 Sat Jun 17 23: 2:49 2004 192.168.2.1 Jun 16 15:13:56 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3428->68.92.121.20:80 on ppp0) [0,0]
    73 Sat Jun 17 23: 2:50 2004 192.168.2.1 Jun 16 15:13:57 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3429->68.92.121.20:80 on ppp0) [0,0]
    74 Sat Jun 17 23: 2:50 2004 192.168.2.1 Jun 16 15:13:57 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.100:3430->68.92.121.20:80 on ppp0) [0,0]
    75 Sat Jun 17 23: 2:53 2004 192.168.2.1 Jun 16 15:13:59 2004 OpenRG RGFW-IN: BLOCK-RULES (TCP 138.88.91.128:4206->138.88.232.96:445 on ppp0) [0,0]
    76 Sat Jun 17 23: 2:56 2004 192.168.2.1 Jun 16 15:14:02 2004 OpenRG RGFW-IN: BLOCK-RULES (TCP 138.88.91.128:4206->138.88.232.96:445 on ppp0) [0,0]
    77 Sat Jun 17 23: 3: 0 2004 192.168.2.1 Jun 16 15:14:07 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.102:3184->147.9.1.123:443 on ppp0) [0,0]
    78 Sat Jun 17 23: 3: 1 2004 192.168.2.1 Jun 16 15:14:07 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.102:3185->147.9.1.123:443 on ppp0) [0,0]
    79 Sat Jun 17 23: 3: 1 2004 192.168.2.1 Jun 16 15:14:07 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.102:3186->147.9.1.123:443 on ppp0) [0,0]
    80 Sat Jun 17 23: 3: 1 2004 192.168.2.1 Jun 16 15:14:07 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.102:3187->147.9.1.123:443 on ppp0) [0,0]
    81 Sat Jun 17 23: 3: 1 2004 192.168.2.1 Jun 16 15:14:07 2004 OpenRG Jun 16 15:14:07 pluto[33]: "ips0" #6: responding to Main Mode
    82 Sat Jun 17 23: 3: 1 2004 192.168.2.1 Jun 16 15:14:07 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.102:3188->147.9.1.123:443 on ppp0) [0,0]
    83 Sat Jun 17 23: 3: 1 2004 192.168.2.1 Jun 16 15:14:07 2004 OpenRG Jun 16 15:14:07 pluto[33]: "ips0" #6: number of Transform Payloads disagrees with OaG
    84 Sat Jun 17 23: 3: 1 2004 192.168.2.1 Jun 16 15:14:08 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.102:3189->147.9.1.123:443 on ppp0) [0,0]
    85 Sat Jun 17 23: 3: 1 2004 192.168.2.1 Jun 16 15:14:08 2004 OpenRG RGFW-OUT: ACCEPT (TCP 192.168.2.102:3190->147.9.1.123:443 on ppp0) [0,0]
    87 Sat Jun 17 23: 3: 4 2004 192.168.2.1 Jun 16 15:14:10 2004 OpenRG Jun 16 15:14:10 pluto[33]: "ips0" #3: starting keying attempt 2 of at most 3
    88 Sat Jun 17 23: 3: 4 2004 192.168.2.1 Jun 16 15:14:10 2004 OpenRG Jun 16 15:14:10 pluto[33]: "ips0" #7: initiating Main Mode to replace #3
    89 Sat Jun 17 23: 3: 5 2004 192.168.2.1 Jun 16 15:14:12 2004 OpenRG RGFW-IN: BLOCK-RULES (TCP 221.156.1.44:4277->138.88.232.96:4899 on ppp0) [0,0]


    It really sounds like the VPN capabilites of this product were not ready for prime time. Are there any other support options? How can I get someone at LinkSys who knows the product to look at the logs and provide some help??

    -Darin
     

Share This Page