SR520 Auto Reconnect VPN Remote Connection

Hi,
I am new to the SR520 router, and I have gotten the vpn server and remote to work. We have 3 of these routers, one at our corporate site, and one at each of our remote sites. The VPN's work good, but I would like them to auto-reconnect because we have some voice traffic that needs to pass over them, and the staff is not very capable of using the connection tool. Is this possible? Is there a time out on them that I can remove?
I have only used the Cisco Configuration Assistant to configure them, and when I used the command line, the vpn's wouldn't work.
Any help would be appreciated.

Addis and I connected with Andy Hickman who share the following that could work for this.
To keep the tunnel up you can use the auto connect feature of EZVPN.  This is pretty straight forward, just do the following:
Starting from a standard configuration built by CCA1.9 for remote access, use the following to allow the remote router to connect automatically to the UC500 VPN server.
On the UC500, add the following configuration via CLI:
crypto isakmp client configuration group EZVPN_GROUP_1
  save-password
On the remote device (870 or SR520), add the following configuration via CLI:
crypto ipsec client ezvpn EZVPN_REMOTE_CONNECTION_1
  username password
It is also strongly recommended that password encryption is configured on the remote device:
password encryption aes
key config-key password-encrypt

Similar Messages

  • Getting intermittent connection to internal resources from vpn remote connection

    Hi there,
    I have an intermittent issue happening on my company's firewall, and I'm at a loss as to how to troubleshoot further. I'm hoping someone can give me some tips or pointers in the right direction.
    We recently made some changes to our network, which included moving an ASA 5505 from one location to another. In moving this we also connected it to a different switch. It used to hang off a Cisco 3560, and now it hangs off a ProCurve 5406zl.
    The setup is that the ASA is connected on two ports to the HP, which is simply a layer 2 device sitting between the firewall and the uplink to our ISP. One port, e0/0, is the outside interface and is set to switchport access vlan 2. The second interface, e0/1, is set for vlan 1, also access mode. It has an IP of 10.0.0.2. The HP on the other end of that has an IP of 10.0.0.1. So outside VPN connections come through the HP to the ASA on e0/0, and back out the ASA on port e0/1 to reach devices on the internal network.
    What happens is that when a user connects to the VPN, they can reach internal resources intermittently. For example, I tried to ping an internal server IP address (let's say 10.0.0.23) from my laptop, while on the VPN, and pings failed. However I could ping that IP from the ASA itself. Another example is that during one VPN connection I was unable to connect to an internal web server, but once I disconnected and connected ahain I could reach the server fine.
    The intermittent nature of the problem made me think that it could be an ARP issue, that somehow the traffic is getting sent back out the wrong interface sometimes, hence the lack of communication. However when I did show switch mac-address | include mac address, using the base mac of the HP, I only saw the mac address of the HP on one interface, e0/1. That makes me think that things are working as they should. Although I guess maybe it should appear on both interfaces...? I don't know. Can anyone share some ideas of what the problem might be, or how I can most effectively troubleshoot this? It seems like the symptoms are indicative of some kind of rookie mistake, but for the life of me I can't figure out what it is.
    I appreciate your responses. Thanks.

    Hi Jeff, and thanks. I didn't change anything in the config actually. The IP ranges didn't change, nor did the IP of the ASA itself. In its old setting it hung off of an intermittent Cisco switch, let's say IP 10.100.0.25. There were two other switches that used VRRP with a shared IP of 10.100.10.1 and acted as the default gateway for all devices on the network, except the ASA. The gateway switches in turn used the ASA, 10.100.10.2, as the default gateway. So, internal traffic would flow through 10.100.0.1 unless it needed to access an external network, i.e. the WAN, in which case the switch at 10.100.10.1 would send the traffic to the ASA at 10.100.10.2. The ASA's default gateway was the public IP of our ISP.
    In the change we moved from using a Cisco core to an HP core, so the ASA was moved to hang directly off the HP. The HP was re-IP'd as 10.100.10.1, the ASA stayed the same. I didn't change any configuration on the ASA, and the only thing did to the HP was to change it's default gateway to point to the ASA (same as the old setup), and set the ports for the different vlans.
    What I've also found is that at times once I establish a vpn connection I cannot even ping the connected HP switch from my client machine, but I can ping it from the ASA. If I disconnect from the vpn and try again, it may work.  Here's some output based on commands in this link,
    http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a00807c35e7.shtml#s1. For this command I am attempting to first ping 10.100.10.1 (the HP switch) and then ssh to it.
    asa# capture capin interface inside match ip host 10.100.15.3 host 10.100$
    asa# show cap
    asa# show capture capin
    18 packets captured
       1: 11:00:24.574997 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request
       2: 11:00:24.577210 802.1Q vlan#1 P6 10.100.10.1 > 10.100.15.3: icmp: echo reply
       3: 11:00:25.585342 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request
       4: 11:00:26.576676 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request
       5: 11:00:27.584259 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request
       6: 11:00:28.577896 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request
       7: 11:00:29.590682 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request
       8: 11:00:30.579529 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request
       9: 11:00:31.588363 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request
      10: 11:00:32.588317 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request
      11: 11:00:38.699441 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S 2589950443:2589950443(0) win 65535
      12: 11:00:39.642651 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S 2589950443:2589950443(0) win 65535
      13: 11:00:40.645352 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S 2589950443:2589950443(0) win 65535
      14: 11:00:41.648815 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S 2589950443:2589950443(0) win 65535
      15: 11:00:42.649777 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S 2589950443:2589950443(0) win 65535
      16: 11:00:43.659832 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S 2589950443:2589950443(0) win 65535
      17: 11:00:45.654049 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S 2589950443:2589950443(0) win 65535
      18: 11:00:49.664699 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S 2589950443:2589950443(0) win 65535
    18 packets shown
    asa# show capture capin detail
    18 packets captured
       1: 11:00:24.574997 001d.45e5.85ce 441e.a16a.8b00 0x8100 102: 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request (ttl 64, id 38278)
       2: 11:00:24.577210 441e.a16a.8b00 001d.45e5.85ce 0x8100 102: 802.1Q vlan#1 P6 10.100.10.1 > 10.100.15.3: icmp: echo reply [tos 0xe0]  (ttl 255, id
       3: 11:00:25.585342 001d.45e5.85ce 441e.a16a.8b00 0x8100 102: 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request (ttl 64, id 9469)
       4: 11:00:26.576676 001d.45e5.85ce 441e.a16a.8b00 0x8100 102: 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request (ttl 64, id 50837)
       5: 11:00:27.584259 001d.45e5.85ce 441e.a16a.8b00 0x8100 102: 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request (ttl 64, id 24048)
       6: 11:00:28.577896 001d.45e5.85ce 441e.a16a.8b00 0x8100 102: 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request (ttl 64, id 57505)
       7: 11:00:29.590682 001d.45e5.85ce 441e.a16a.8b00 0x8100 102: 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request (ttl 64, id 8438)
       8: 11:00:30.579529 001d.45e5.85ce 441e.a16a.8b00 0x8100 102: 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request (ttl 64, id 64136)
       9: 11:00:31.588363 001d.45e5.85ce 441e.a16a.8b00 0x8100 102: 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request (ttl 64, id 24534)
      10: 11:00:32.588317 001d.45e5.85ce 441e.a16a.8b00 0x8100 102: 802.1Q vlan#1 P0 10.100.15.3 > 10.100.10.1: icmp: echo request (ttl 64, id 56295)
      11: 11:00:38.699441 001d.45e5.85ce 441e.a16a.8b00 0x8100 82: 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S [tcp sum ok] 2589950443:2589950
      12: 11:00:39.642651 001d.45e5.85ce 441e.a16a.8b00 0x8100 82: 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S [tcp sum ok] 2589950443:2589950
      13: 11:00:40.645352 001d.45e5.85ce 441e.a16a.8b00 0x8100 82: 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S [tcp sum ok] 2589950443:2589950
      14: 11:00:41.648815 001d.45e5.85ce 441e.a16a.8b00 0x8100 82: 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S [tcp sum ok] 2589950443:2589950
      15: 11:00:42.649777 001d.45e5.85ce 441e.a16a.8b00 0x8100 82: 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S [tcp sum ok] 2589950443:2589950
      16: 11:00:43.659832 001d.45e5.85ce 441e.a16a.8b00 0x8100 82: 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S [tcp sum ok] 2589950443:2589950
      17: 11:00:45.654049 001d.45e5.85ce 441e.a16a.8b00 0x8100 82: 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S [tcp sum ok] 2589950443:2589950
      18: 11:00:49.664699 001d.45e5.85ce 441e.a16a.8b00 0x8100 66: 802.1Q vlan#1 P0 10.100.15.3.57943 > 10.100.10.1.22: S [tcp sum ok] 2589950443:2589950
    18 packets shown
    asa# show capture capin trace                           
    7 packets captured
       1: 11:04:53.510685 802.1Q vlan#1 P0 10.100.15.3.57954 > 10.100.10.1.22: S 1151368455:1151368455(0) win 65535
       2: 11:04:54.491414 802.1Q vlan#1 P0 10.100.15.3.57954 > 10.100.10.1.22: S 1151368455:1151368455(0) win 65535
       3: 11:04:55.482488 802.1Q vlan#1 P0 10.100.15.3.57954 > 10.100.10.1.22: S 1151368455:1151368455(0) win 65535
       4: 11:04:56.499119 802.1Q vlan#1 P0 10.100.15.3.57954 > 10.100.10.1.22: S 1151368455:1151368455(0) win 65535
       5: 11:04:57.489308 802.1Q vlan#1 P0 10.100.15.3.57954 > 10.100.10.1.22: S 1151368455:1151368455(0) win 65535
       6: 11:04:58.493275 802.1Q vlan#1 P0 10.100.15.3.57954 > 10.100.10.1.22: S 1151368455:1151368455(0) win 65535
       7: 11:05:00.495473 802.1Q vlan#1 P0 10.100.15.3.57954 > 10.100.10.1.22: S 1151368455:1151368455(0) win 65535
    7 packets shown
    Here are some additional potentially relevant sections of my ASA config (public IPs changed for security):
    asa# show route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
           i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
           * - candidate default, U - per-user static route, o - ODR
           P - periodic downloaded static route
    Gateway of last resort is 1.1.1.125 to network 0.0.0.0
    C    1.1.1.64 255.255.255.192 is directly connected, outside
    S    10.100.15.3 255.255.255.255 [1/0] via 1.1.1.125, outside
    S    10.105.0.0 255.255.0.0 [1/0] via 10.100.10.1, inside
    C    10.100.0.0 255.255.0.0 is directly connected, inside
    S*   0.0.0.0 0.0.0.0 [255/0] via 1.1.1.125, outside
    Thanks in advance for your suggestions and observations.

  • Vpn to auto reconnect/connect

    If anyone who uses vpn to connect online knows this is a problem in Tiger, everytime it disconnect or goes to sleep the vpn will not reconnect itself auto. I have to manually connect which makes it very annoying if I am leaving my computer over night to download something hoping to have it in the morning but I don't because it got disconnected halfway through. Are there any ways to make it reconnect automatically?
    Thanks,
    John

    Hello,
    So in this case, I think that I have to use the Windows VPN client. But do I can make it compatible with a IOS VPN 12.4.10 ? Because I using a router for the VPN Server.
    Regards,
    Omar

  • VPN Auto Reconnect

    Hello, I'm using VPN(PPTP) to connect to my office but sometimes the connection is not stable and I got a lot of disconnection. Is there a way to auto reconnect to the VPN Server?

    Seems like you should be able to Script it, but I wonder if this Widget might help, seems to have a reconnect feature for PPP, so maybe more...
    http://www.apple.com/downloads/macosx/networking_security/netmonitor.html

  • Make VPN 1) reconnect to resume 2) reconnect on new connection

    Currently the VPN connection get's disconnected if the phone is in idle state for a while. I assume it has to do with networking getting into idle state to preserve the battery life. However, when I resume working on iPhone the VPN connection should reconnect automatically. Right now I have to go through the menu every time to reconnect. That's a major security problem. If I don't reconnect it manually I am basically using the device without VPN. I am breaching security policy of our company and if data get's lost I will be on line for it. Back in those old Nokia days I could make the VPN encrypted connection mandatory and keep it permanently on.
    Same happense in case when the connection (Wifi) get's lost and I reconnect again (same or different network). Same here, VPN would be disconnected and I have to manually reconnect. I can have the best secured connection SSL or L2DP/IPSec on the server side but what gives if the VPN on iPhone has the major bug above and poorly implemented. This has been persistant problem for many months and still not resolved.

    Not sure if this helps, just an idea: in the iOS config profiles, when setting up the cisco VPN, if you use it in cert based mode, you can specify domains, which always invoke the VPN connection, even if was disconnected a while ago. I think this is a system wide settings, so if a third party app tries to connect to that domain, it starts the VPN too. We did not use or test this (only the mode which involves an RSA token and frequent reconnections ), but I am avare the possibility.

  • Remotely connect to network with VPN

    I'd like to remotely connect to our local network using VPN. I've tried vnc://external_IP.., but it fails with a message that screen sharing is not engaged.
    How can I access this local network and specifically, individual Macs on the network?

    First, you need to establish which VPN protocols can be used to connect to your network - your IT people should be able to give you this information. If it's a Cisco or L2TP/PPTP VPN connection, you should be able to use the Network Preferences to create a new VPN connection and use the appropriate login information to connect.
    If you have an IPSec VPN system, you can use the free IPSecuritas to connect.
    Either way, you need to get the detailed connection parameters from your network admin before you can connect from the outside world. Once you're connected, you should be able to connect to any local services (screen sharing, file sharing, etc) using local addresses instead of external IP addresses.
    hope that helps
    Matt

  • Remote connection to SAP(internet VPN) with Juniper Netscreen 5XT

    Hi,
    I am now setting up the remote connection (internet VPN) with the network device Juniper Netscreen 5XT.
    Since I am not a network expert, I met some trouble on it.
    We have prepared 2 public IP address. 61.xx.xx.45/29 for SAP router and 61.xx.xx.46/29 for setting up the VPN tunnel.
    And we use 192.168.1.10/255.255.255.0(for example) as the private IP address of SAP router, and use NAT to map 192.168.1.10 to 61.xx.xx.45/29...
    Any way, although the VPN tunnel can be set up, I can not ping the SAP router@SAP side.
    But with the help of SAP, I did the test, use 202.xx.xx.xx(public IP address) as private IP address of SAP router, and did not use NAT, and registered in SAP side,I can ping the SAP router@SAP side.
    I also think that use NAT of SAP router is a normal way to settup the internet VPN.
    What's wrong with it?
    Would you please give me some suggestion on it?
    Thanks in advance.
    Best regards,
    Randy

    It is OK after replace the network device as the cisco router.

  • Is it possible to get Win 7 to auto start VPN connection?

    Hey all,
    Is it possible to get Windows 7 to auto start VPN connection? Or can you recommend a 3rd Party VPN client application?
    thanks

    To make a batch file. exe or cmd, you need to open a notepad. Go to Start-All Programs -Accessories and click on Notepad. In notepad type in
    rasphone -d ****** where is ****** a name of your VPN connection
    For example: your Vpn connection is called My VPN
    The command line will be:
    rasphone -d My VPN
    Then, save as .cmd or .bat for example. Vpn.cmd
    2. Then, Go to Start-All programs -Startup Folder. Click on it with a mouse right button and drag the Vpn.cmd file (file you've made in a notepad). Now, you should see it in startup folder.
    3 Right click on your Vpn connection, choose properties. Go to the ,,Option menu,, and Unmark (if marked) -prompt for user name and password, certificate etc. And press Ok.
    Restart the laptop. if everything is ok, you will see appearing Command prompt after Windows logging. It connects automatically and disappears.

  • Communication problem from the vpn-anyconnect to easy-vpn-remote

    Hi Team,
    I have a communication problem from the vpn-anyconnect to easy-vpn-remote, I´ll explain better bellow and see the attached
    topology:
    1) VPN Tunnel between HQ to Branch Office - That´s OK
    2) VPN Tunnel between Client AnyConnect to HQ - That´s OK
    The idea is that the Client Anyconnect is to reach the LAN at Branch Office, but did not reach.
    The communication is stablished just when I start a session (icmp and/or rdp) from Branch Office to the Client AnyConnect,
    in this way, the communication is OK, but just during a few minutes.
    Could you help me?
    Bellow the IOS version and configurations
    ASA5505 Version 8.4(7)23 (headquarters)
    ASA5505 Version 8.4(7)23 (Branch)
    **************** Configuration Easy VPN Server (HQ) **************** 
    crypto dynamic-map DYNAMIC-MAP 5 set ikev1 transform-set ESP-AES-256-SHA
    crypto map outside-link-2_map 1 ipsec-isakmp dynamic DYNAMIC-MAP
    crypto map outside-link-2_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
    crypto map outside-link-2_map interface outside-link-2
    access-list ACL_EZVPN standard permit 10.0.0.0 255.255.255.0 
    access-list ACL_EZVPN standard permit 192.168.1.0 255.255.255.0 
    access-list ACL_EZVPN standard permit 192.168.50.0 255.255.255.0 
    access-list ACL_EZVPN standard permit 10.10.0.0 255.255.255.0 
    group-policy EZVPN_GP internal
    group-policy EZVPN_GP attributes
     split-tunnel-policy tunnelspecified
     split-tunnel-network-list value ACL_EZVPN
     nem enable 
    tunnel-group EZVPN_TG type remote-access
    tunnel-group EZVPN_TG general-attributes
     default-group-policy EZVPN_GP
    tunnel-group EZVPN_TG ipsec-attributes
     ikev1 pre-shared-key *****
    object-group network Obj_VPN_anyconnect-local
     network-object 192.168.1.0 255.255.255.0
     network-object 192.168.15.0 255.255.255.0
    object-group network Obj-VPN-anyconnect-remote
     network-object 192.168.50.0 255.255.255.0
    object-group network NAT_EZVPN_Source
     network-object 192.168.1.0 255.255.255.0
     network-object 10.10.0.0 255.255.255.0
    object-group network NAT_EZVPN_Destination
     network-object 10.0.0.0 255.255.255.0
    nat (inside,outside-link-2) source static Obj_VPN_anyconnect-local Obj_VPN_anyconnect-local destination static Obj-VPN-
    anyconnect-remote Obj-VPN-anyconnect-remote no-proxy-arp route-lookup
    nat (inside,outside-link-2) source static NAT_EZVPN_Source NAT_EZVPN_Source destination static NAT_EZVPN_Destination 
    NAT_EZVPN_Destination no-proxy-arp route-lookup
    nat (outside-link-2,outside-link-2) source static Obj-VPN-anyconnect-remote Obj-VPN-anyconnect-remote destination static 
    NAT_EZVPN_Destination NAT_EZVPN_Destination no-proxy-arp route-lookup
    **************** Configuration VPN AnyConnect (HQ) **************** 
    webvpn
     enable outside-link-2
     default-idle-timeout 60
     anyconnect-essentials
     anyconnect image disk0:/anyconnect-win-2.5.2014-k9.pkg 1
     anyconnect profiles Remote_Connection_for_TS_Users disk0:/remote_connection_for_ts_users.xml
     anyconnect enable
     tunnel-group-list enable
    access-list split-tunnel standard permit 192.168.1.0 255.255.255.0 
    access-list split-tunnel standard permit 192.168.15.0 255.255.255.0 
    access-list split-tunnel standard permit 10.0.0.0 255.255.255.0 
    group-policy clientgroup internal
    group-policy clientgroup attributes
     wins-server none
     dns-server value 192.168.1.41
     vpn-tunnel-protocol ssl-client 
     split-tunnel-policy tunnelspecified
     split-tunnel-network-list value split-tunnel
     default-domain value ipconnection.com.br
     webvpn       
      anyconnect keep-installer installed
      anyconnect ssl rekey time 30
      anyconnect ssl rekey method ssl
      anyconnect profiles value Remote_Connection_for_TS_Users type user
      anyconnect ask none default anyconnect
    tunnel-group sslgroup type remote-access
    tunnel-group sslgroup general-attributes
     address-pool vpnpool
     authentication-server-group DC03
     default-group-policy clientgroup
    tunnel-group sslgroup webvpn-attributes
     group-alias IPConnection-vpn-anyconnect enable
    object-group network Obj_VPN_anyconnect-local
     network-object 192.168.1.0 255.255.255.0
     network-object 192.168.15.0 255.255.255.0
    object-group network Obj-VPN-anyconnect-remote
     network-object 192.168.50.0 255.255.255.0
    object-group network NAT_EZVPN_Source
     network-object 192.168.1.0 255.255.255.0
     network-object 10.10.0.0 255.255.255.0
    object-group network NAT_EZVPN_Destination
     network-object 10.0.0.0 255.255.255.0
    nat (inside,outside-link-2) source static Obj_VPN_anyconnect-local Obj_VPN_anyconnect-local destination static Obj-VPN-
    anyconnect-remote Obj-VPN-anyconnect-remote no-proxy-arp route-lookup
    nat (inside,outside-link-2) source static NAT_EZVPN_Source NAT_EZVPN_Source destination static NAT_EZVPN_Destination 
    NAT_EZVPN_Destination no-proxy-arp route-lookup
    nat (outside-link-2,outside-link-2) source static Obj-VPN-anyconnect-remote Obj-VPN-anyconnect-remote destination static 
    NAT_EZVPN_Destination NAT_EZVPN_Destination no-proxy-arp route-lookup

    Hi,
    the communication works when you send traffic from easyvpn branch side because it froms the IPSEC SA for local subnet and anyconnect HQ pool. The SA will only form when branch initiates the connection as this is dynamic peer connection to HQ ASA.
    when there no SA between branch and HQ for this traffic, HQ ASA has no clue about where to send the traffic from anyconnect to branch network.
    I hope it explains the cause.
    Regards,
    Abaji.

  • My Apple TV is showing no signs of reconnecting a remote! Help!

    I cant get my 3rd generation Apple TV to connect to any of my remotes. I've tried restarting it & trying to reconnect the remote or remote app to the Apple TV but the TV shows no signs of a connection. Ive tried all the troubleshooting things for reconnecting the remote & none of them work. The TV still comes on but only if I unplug it & plug it back in. Pleaseeee help me!!

    Welcome to the Apple Community.
    Your Apple TV may have become paired with another remote. Hold the remote close to and pointed at the Apple TV, hold down the menu and Rewind buttons together for 6 seconds or until you see a broken chain icon on screen.

  • Remote Connecting to a PC from my Mac

    Hi, I am wondering how I can essentially "screen share" with my friend using a pc. By this I mean they share their screen. I've been looking on the internet for answers and I have found multiple hits for connecting from PC to Mac but not the other way around. In addition, from what I have read, nothing was vert step-by-step. I heard about TightVNC so I told my friend to download it and that I would be able to remote connect to them using what I have in Leopard. However, it's at this point that I am completely clueless on how to actually establish that connection.
    I would like to know what the PC user needs to do and secondly what I would need to know/type in in order to connect to their pc and control their screen.
    Thanks

    When it says "computer:________" Connect. I put in the PC's ip address (I'm pretty sure it's the right one, I will ask again if not).
    Do they have a home router between their ISP connection and their PC? If so, their router needs to forward port 3389 from the Internet to their PC. And the IP address you need is the IP address assigned to the router by the ISP. They could access a web site such as <http://whatismyip.com> to find out their public IP address.
    1. Who's user name and Password? The PC User's or My account name and my password? If theirs, they don't have a name or password, they turn on the computer and the desktop is there, without having to log in. Do they need to have one (an account or w/e).
    The PC's Username and Password. And yes they do have a username and password. They may not remember what they setup, since they have it set to auto login. I do NOT know how to find out this information, as I am a Mac and/or Unix kind of guy
    2. Domain. This is optional is it not? Can the IP go in here?
    This is the Windows account domain, and nothing to do with IP addresses nor DNS. Mostly they have WORKGROUP or MSHOME as their domain. If it is optional, then ignore it.
    Here are some alternative approaches. Sign-up for a free LogMeIn.com account <http://logmein.com>. Have them install the LogMeIn.com server and associate it with the LogMeIn.com account you created. Now you can use your web browser (Safari) to login to the LogMeIn.com account, and from there connect to their PC's LogMeIn.com server.
    The current version of Skype allows screen sharing, however, I think it is a view ONLY connection. That is to say, you can watch their screen, but you can not control their keyboard, nor their mouse. <http://skype.com>
    Another choice might be a purchased copy of GoToMyPC (there are both Mac and PC versions).
    There is also TimBukTu from <http://www.netopia.com> which is also cross platform.
    VNC has also been mentioned. Again, VNC needs router port forwarding, only VNC needs port 5900 forwarded. TightVNC, UltraVNC, RealVNC are possible Window's VNC servers. JollysFastVNC (highly recommended), Chicken of the VNC, or Mac OS X built-in Screen Sharing (Finder -> Go -> Connect to Server -> vnc://ip.addr.of.pc). I only recommend the built-in Mac OS X Screen Shring if the other system is on the same high speed network, or if connecting to another Mac OS X system.

  • Rv220w pptp remote connection use two ip address

                       Hello, I am a long time quick vpn user. I recently purchased a new windows 8.1 pro and the quickvpn fails. After many searches It appears this is a know issue and I should look for another way to connect. I choose to use the PPTP option. I set it up and everything it going well. however I have one slight issues when I try to use an ip specific software on my system that has remotely made the vpn pptp connection. I ran the cmd and check the ipconfig and see now that my computer has two ip address one from the air card I am using to connect to the internet 192.168.0.192 and one that the pptp vpn connection assigns 10.0.0.21 my issue is for my ip specific software to work I am forced to register both ip address for the same computer and each license from the vendor is good for one computer one ip address so this is going to double my operating cost. can anyone help.
    Please let me know if you need more info I will do my best to gather. Thanks in advance.

    I was able to make a quickvpn connection to my rv220w router via a wifi connection. I am unsure of the exact change made and I am now wondering if anyone can review this log and tell me what happened to allow the connection. At first I was very taken back and had to triple check to make sure it was working. Below is today’s router log at 18:00 I was able to make a successful quickvpn connection. Anyone see how? The rest of the morning I was trying repeatedly to make a connection
    is this important? "
    2014-02-01 19:04:31: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2000-01-01 00:00:36: [rv220w][IKE] INFO:  IKE started
    2014-02-01 12:47:49: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "joey01"
    2014-02-01 12:47:49: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "joey01"
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[500].
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>166.155.0.67[500]
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  For 166.155.0.67[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[500]
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 166.155.0.67[4500]
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:3671b391a56b4bee:52b561ece6e2aa09
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 12:48:01: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=266310588(0xfdf93bc)
    2014-02-01 12:48:01: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3530213431(0xd26ac837)
    2014-02-01 12:49:19: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=3671b391a56b4bee:52b561ece6e2aa09.
    2014-02-01 12:49:20: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:3671b391a56b4bee:52b561ece6e2aa09
    2014-02-01 13:36:02: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3530213431(0xd26ac837)
    2014-02-01 13:36:02: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=266310588(0xfdf93bc)
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:1d7d95d359ea4f66:d71a5efcd843af68
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 13:46:51: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 13:46:51: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 13:46:51: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 13:46:51: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=225127593(0xd6b2ca9)
    2014-02-01 13:46:51: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=1534791298(0x5b7b0e82)
    2014-02-01 13:48:34: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=1d7d95d359ea4f66:d71a5efcd843af68.
    2014-02-01 13:48:35: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:1d7d95d359ea4f66:d71a5efcd843af68
    2014-02-01 14:34:01: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "alohavpn"
    2014-02-01 14:34:01: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "alohavpn"
    2014-02-01 14:34:06: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.250/8<->166.142.243.242/30
    2014-02-01 14:34:06: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 14:34:06: [rv220w][IKE] INFO:  Initiating new phase 1 negotiation: 192.168.0.10[500]<=>166.142.243.242[500]
    2014-02-01 14:34:06: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 14:34:06: [rv220w][IKE] INFO:   [ident_i1send:180]: XXX: NUMNATTVENDORIDS: 3
    2014-02-01 14:34:06: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 4
    2014-02-01 14:34:06: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 8
    2014-02-01 14:34:06: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 9
    2014-02-01 14:34:27: [rv220w][IKE] INFO:  accept a request to establish IKE-SA: 166.142.243.242
    2014-02-01 14:34:27: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 14:34:37: [rv220w][IKE] ERROR:  Phase 2 negotiation failed due to time up waiting for phase1. ESP 166.142.243.242->192.168.0.10
    2014-02-01 14:34:52: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=1534791298(0x5b7b0e82)
    2014-02-01 14:34:52: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=225127593(0xd6b2ca9)
    2014-02-01 14:34:58: [rv220w][IKE] ERROR:  Invalid SA protocol type: 0
    2014-02-01 14:34:58: [rv220w][IKE] ERROR:  Phase 2 negotiation failed due to time up waiting for phase1.
    2014-02-01 14:35:06: [rv220w][IKE] ERROR:  Phase 1 negotiation failed due to time up for 166.142.243.242[500]. a8c862e86c5d65ea:0000000000000000
    2014-02-01 14:35:18: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.250/8<->166.142.243.242/30
    2014-02-01 14:35:18: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 14:35:18: [rv220w][IKE] INFO:  Initiating new phase 1 negotiation: 192.168.0.10[500]<=>166.142.243.242[500]
    2014-02-01 14:35:18: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 14:35:18: [rv220w][IKE] INFO:   [ident_i1send:180]: XXX: NUMNATTVENDORIDS: 3
    2014-02-01 14:35:18: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 4
    2014-02-01 14:35:18: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 8
    2014-02-01 14:35:18: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 9
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'isakmp_chkph1there'.
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  IPSec configuration with identifier "alohavpn" deleted sucessfully
    2014-02-01 14:35:29: [rv220w][IKE] WARNING:  no phase2 bounded.
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  Purged ISAKMP-SA with spi=44ad4081d881ca39:0000000000000000.
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'purge_remote'.
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'isakmp_ph1resend'.
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  IKE configuration with identifier "alohavpn" deleted sucessfully
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:e7ff5eebc74fe18e:26a523a055bdd961
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 14:45:38: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=233645680(0xded2670)
    2014-02-01 14:45:38: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3473253380(0xcf05a404)
    2014-02-01 14:47:04: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=e7ff5eebc74fe18e:26a523a055bdd961.
    2014-02-01 14:47:05: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:e7ff5eebc74fe18e:26a523a055bdd961
    2014-02-01 14:49:00: [rv220w][IKE] ERROR:  Could not find configuration for 99.120.21.158[500]
    2014-02-01 14:49:01: [rv220w][IKE] ERROR:  Could not find configuration for 99.120.21.158[500]
    2014-02-01 14:49:03: [rv220w][IKE] ERROR:  Could not find configuration for 99.120.21.158[500]
    2014-02-01 14:49:07: [rv220w][IKE] ERROR:  Could not find configuration for 99.120.21.158[500]
    2014-02-01 14:49:42: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "tim000"
    2014-02-01 14:49:42: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "tim000"
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[500].
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.120.21.158[500]
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  For 99.120.21.158[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[500]
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.120.21.158[4500]
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:c37856d7496f4bc0:d866a785808f18ff
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 14:49:45: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 14:49:45: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 14:49:45: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 14:49:45: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=201496659(0xc029853)
    2014-02-01 14:49:45: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=3623586341(0xd7fb8a25)
    2014-02-01 14:51:02: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=c37856d7496f4bc0:d866a785808f18ff.
    2014-02-01 14:51:03: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:c37856d7496f4bc0:d866a785808f18ff
    2014-02-01 15:33:39: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3473253380(0xcf05a404)
    2014-02-01 15:33:39: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=233645680(0xded2670)
    2014-02-01 15:37:46: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=3623586341(0xd7fb8a25)
    2014-02-01 15:37:46: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=201496659(0xc029853)
    2014-02-01 15:38:35: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 15:38:35: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 15:38:55: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 15:38:55: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 15:38:55: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 15:40:28: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:40:28: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 15:40:28: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:40:28: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 15:40:28: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 15:40:28: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 15:40:28: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 15:40:47: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 15:40:47: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 15:40:55: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 15:40:55: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 15:40:55: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 15:44:52: [rv220w][IKE] WARNING:  no phase2 found for "joey01"
    2014-02-01 15:44:52: [rv220w][IKE] INFO:  IPSec configuration with identifier "joey01" deleted sucessfully
    2014-02-01 15:44:52: [rv220w][IKE] WARNING:  no phase1 found for "joey01"
    2014-02-01 15:44:52: [rv220w][IKE] INFO:  IKE configuration with identifier "joey01" deleted sucessfully
    2014-02-01 15:44:52: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "joey01"
    2014-02-01 15:44:52: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "joey01"
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[500].
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>166.155.0.67[500]
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  For 166.155.0.67[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[500]
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 166.155.0.67[4500]
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:26214a2b8fde97de:0f3107405c30ec29
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 15:45:04: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=171519328(0xa392d60)
    2014-02-01 15:45:04: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=995888774(0x3b5c0e86)
    2014-02-01 15:46:19: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=26214a2b8fde97de:0f3107405c30ec29.
    2014-02-01 15:46:20: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:26214a2b8fde97de:0f3107405c30ec29
    2014-02-01 15:47:22: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:47:22: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 15:47:22: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:47:22: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 15:47:22: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 15:47:22: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 15:47:22: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[4500].
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[4500]
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:95b646cb75adbb50:0ed9f31398ea14aa
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 15:48:38: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=254599107(0xf2cdfc3)
    2014-02-01 15:48:38: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2917092721(0xaddf4d71)
    2014-02-01 15:50:17: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=95b646cb75adbb50:0ed9f31398ea14aa.
    2014-02-01 15:50:18: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:95b646cb75adbb50:0ed9f31398ea14aa
    2014-02-01 15:50:23: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 15:50:23: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 15:50:39: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 15:50:39: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 15:50:39: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 15:51:12: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:51:12: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 15:51:12: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:51:12: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 15:51:12: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 15:51:12: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 15:51:12: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 16:33:05: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=995888774(0x3b5c0e86)
    2014-02-01 16:33:05: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=171519328(0xa392d60)
    2014-02-01 16:36:39: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2917092721(0xaddf4d71)
    2014-02-01 16:36:39: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=254599107(0xf2cdfc3)
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:6a803bd2c559ba70:d005a2ba6e84b619
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 16:43:51: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=98566123(0x5dfffeb)
    2014-02-01 16:43:51: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3231695043(0xc09fc0c3)
    2014-02-01 16:45:28: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=6a803bd2c559ba70:d005a2ba6e84b619.
    2014-02-01 16:45:29: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:6a803bd2c559ba70:d005a2ba6e84b619
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[4500].
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[4500]
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:6852c876e1425084:944da52b84937c9a
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 16:47:30: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 16:47:30: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=103279842(0x627ece2)
    2014-02-01 16:47:30: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2492252444(0x948cc11c)
    2014-02-01 16:48:47: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=6852c876e1425084:944da52b84937c9a.
    2014-02-01 16:48:48: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:6852c876e1425084:944da52b84937c9a
    2014-02-01 17:31:52: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3231695043(0xc09fc0c3)
    2014-02-01 17:31:52: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=98566123(0x5dfffeb)
    2014-02-01 17:35:31: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2492252444(0x948cc11c)
    2014-02-01 17:35:31: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=103279842(0x627ece2)
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:610f4e8b8a701292:1b5b4fac9129d2cc
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=5442197(0x530a95)
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=281087573(0x10c10e55)
    2014-02-01 17:43:58: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=610f4e8b8a701292:1b5b4fac9129d2cc.
    2014-02-01 17:43:59: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:610f4e8b8a701292:1b5b4fac9129d2cc
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[4500].
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[4500]
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:34fbdc2521b83861:4f04939eefba3853
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=232320279(0xdd8ed17)
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2789259203(0xa640b7c3)
    2014-02-01 17:48:02: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=34fbdc2521b83861:4f04939eefba3853.
    2014-02-01 17:48:03: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:34fbdc2521b83861:4f04939eefba3853
    2014-02-01 18:30:42: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=281087573(0x10c10e55)
    2014-02-01 18:30:42: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=5442197(0x530a95)
    2014-02-01 18:34:26: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2789259203(0xa640b7c3)
    2014-02-01 18:34:26: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=232320279(0xdd8ed17)
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:11605c3a8435559f:38b8c86ef5bc8173
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=116125724(0x6ebf01c)
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=712542982(0x2a788b06)
    2014-02-01 18:43:05: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=11605c3a8435559f:38b8c86ef5bc8173.
    2014-02-01 18:43:06: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:11605c3a8435559f:38b8c86ef5bc8173
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[4500].
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[4500]
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:78a21d9a6ff7a028:d143c9317afa091b
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 18:45:12: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=129883376(0x7bddcf0)
    2014-02-01 18:45:12: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=654476335(0x2702842f)
    2014-02-01 18:46:32: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=78a21d9a6ff7a028:d143c9317afa091b.
    2014-02-01 18:46:33: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:78a21d9a6ff7a028:d143c9317afa091b
    2014-02-01 19:04:30: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 19:04:30: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 19:04:31: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 19:04:31: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 19:04:31: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 19:05:13: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 19:05:13: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 19:05:13: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 19:05:14: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 19:05:14: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 19:05:14: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 19:05:14: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 19:05:53: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 19:05:53: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 19:06:07: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 19:06:07: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 19:06:07: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 19:06:27: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 19:06:27: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 19:06:27: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 19:06:27: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 19:06:27: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 19:06:27: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 19:06:27: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 19:09:21: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 19:09:21: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Configuration found for 99.101.94.86[500].
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  For 99.101.94.86[500], Selected NAT-T version: RFC 3947
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.101.94.86[500]
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Configuration found for 99.101.94.86[500].
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  For 99.101.94.86[500], Selected NAT-T version: RFC 3947
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.101.94.86[500]
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.101.94.86[4500]
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:c45d81319a7961c2:df7f2a51e8084be5
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 19:09:34: [rv220w][IKE] NOTIFY:  The packet is retransmitted by 99.101.94.86[500].
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.101.94.86[0]
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.0.192/32
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  Adjusting peer's encmode 3(3)->Tunnel(1)
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.101.94.86[4500]
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:51bf7e3f5283a021:c319b19d85b0abd0
    2014-02-01 19:09:35: [rv220w][IKE] ERROR:  wrong state 8.
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.101.94.86->192.168.0.10 with spi=43713598(0x29b043e)
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.101.94.86 with spi=2920045730(0xae0c5ca2)
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Configuration found for 99.101.94.86[500].
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  For 99.101.94.86[500], Selected NAT-T version: RFC 3947
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=51bf7e3f5283a021:c319b19d85b0abd0.
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.101.94.86[500]
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.101.94.86[4500]
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:518570911a48e055:e1b21587fbe64a7d
    2014-02-01 19:10:34: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.101.94.86[4500] with spi:51bf7e3f5283a021:c319b19d85b0abd0
    2014-02-01 19:11:31: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=518570911a48e055:e1b21587fbe64a7d.
    2014-02-01 19:11:32: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.101.94.86[4500] with spi:518570911a48e055:e1b21587fbe64a7d
    2014-02-01 19:29:23: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=712542982(0x2a788b06)
    2014-02-01 19:29:23: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=116125724(0x6ebf01c)
    2014-02-01 19:33:13: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=654476335(0x2702842f)
    2014-02-01 19:33:13: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=129883376(0x7bddcf0)
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:86a51befd7ee8b38:1c072d85c8c7ab2e
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 19:40:17: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=131309239(0x7d39eb7)
    2014-02-01 19:40:17: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=656105156(0x271b5ec4)
    2014-02-01 19:41:35: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=86a51befd7ee8b38:1c072d85c8c7ab2e.
    2014-02-01 19:41:36: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:86a51befd7ee8b38:1c072d85c8c7ab2e
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[4500].
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[4500]
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:e1442468d0529bbe:f66c9601351bd3a2
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 19:43:58: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=191762664(0xb6e10e8)
    2014-02-01 19:43:58: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=3118196926(0xb9dbe8be)
    2014-02-01 19:45:02: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=e1442468d0529bbe:f66c9601351bd3a2.
    2014-02-01 19:45:03: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:e1442468d0529bbe:f66c9601351bd3a2
    2014-02-01 19:57:36: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.101.94.86 with spi=2920045730(0xae0c5ca2)
    2014-02-01 19:57:36: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.101.94.86->192.168.0.10 with spi=43713598(0x29b043e)
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Configuration found for 99.101.94.86[500].
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  For 99.101.94.86[500], Selected NAT-T version: RFC 3947
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.101.94.86[500]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.101.94.86[4500]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:5fbfcd9413b4c0f5:76e81b7495bfa7c8
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.101.94.86[0]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.0.192/32
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Adjusting peer's encmode 3(3)->Tunnel(1)
    2014-02-01 19:59:09: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.101.94.86->192.168.0.10 with spi=267963700(0xff8cd34)
    2014-02-01 19:59:09: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.101.94.86 with spi=2847327220(0xa9b6c3f4)
    2014-02-01 20:04:12: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'pk_recvupdate'.
    2014-02-01 20:04:12: [rv220w][IKE] INFO:  Purged IPsec-SA with proto_id=ESP and spi=2847327220(0xa9b6c3f4).
    2014-02-01 20:04:12: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=5fbfcd9413b4c0f5:76e81b7495bfa7c8.
    2014-02-01 20:04:13: [rv220w][IKE] WARNING:  no phase2 found for "happy00"
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.101.94.86[4500] with spi:5fbfcd9413b4c0f5:76e81b7495bfa7c8
    2014-02-01 20:04:13: [rv220w][IKE] WARNING:  no phase2 bounded.
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  Sending Informational Exchange: delete payload[]
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  Purged IPsec-SA with spi=2920045730(0xae0c5ca2).
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  Purged IPsec-SA with spi=267963700(0xff8cd34).
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  Purged IPsec-SA with spi=43713598(0x29b043e).
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  Purged ISAKMP-SA with spi=c45d81319a7961c2:df7f2a51e8084be5.
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'purge_remote'.
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 20:04:13: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 20:04:13: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 20:04:13: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 20:04:13: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 20:06:01: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 20:06:01: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 20:06:07: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 20:06:07: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 20:06:07: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 20:07:25: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 20:07:25: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 20:07:25: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 20:07:25: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 20:07:25: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 20:07:25: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 20:07:25: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 20:09:58: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 20:09:58: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Configuration found for 99.101.94.86[500].
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  For 99.101.94.86[500], Selected NAT-T version: RFC 3947
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.101.94.86[500]
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 20:10:12: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.101.94.86[4500]
    2014-02-01 20:10:12: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:1e81ce312812da50:569671b6b2a1ad6a
    2014-02-01 20:10:12: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]

  • Solution manager Remote Connection issues

    Hi
    I'm currently in the process of setting up Solution Manager 7.1 on windows Server 2008r2 using central system.
    I did the prerequisite check & the Solman installation and i'm actuallly working on the post-installation steps.
    I'm experiencing difficulty with the step : "Configure Remote Connection to SAP".
    I followed the informations provided on :   http://service.sap.com/remoteconnection
    In the technical prerequesite you have to set up a connection to sap support.
    So i have to choose a connection type : I selected Internet connection so my first question is : do we need "VPN with SNC" or "VPN OR SNC" ?
    I personnaly understood VPN or SNC.
    So from here i decided to use SNC.
    The first step was to set up & configure the SAProuter. I decided to do it on an another computer on the same domain ( not on the same computer where Solution Manager is installed ) but i'm not sure it is necesary
    I assume I can install Saprouter on the same location as the Solution manager? do you recommend it ?
    The Basic Functions testing with niping is working.
    The next step is : "establish Internet Connections"
    So now i can choose between SNC or VPN : my goal is to establish the connection as fast as possible.
    I actually don't have a switch available ( i can get one if necesary but time is running ... ) so i'm opting for the SNC solution.
    I tryed to get the certificate for the saprouter but i don't have a register SAProuter, but when i opened a customer messager for component  XX-SER-NET, SAP answered about the impossibility to access SAP service Backbone with an SNC , saying that i will need to register a VPN site to site connection to SAP => i don't get it .... Can someone explain it to me ?
    So please can one of you guru's tell me how to set this remote connection :
    -which materials ( server / switch / firewalls ) ?
    -where to get the right documentation ?
    -What about DMZ ?
    -I have a single IP Address is that enough ? ( setting up nat for port  3299 )
    - do i have to contact a service provider ?
    My idea was initially to set up the SAProuter on the same computer as the SOLMAN setup & use SNC communication  to communicate with SAP but it doesn't seems that easy. Do i need separate installation for Saprouter <=> Solution Manager. ?
    What's the minimal infrastructure to establish this connection ?
    In addition to that, after configuring the SAProuter, i had trouble with the SAPMMC : on my system , on the instance 0 , the process disp+work.EXE  won't run ( yellow light )and i can't find where i made a mistake if you have suggestions ...
    Really need your help, i'm on a short deadline ... Any help, even incomplete, would be appreciated.
    Thanks a lot.

    Thx for the answer.
    I actually managed to register my saprouter with SAP and was granted with CN/OU & connection informations.
    I followed this guide : http://service.sap.com/saprouter-sncdoc  with the addition of this guide : http://wiki.sdn.sap.com/wiki/display/Basis/SAProuterviaSNC.
    My first issue : I'm running with a Windows server 2008 r2 enterprise edition 64 bits with a processor Intel Xeon 2.4ghz ( dualcore). so i decided to use the crypto folder "nt-x86_64"
    For the environment variable i set as System variables SECUDIR = C:\usr\sap\saprouter and SNC_LIB = C:\usr\sap\saprouter\nt-x86_64\sapcrypto.dll 
    The generation/install of the certificate is alright ( sapgenpse get_my_name -v -n Issuer is OK )
    using the command :saprouter -r -K "p:CN=mycn, OU=myOUnbr, OU=SAProuter, O=SAP, C=DE" i have
    I get the following message :  trc file     dev_rout
                                                    no ligging active
    Its strange cause it looks like its running but when i check the services running on windows saprouter isn't started .... How to know if SAProuter is running right ?
    If i folow the SAP procedure : Step 3 : test of the ip connection by the customer : SAP Remote Services : technical preparation ( see SAP Note 812386 ) : it's ask in the note to implement note 766505 via SNOTE : i get the following error msg : Error in remote connection to destination SAPOSS : Error when opening an RFC connection ( LB: Hostname or service of the message server unknown#DEST = SA
    What's wrong ?
    If i use T oss1 in parameter => technical setting => i set my saprouter info in SAProuter 1 ( at customer site ) with instance no. 99 and if SAProuter and SAPNet Message Server at SAP i put the following : Name : sapserv2 / IP Address 194.39.131.34 intance no. 99 and message server name oss001/ DB Name 001/ Instance no.01.
    When trying to "Logon to SAPNet"  i have an error Unable to connect to SAPNet message server ( default connection will be used ... ) 
    and followed by the error screen : "partner '80.15.173.168:sapdp99' not reached WSAECONNREFUSED : Connection refused. do you want to see the detailed error description ? "
    Details : module nixxi.cpp / line 3286 / Method : NipConnect2:80.15.173.168:3299 / Return code : -10 / System call : connect / Error No : 10061 / Error Text WSAECONNREFUSED: Connection refused / Counter : 10
    Any idea ?
    when doing niping.exe -c -H /H/mylocalSR/H/194.39.131.34/H/194/39.131.34 i obtain :
    Wed Dec 07 21:20:09 2011
    connect to server o.k
    Wed Dec 07 21:20:09 2011
    send and receive 10 messages (len 1000)
    times -
    avg   122.148 ms
    max   193.731 ms
    min   81.564 ms
    tr 15.990 kB/s
    excluding max and min :
    av2   118.273 ms
    tr2   16.514 kB/s
    Is it the expected output ?
    I've maintained system data in service.sap.com/system-data ( selecting the sap router ) then i tryed to use the SAP service connection, downloaded the .exe but i can't find the stfk.oez. I realized that in my maintain connection screen i have no space for entering any routestring. Seems wrong ?
    Do i have to use the SAO?
    i've made nat redirection from my router as this : from my public ip to my lan ip ( 192.168.x.x) what should i enter in the routestring : /H/public or lan or hostname ?/S/3299 ?
    Hoping you can help me ! ( the goal of all this is to set up RFC connection for postinst step of Solution manager ).
    Edited by: BLANCHARD Guillaume on Dec 7, 2011 10:47 PM

  • Remote connection from home PC to work iMac

    Our organization recently purchased an iMac 27-inch for an employee. That user would like to be able to remote into the computer from home. Unfortunately, that user has a PC at home. We were able to establish a VPN connection on the home PC and recreate the user's desktop via TightVNC: http://www.tightvnc.com/
    We can see the desktop and access mail and files but the connection is way too slow to work effectively. Has anyone tried a different solution for PC to Mac remote connections? Thanks in advance.

    Never tried
    http://www.coderebel.com/products/irapp

  • No Internet access after cisco vpn client connection

    Hi Experts,
    Kindly check below config.the problem is  vpn is connected but no internet access
    on computer after connecting vpn
    ASA Version 8.0(2)
    hostname ciscoasa
    enable password 8Ry2YjIyt7RRXU24 encrypted
    names
    interface Ethernet0/0
     nameif outside
     security-level 0
     ip address 192.168.10.10 255.255.255.0
    interface Ethernet0/1
     nameif inside
     security-level 100
     ip address 192.168.14.12 255.255.255.0
    interface Ethernet0/2
     shutdown
     no nameif
     no security-level
     no ip address
    interface Ethernet0/3
     shutdown
     no nameif
     no security-level
     no ip address
    interface Management0/0
     shutdown
     no nameif
     no security-level
     no ip address
    passwd 2KFQnbNIdI.2KYOU encrypted
    ftp mode passive
    access-list dubai_splitTunnelAcl standard permit 192.168.14.0 255.255.255.0
    access-list INSIDE_nat0_outbound extended permit ip any 192.168.14.240 255.255.2
    55.240
    pager lines 24
    mtu inside 1500
    mtu outside 1500
    ip local pool testpool 192.168.14.240-192.168.14.250
    no failover
    icmp unreachable rate-limit 1 burst-size 1
    no asdm history enable
    arp timeout 14400
    global (outside) 1 interface
    nat (inside) 0 access-list INSIDE_nat0_outbound
    nat (inside) 1 0.0.0.0 0.0.0.0
    route outside 0.0.0.0 0.0.0.0 192.168.10.12 1
    timeout xlate 3:00:00
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
    timeout uauth 0:05:00 absolute
    dynamic-access-policy-record DfltAccessPolicy
    http server enable
    http 192.168.14.0 255.255.255.0 inside
    no snmp-server location
    no snmp-server contact
    snmp-server enable traps snmp authentication linkup linkdown coldstart
    crypto ipsec transform-set setFirstSet esp-3des esp-md5-hmac
    crypto dynamic-map dyn1 1 set transform-set setFirstSet
    crypto dynamic-map dyn1 1 set reverse-route
    crypto map mymap 1 ipsec-isakmp dynamic dyn1
    crypto map mymap interface outside
    crypto isakmp enable outside
    crypto isakmp policy 1
     authentication pre-share
     encryption 3des
     hash sha
     group 2
     lifetime 43200
    crypto isakmp policy 65535
     authentication pre-share
     encryption 3des
     hash sha
     group 2
     lifetime 86400
    telnet timeout 5
    ssh timeout 5
    console timeout 0
    threat-detection basic-threat
    threat-detection statistics access-list
    class-map inspection_default
     match default-inspection-traffic
    policy-map type inspect dns preset_dns_map
     parameters
      message-length maximum 512
    policy-map global_policy
     class inspection_default
      inspect dns preset_dns_map
      inspect ftp
      inspect h323 h225
      inspect h323 ras
      inspect netbios
      inspect rsh
      inspect rtsp
      inspect skinny
      inspect esmtp
      inspect sqlnet
      inspect sunrpc
      inspect tftp
      inspect sip
      inspect xdmcp
    service-policy global_policy global
    username testuser password IqY6lTColo8VIF24 encrypted
    username khans password X5bLOVudYKsK1JS/ encrypted privilege 15
    tunnel-group mphone type remote-access
    tunnel-group mphone general-attributes
     address-pool testpool
    tunnel-group mphone ipsec-attributes
     pre-shared-key *
    prompt hostname context
    Cryptochecksum:059363cdf78583da4e3324e8dfcefbf0
    : end
    ciscoasa#

    Hi Harish,
    Please check the o/ps below and route print in attached file
    Latest ASA Config
    ASA Version 8.0(2)
    hostname ciscoasa
    enable password 8Ry2YjIyt7RRXU24 encrypted
    names
    interface Ethernet0/0
     nameif outside
     security-level 0
     ip address 192.168.10.10 255.255.255.0
    interface Ethernet0/1
     nameif inside
     security-level 100
     ip address 192.168.14.12 255.255.255.0
    interface Ethernet0/2
     shutdown
     no nameif
     no security-level
     no ip address
    interface Ethernet0/3
     shutdown
     no nameif
     no security-level
     no ip address
    interface Management0/0
     shutdown
     no nameif
     no security-level
     no ip address
    passwd 2KFQnbNIdI.2KYOU encrypted
    ftp mode passive
    access-list dubai_splitTunnelAcl standard permit 192.168.14.0 255.255.255.0
    access-list INSIDE_nat0_outbound extended permit ip any 192.168.14.0 255.255.255
    .0
    pager lines 24
    mtu outside 1500
    mtu inside 1500
    ip local pool testpool 192.168.15.240-192.168.15.250
    no failover
    icmp unreachable rate-limit 1 burst-size 1
    no asdm history enable
    arp timeout 14400
    global (outside) 1 interface
    nat (inside) 1 0.0.0.0 0.0.0.0
    route outside 0.0.0.0 0.0.0.0 192.168.10.12 1
    timeout xlate 3:00:00
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
    timeout uauth 0:05:00 absolute
    dynamic-access-policy-record DfltAccessPolicy
    http server enable
    http 192.168.14.0 255.255.255.0 inside
    no snmp-server location
    no snmp-server contact
    snmp-server enable traps snmp authentication linkup linkdown coldstart
    crypto ipsec transform-set setFirstSet esp-3des esp-md5-hmac
    crypto dynamic-map dyn1 1 set transform-set setFirstSet
    crypto dynamic-map dyn1 1 set reverse-route
    crypto map mymap 1 ipsec-isakmp dynamic dyn1
    crypto map mymap interface outside
    crypto isakmp enable outside
    crypto isakmp policy 1
     authentication pre-share
     encryption 3des
     hash sha
     group 2
     lifetime 43200
    crypto isakmp policy 65535
     authentication pre-share
     encryption 3des
     hash sha
     group 2
     lifetime 86400
    no crypto isakmp nat-traversal
    telnet timeout 5
    ssh timeout 5
    console timeout 0
    threat-detection basic-threat
    threat-detection statistics access-list
    class-map inspection_default
     match default-inspection-traffic
    policy-map type inspect dns preset_dns_map
     parameters
      message-length maximum 512
    policy-map global_policy
     class inspection_default
      inspect dns preset_dns_map
      inspect ftp
      inspect h323 h225
      inspect h323 ras
      inspect netbios
      inspect rsh
      inspect rtsp
      inspect skinny
      inspect esmtp
      inspect sqlnet
      inspect sunrpc
      inspect tftp
      inspect sip
      inspect xdmcp
    service-policy global_policy global
    group-policy mphone internal
    group-policy mphone attributes
     split-tunnel-policy tunnelspecified
     split-tunnel-network-list value dubai_splitTunnelAcl
    username testuser password IqY6lTColo8VIF24 encrypted privilege 15
    username testuser attributes
     vpn-group-policy mphone
    username khans password X5bLOVudYKsK1JS/ encrypted privilege 15
    username khans attributes
     vpn-group-policy mphone
    tunnel-group mphone type remote-access
    tunnel-group mphone general-attributes
     address-pool testpool
    tunnel-group mphone ipsec-attributes
     pre-shared-key *
    prompt hostname context
    Cryptochecksum:12308d7ff6c6df3d71181248e8d38ba8
    : end
    ciscoasa#
    Route Print after vpn connection 
    C:\>route print
    ===========================================================================
    Interface List
    0x1 ........................... MS TCP Loopback interface
    0x40003 ...00 24 01 a2 e6 f1 ...... D-Link DFE-520TX PCI Fast Ethernet Adapter -
     Packet Scheduler Miniport
    0x250004 ...00 05 9a 3c 78 00 ...... Cisco Systems VPN Adapter - Packet Schedule
    r Miniport
    ===========================================================================
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0     192.168.10.1  192.168.10.211       20
            127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
         192.168.10.0    255.255.255.0   192.168.10.211  192.168.10.211       20
       192.168.10.211  255.255.255.255        127.0.0.1       127.0.0.1       20
       192.168.10.255  255.255.255.255   192.168.10.211  192.168.10.211       20
         192.168.14.0    255.255.255.0     192.168.15.1  192.168.15.240       1
         192.168.15.0    255.255.255.0   192.168.15.240  192.168.15.240       20
       192.168.15.240  255.255.255.255        127.0.0.1       127.0.0.1       20
       192.168.15.255  255.255.255.255   192.168.15.240  192.168.15.240       20
        213.42.233.97  255.255.255.255     192.168.10.1  192.168.10.211       1
            224.0.0.0        240.0.0.0   192.168.10.211  192.168.10.211       20
            224.0.0.0        240.0.0.0   192.168.15.240  192.168.15.240       20
      255.255.255.255  255.255.255.255   192.168.10.211  192.168.10.211       1
      255.255.255.255  255.255.255.255   192.168.15.240  192.168.15.240       1
    Default Gateway:      192.168.10.1
    ===========================================================================
    Persistent Routes:
      None
    C:\>
    C:\>ipconfig /all
    Windows IP Configuration
            Host Name . . . . . . . . . . . . : asu
            Primary Dns Suffix  . . . . . . . :
            Node Type . . . . . . . . . . . . : Unknown
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No
    Ethernet adapter Local Area Connection 7:
            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : D-Link DFE-520TX PCI Fast Ethernet A
    dapter
            Physical Address. . . . . . . . . : 00-24-01-A2-E6-F1
            Dhcp Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 192.168.10.211
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.10.1
            DNS Servers . . . . . . . . . . . : 213.42.20.20
                                                195.229.241.222
    Ethernet adapter Local Area Connection 8:
            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Cisco Systems VPN Adapter
            Physical Address. . . . . . . . . : 00-05-9A-3C-78-00
            Dhcp Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 192.168.15.240
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . :

Maybe you are looking for

  • I have home sharing activated, but it is not showing up on my iTunes sidebar.

    I have recently bought an ipod touch 4th gen. I had my iTunes on one computer, then turned on home sharing, and it was fine. I was transfering my library and a moie was copying. I decided to brows the book store and purchased a book. When the book fi

  • Where are my apps in iTunes?

    This week, I upgraded to a 3GS, then downgraded to a 3G again when my purchase revealed that the problem with the 3G was a trivial software setting issue, not a hardware problem. THe 3G is running fine, and I'm happy to have it back again. However. I

  • 4 State Buttons - Disabled and Visited State

    Hi everyone, Does anyone know if CP will be offering 4 state buttons as an option in the future. Essentially adding a _disabled or _visited (both would be great) option to image buttons. 3 state buttons are great, but im finding more and more clients

  • Map Header field on Item field

    hello everibody. I have a very simple problem but i'm not is possible solve with standard graphycal mapping. I need map a field on header structure in all relative field on item structure: example: inbound message: <header> <field1>a</field1>    <row

  • Movement type 313 and 315 with special stock K.

    Hi, I would like to post a movement type 313 and 315 with special stock k (consignment) but it is not possible. Also i have tried to create a new movement type (OMJJ) coping 313 and trying to set stock special k in somewhere but I couldn't. it is pos