BPF Package Manager won't open in remote connection using Public IP address

I have a problem to open BPF package manager.
Im able to open bpf package manager in my server and to all local bpc users but on the remote connection (vpn/web) they couldn't open the bpf.
Our server uses an private Ip address which is 10.1.25.81 (local LAN) but we also access BPC remotely using an
Public IP address (202.129.238.46 or http://servername.example.com/osft ) using a configuration of IP Forwarding in our router.
example:
(LAN)
User 1 on System 1 - does the BPF work?yes
User 1 on System 2 - does the BPF work?yes
User 2 on System 1 - does the BPF work?yes
User 2 on System 2 - does the BPF work?yes
(WAN/VPN)
User 1 on System 1 - does the BPF work?no
User 1 on System 2 - does the BPF work?no
User 2 on System 1 - does the BPF work?no
User 2 on System 2 - does the BPF work?no

When you are performing installation of BPC or after if you are looking into Server Manager - Server Option you will see for application server, web server and reporting services server you have two fields where you can specify name for internal and nae Example for application server:
Application  Server name: FQDN (or IP)
External Application Name: FQDN (or IP)
Normally we recommedn to use FQDN (Fully qualified DNS name)
because if the DNS entry are set correct then you will be able to connect from internal and also from external without any problem.
The system will provide every time the correct IP.
In my opinion you used IP and the problem it is that internal the external IP is not recognized.
Please verify the configuration and provide more information about the landscape.
Only in this way we will be able to provide you the right sugestions to fix this issue.
Kind Regards
Sorin Radulescu

Similar Messages

  • 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]

  • Adobe Application Manager Won't Open and CC Desktop failed to install

    I am running Win 7 Ultimate. Adobe Application Manager Won't Open and CC Desktop failed to install on my computer after I signed up for Adobe CC tonight. I am currently using the CS5 suite (perpetual license) and do not want to uninstall any of the programs until I am successfully running the Adobe CC versions. The AAM gives me an error message saying that it failed to open when I select it, and the creative cloud installer fails to install. I have tried restarting my computer. Help? This is very frustrating. I am a student and use this software on a daily basis, and can't afford to not have these programs available when I need them.

    Link for Download & Install & Setup & Activation problems may help
    -Online Chat http://www.adobe.com/support/download-install/supportinfo/
    OR
    Some download & install troubleshooting links
    -Comodo Security kills download http://forums.adobe.com/thread/1460361?tstart=0
    -http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html
    -http://forums.adobe.com/community/download_install_setup
    -http://helpx.adobe.com/creative-cloud/kb/troubleshoot-cc-installation-download.html
    -http://helpx.adobe.com/x-productkb/global/errors-or-unexpected-behavior-websites.html
    -http://helpx.adobe.com/creative-cloud/kb/unknown-server-error-launching-cc.html
    -Server won't connect https://forums.adobe.com/thread/1233088

  • Hot sync manager won't open

    For some reason I downloaded Palm desktop 4.1.4 on my windows PC for my M130 and the hot sync manager won't open. My operating system is XP Home. I was wondering if the problem might be that the Palm desktop is too outdated to use on XP. I'm new in the Palm world so I really need some help. 
    Post relates to: Palm m130

    Are you running any kind of Fax software or modem software on this PC?
    I found out Windows Media Center has a function that monitors the phone line to your computer.  It will announce the caller ID of any call coming in, if set to do so.
    This was causing problems with some Fax software I wanted to run!  When I turned this setting off, the Com port became available.
    WyreNut
    Post relates to: Centro (AT&T)
    I am a Volunteer here, not employed by HP.
    You too can become an HP Expert! Details HERE!
    If my post has helped you, click the Kudos Thumbs up!
    If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

  • Blackberry desktop media manager won't open

    I have no problem syncing my contacts, calendar items etc, using the desktop; I can even transfer media files no problem directly onto my media card.  But when I try to use desktop manager media manager it won't open.  When I double click on it it thinks for a second then does nothing.  Does anyone have any suggestions?
    Thanks.

    have you had a previous version of DTM installed before?
    do you have an active start button for media manager?
    check add/remove programs and see if you have any other roxio, or ezcd creator software
    have you tried syncing just contacts, or just calendar?
    do you get any errors?
    what version of DTM do youhave installed?

  • Bootcamp manager won't open in Windows 8.1.

    I've installed bootcamp on my iMac but the trackpad touch-to-click or multi-gesture functionality doesn't work. The odd thing is that the functionality works for a few moments after I've logged in, but it doesn't work once the account is fully logged in
    I've tried to open the bootcamp manager, but it won't open. Clicking on it does absolutely nothing. I've tried to create a non-administration account (as I've heard that bootcamp manager opens up in that) but no joy.
    Can anyone suggest an approach that doesn't involve re-installing the whole OS again?

    You may want to re-post in the Boot Camp forum located at
    https://discussions.apple.com/community/windows_software/boot_camp

  • I can't install Pixel Bender because the Extensions Manager won't open.

    HI1  I can't install Pixel vender because the Extensions manger won't open.  I get the message that it has "unexpectedly quit" and then I'm supposed to send a report to Apple.  Of course, nothing comes of that.  Does anyone have any suggestions?  Thanks for your help.
    Best,
    Endre

    Dear Endre,
    Please back up all files in the folder /Library/InputManagers and remove those files, and then try to launch Extension Manager. It may solve the issue.
    You can also to try the following method:
    Remove all old Extension Manager preference and application support files.
    To delete the application support files for Extension Manager CS5, please navigate to folder '/Users/<current user>/Library/Application Support/Adobe/Extension Manager CS5', then back up all files in the folder, and then delete all files and sub directories in the folder.
    To delete the preference file for Extension Manager CS5, please navigate to folder '/Users/<current user>/Library/Preferences/Adobe/Extension Manager CS5', then back up all files in the folder, and then delete all files and sub directories in the folder.
    If neither above way works, please use the below method to gather crash log and I will check those crash log. Thanks.
    As you mentioned, when Extension Manager crashes, there would be a dialog to ask for sending report to Apple. In that dialog, you can view the crash log by clicking report button. Then you can copy the crash log and paste it into the forum.
    Best wishes,
    chengyon

  • Dreamweaver CS6 cloud - I can no longer use "Save As'  and the Application manager won't open.

    I always open an old page and use "save all"  to save it,  then "save as"  and change the name of the page to what I want the new page to be the rewrite the new content. It doesn't open a box for name change any longer. Also The application manager does not open at all.
    What to do to fix this?
    Roger

    Hi Roger,
    Can you close other applications open on your computer, and retry before the experts here suggest other solutions?
    Thanks,
    Preran

  • Adobe application manager won't open

    I just subscribed to Adobe Cloud CC , but my download won't work because Adobe application Manager won't launch.
    Any suggestions ?
    Vic

    The Adobe Application Manager is normally started from Photoshop menu Help>Updates.  Is this what you referring  to or are you referring to the Creative Cloud desktop application?

  • TS2972 I downloaded text me ap from the itunes store onto my computer but it won't open, how do I use it?

    Hello I just downloaded "text me" ap from the itunes store to my desktop computer, but it won't open!!  How do I use it?  I tried right clicking and double clicking but nothing happens... Please advise.
    Corinne

    If you have a rescue email address set up on your account then you can try going to https://appleid.apple.com/ and click 'Manage your Apple ID' on the right-hand side of that page and log into your account. Then click on 'Password and Security' on the left-hand side of that page and on the right-hand side you might see an option to send security question reset info to your rescue email address.
    If you don't have a rescue email address then go to Express Lane  and select 'iTunes' from the list of 'products' in the middle of the screen.
    Then select 'iTunes Store', and on the next screen select 'Account Management'
    Next choose 'iTunes Store Account Security' and fill in that you'd like your security questions/answers reset.
    You should get an email reply within, I think, about 24 to 48 hours (and check your Spam folder as well as your Inbox)

  • How do I stop VI Package Manager from crashing when I try to use it?

    So I've been wanting to play around with the Arduino toolkit, but when I installed the VI Package Manager, the splash screen stayed up for a very long time. I tried quitting in Task Manager, and running it again. This time after about 10 seconds, it gave me the standard Windows crash dialog. I tried running it as Administrator, but that didn't help. I also tried running it in XP compatibility mode, and that opened a popup saying it couldn't detect a LabVIEW installation, but it still wouldn't load (It didn't crash though; just stayed at the splash screen.) I'm running Windows 7 Ultimate, and LabVIEW 2011 Professional Development System.

    You really should ask this question on the VIPM board at JKI.
    http://forums.jki.net/forum/5-vi-package-manager-vipm/
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Intel VPRO managment engine - cant get "initiate remote connection"

    Hi Everyone
    When configuring the intel ME bios to enable KVM access on my new ThinkCentre M93P machines, i no longer get the option "Press 2 to initiate a remote connection" when i turn the machine on and hit CTRL+P
    What used to happen (and still works fine on ThinkPads) is that the first time you hit CTRL+P you go into the intel management engine setup screen.  Then once setup, the next time you hit CTRL+P , rather than go straight into the manegement engine BIOS you would get two options:
    Press 1 to enter ME configuration screens
    Press 2 to initiate a remote connection
    However on the Thinkcentres i cant get it to give me these two options, it always goes into the ME screens.   Anyone else succesfully using this feature?
    Thanks for any help

    Hi,
    iChat to iChat, Google ID to Google ID works.
    It invokes exactly the same A/V side of iChat.
    This does require that the ports are allowed (UPnP) or opened (Port Forwarding or Port triggering) in the connection device that you have.
    It requires that you do not have two device at one end doing DHCP (just bad Networking) and in some cases iChat needs to make sure the LAN is specifically set up on the NAT front.
    Tell us what device you have at both ends and what you have done to set them up for iChat please.
    Also is the other end actually an Error 8 like your is ?
    Is it Error 4 as this would tend to mean Internet Sharing was turned On and should be Off.
    Error 7s are about security features in one of the devices.
    1:08 PM Sunday; March 16, 2008

  • I downloaded and installed Firefox 4, but it won't open. I have used an older version of Firfox for a long time. I now have nothing. What gives?

    I've used an older version (3.?) of Firefox for a long time. I had loads of bookmarks. I downloaded the new Firefox 4. It won't open and the older version is now gone. I use a Mac with a 400 MHz PowerPC G4 with 1.12 GB SDRAM and a 60 GB Internal Hard Drive. I'm running Mac OS X Version 10.4.11. I really need to recover the older version of Firefox or make the new version work.

    Firefox 4 requires at least OS X 10.5 and an Intel Mac. There is a third party version of Firefox 4 that runs on OS X 10.4/10.5 and PPC Macs, for details see http://www.floodgap.com/software/tenfourfox
    If you prefer, you can get the latest version of Firefox 3.6 from http://www.mozilla.com/en-US/firefox/all-older.html

  • Elements 5 won't open, error message "attempt to access invalid address" any solutions please.

    I have been using this for years with other problems, however now it refuses to open. I have uninstalled and re-installed after restarting the computer twice. I also deleted every folder I could find with elements in the name to no avail. If I read a camera card elements get photos opens them into elements organiser but if I click the edit photos tab it refuses to open. I have windows vista 32 bit.

    Hi Garry,
    Yes, I did download PSE 8 and it did work.  However, the trial period has ended.  I have uninstalled PSE 8.  I have also unistalled PSE 5 and then reloaded it.  Upon completeion of the PSE 5 load, I tried to open the PSE 5 and the invalid address error message continues to display.  I am very sad that I cant get PSE 5 to work.  Can you help with more things I can try?  Please let me know
    All the best
    David

  • Application world won't open in PlayBook when using BIS

    App world on my PlayBook  won't load when I am using bridge with BIS.every other thing works though. Why is this so? Please someone help 
    Solved!
    Go to Solution.

    It varies by carrier so you need to call them. My carrier includes it

Maybe you are looking for

  • Video Files Import into an IMAC

    Can someone lend me their advice ... I am using a PC and creating a POWERPOINT show ... I have different tools to take this show to convert it into a video file (like MP4 etc). What Ia m trying to do - is to merge a video file and pictures - the pict

  • Develop Presets:  Move from "Stored With Catalog" to ?

    Early on with LR1, I checked...or didn't uncheck--the box that has LR store the Develop Presets with the Catalog. I have since read that storing them there may not be a good choice. Would there be any point to moving them?  Is there any practical way

  • Stackoverflow Error in connect component analysis

    Hi all, I'm writing a method for labelling connect component in a 320*240 image. But every time I tested it always got a stack overflow error :( The code is like this boolean[] checked=new boolean[320*240]; boolean[] ccomponet=new boolean[320*240]; p

  • Nokia Series 60 Theme Studio

    Hi @ll i got a problem with the nokia series 60 theme studio. it is very very very slow. Ok,, my pc is not the fastest, but i tried it on a faster machine without any changes in speed performance. can anybody tell me a trick or something to tweak the

  • Synchronizing Search and Edit pages in JDev11g

    Hi! How can I simply synchronize Search and Edit pages in JDeveloper 11g? In JDeveloper 10g I used <br>1) at Search side: SetActionListener with From:#{row.PkField} To:#{processScope.someVar}<br> 2) at Page Definition of Edit side: action setCurrentR