Remote connection using SAProuter and Service Connector

Hello everyone!
What I am trying to do is to connect to an SAP system of a client of ours.
This is what I have found out and what works -
I found out that for such a scenario a SAProuter and the Service Connector somewhow come into play. I worked with the SAProuter and could connect to a test IDES system in our company with the following router string -
/H/<localsystem_where_SAProuter_is_running>/H/<IP_of_IDES>/S/3200
This basically means that I would have to connect my SAProuter with the client's SAProuter and the client router would then pass on my connection to their SAP system like this -
/H/<mySAProuter>/H/<clientSAProuter>/S/<port_client_SAProuter>/W/<client_password_if_specified>
When this connection is established, I can access the client's SAP system through a SAPGui (Windows or Java) from my side using the connection string as specified above.
If this works, why do I need a service connector? What would it's function be?
Another question being - I have been told that a connection can also be established by using a connection from us to SAP and then from SAP to the client's SAP system (this has been suggested by the client). Where does this scenario fit in? If it is indeed possible, what do I need to do to make such a connection work?
I would appreciate it if someone answers who has actually worked on such a situation.
Bye!
Sameer

The service connector is used by SAP to automatically open your systems for customer messages; it's not relevant in the scenario you describe.
You can't use SAP's servers as a "stepping stone" to get to another customer's system.... you can directly link the two organizations by allowing the connections through both firewalls to specific saprouters at each end though:
CustA <> saprouter <> firewall <>  INTERNET <> firewall <> saprouter <> CustB
It requires coordination between both customers and the use of saprouter strings in the SAPGUI configuration, as you've described.
Rich

Similar Messages

  • Can't connect to BI Analysis Services Connector

    Hi all,
    I had tried to connect with BI Analysis Services Connector. I had done all steps, but when I tried to connect with BI Analysis Services Connector, can't view cubes and appear a error message. This don't have specifications.
    Technical details:
    Activity Id: 3629f200-123e-e7b5-7a6b-6676f47608ef
    Request Id: fdfa02e2-4500-3c74-47c5-573a5a97bb9b
    Date: 2015-03-27 20:44:01Z (UTC)
    I don't undertand what is the error.
    Please Help me
    Thanks!

    Thanks for your reply.
    The error I got in the OC4J window is : WARNING java.net.ConnectException: Connection refused: connect
    However, I have now been able to login to BI Publisher as Administrator. What I did was uninstall the full OBIEE (Basic) installation, and instead installed the BI Publisher component only, (along with OC4J).
    Works fine now, although I don't know why it didn't work with the full install. Any ideas?
    Cheers,
    Stephen

  • "Unable to Connect" using Firefox and Windows 7. Have tried all the suggestions on this website to no avail. I need firefox for my work! Please help!

    "Unable to Connect" using Firefox and Windows 7. Have tried all the suggestions on this website to no avail. I need firefox for my work! Please help!
    == This happened ==
    Every time Firefox opened
    == Since I downloaded Firefox

    same here my AV is ESET, i already unblock it but no use can't connect to the internet..

  • 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

  • Porting varray data from one db to another remote db using queues and jms

    We are trying to port a varray from one db to another db using queues and java jms. The varray is embedded in an object type (necessary according to oracle docs). The varray, embed object, and the queues are identical between the 2 dbs. We have used the capabilities in jdeveloper to generate the necessary classes to access the embed object and its payload the varray.
    However, when we attempt this:
    public void publish( com.wgint.sql.EaiType payload )
    throws JMSException, SQLException
    Connection dbConnection = ((AQjmsSession)session).getDBConnection();
    AdtMessage message = ((AQjmsSession)session).createAdtMessage();
    message.setAdtPayload( payload );
    ( (AQjmsTopicPublisher) publisher ).publish( publisher.getTopic(),
    message,
    agents );
    we get a ora-00902 error, invalid datatype. I cannot find a single example on technet or the internet in which someone has done something similar. I do not know if it is feasible or not.
    Steve

    Do you really need JMS to do this? If not, just let the AQ layer propagate your messages from your local to your remote queue. See the online doc how to do this.

  • MS SQL 2005 remote connection using sqljdbc

    Hi,
    I have production line computer with software using java code and firebird database, i also have sqljdbc.jar also in the library.
    my software is trying to connect to mssql2005 database in a remote computer and got this error message:
    java.lang.classnotfoundexception: com.microsoft.sqlserver.jdbc.SQLServerDriver.
    I have no problem when connecting to my local mssql2005 database though. but have problems when trying to make remote connection.
    May i know what could seem to be the cause of the problem, is there anything missing ? do i need to instal anything else on the production line computer? currently it does not have mssql2005 instal on the production computer do i need to instal it ? please help. thanks

    Btreksun wrote:
    Hi,
    Im using MS SQL 2005 Express edition, I dont find any sqljdbc.jar driver inside the installation,
    I dont see any other driver or driver folder in the installation path.
    Inside my instalation path C:\Program Files\Microsoft SQL Server: only shows these folders
    MSSQL$MSSQL2000
    MSSQL.1
    80
    90
    100
    "Class path" applies to java. None of the above is java.
    I dont know what to set my classpath with?You are running your java in "something". That "something" is an application. That "something" does not have the correct class path. You didn't tell us what it is so we can't help you with it.
    I even download sqljdbc.jar and put it inside C:\Program Files\Microsoft SQL Server and set the classpath but doesnt work ?I suggest you google for class path, read several articles about it and try some of the stuff that they talk about.

  • Need a Secure Reliable connection Using IDSL and dsl routers

    I need to get a fast secure remote connection to my database. I am using oracle 8i database and the 6i developer for my applications. I need to connect to from remote sites to my office using my internet dsl router.
    I managed to do this using the web remote desktop , but i need to use a differnt method for tow reasons :
    1- I am worried that i might face performance problems when having many remote desk top connections.
    2- I still need security measures where i want to restrict connections to only specific computers that i have identified by reading hard disks serial numbers etc.
    I will appreciate it if any one can help me and show me a suitable way to connect to the data base remotely using the idsl lines while the application (forms and reports runs in the clients computer) or any other methods to connect using the idsl and the routers and not compromise the security issues of restricting the connections based on hardware information.

    Hi,
    it seems to be a JRE Problem. When I use the Kerberos implementation from "Vintela Single Sign-On for Java" I can establish a "aes256" secured LDAP connection to the AD Server.
    This LDAP connection allows to change the passwords of the users stored in the AD.
    The problem is that "Vintela Single Sign-On for Java" is not free, so it would be nice to have a solution which works with the Kerberos implementation of the JRE.
    The error is the same for "aes128" and "aes256" encryption.
    And with Wireshark I can not see any differences in the packets send to the AD and received from the AD.

  • Client remote Authentication using JAAS and EJB Access

    Hi,
    I have a problem using JAAS in combination with Sun One Appserver 8.1 and a java remote client trying to access an EJB. Here is the scenario:
    I have implemented an EJB who's methods are protected through the deployment descriptor:
            <assembly-descriptor>
                 <security-role>
                    <description>role for clients outside of the server </description>
                    <role-name>sedna</role-name>
                  </security-role>
                <method-permission>
                  <role-name>sedna</role-name>
                  <method>
                    <ejb-name>ServerInfoBean</ejb-name>
                    <method-intf>Remote</method-intf>
                    <method-name>*</method-name>
                  </method>
                </method-permission>
                <method-permission>
                  <unchecked/>
                  <method>
                    <ejb-name>ServerInfoBean</ejb-name>
                    <method-name>getVersion</method-name>
                  </method>
                  <method>
                    <ejb-name>ServerInfoBean</ejb-name>
                    <method-name>create</method-name>
                  </method>
                </method-permission>
            </assembly-descriptor>I've deployed the EJB in a jar file which was packed into an ear file of a bigger application. The role has been mapped to the admin Principal in the sun-ejb-jar.xml descriptor.
    I can find the EJB, create it, and call the unchecked method getVersion and that works fine, so far so good.
    But then I try to access another method which is protected and then I get this exception
    org.omg.CORBA.NO_PERMISSION:   vmcid: 0x2000  minor code: 1806 completed: Maybe
            at com.sun.enterprise.iiop.POAProtocolMgr.mapException(POAProtocolMgr.java:179)
            at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:853)
            at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:137)
    ...I have to mention that I do make a login via the LoginContext. My jaas.config File has a reference to the com.sun.enterprise.security.auth.login.ClientPasswordLoginModule module.
    After login (which works perfectly) I lookup the context with a corbaname url which - if I understood it right - ignores the Context.SECURITY_PRINCIPAL and Context.SECURITY_CREDENTIALS settings.
    After that I make the calls to the EJB. And I am allways ANONYMOUS on the server side, which is definitely the problem. Because ANONYMOUS is not allowed to call the protected EJB Methods. But I made a jaas login in advance. So where am I making a mistake???
    Am I doing something wrong?
    Need help! Thx,
    Stephan

    Hi.
    I understand correctly that you call Subject.doAs on
    the client to call the remote EJB. I guess It isn't
    right way.I had also a bad feeling about this, so I forget it. But anyway it wasn't working with or without using that doAs().
    >
    >
    Subject contextSubject =
    Subject.getSubject(AccessController.getContext());
    contextSubject.getPrincipals();This code throws exceptions in the Appserver. Unfortunately they are catched somewhere so I'm unable to find out what was going wrong. But I guess, that these exceptions where security exceptions. Never the less thanks for the hint!
    But I don't think that doing the check on the server side is the way I want to go because that is programmatically security and I want to use the declarative security which can be used through the deployment descriptor. If used correctly - and supposed I do not completely misunderstand the specification - then it should be possible to create an EJB that is protected via it's deployment descriptor and access it through the client only if the client has been authenticated through JAAS mechanisms. After successful authentication the principal should be accessible through the EJB context but not for security check, that should allready been done at this time.
    Unfortunately I don't find any resource on the internet describing the scenario in such a detail that I can reproduce it. There are only very high level documentations and hints in forums.
    Again, thanks for your effort,
    Stephan

  • Connect using WLST and userConfigFile

    Hi
    I am using WLST to connect to admin server and do deployments etc. I have a jython script which has the following line to connect (as given in bea docs) :
    <p>
    <b>connect(userConfigFile=cFile,userKeyFile=kFile,aURL)</b>
    </p>
    I invoke the script as :
    <p>
    <b>java weblogic.WLST myscript.py</b>
    </p>
    I get the following error:
    <p><b>
    Traceback (innermost last):
    (no code object) at line 0
    File /buildscripts/webapp/myscript.py", line 33
    SyntaxError: non-keyword argument following keyword
    </b></p>
    Here Line 33 is the connect line.
    Am I doing something wrong. What is the right way to connect using a userConfigFile and userKeyFile thru WLST
    Thanks
    Nitin

    Sudarsan Mukundhan <> wrote:
    Hi,
    I am using the following command
    connect(userConfigFile='D:/Command_Line_Scripts/userConfigFile.secure',userKeyFile='D:/Command_Line_Scripts/userKeyFile.secure',url='t3://beaweblogic07:8501')
    >
    but it throws the exception
    Connecting to weblogic server instance running at t3:\beaweblogic07:8501
    as userna me weblogicadmin ...
    Traceback (innermost last):
    File "<input>", line 1, in ?
    File "<iostream>", line 74, in connect
    WLSTException: 'Error occured while performing connect : Error getting the
    initial
    context. There is no server running at t3:\\beaweblogic07:8501. Use
    dumpStack() t
    o view the error stack trace'
    Any idea what is wrong here
    Thanks
    Sudarsan MukundhanHi,
    Your server is just not reachable?
    B
    Schelstraete Bart
    [email protected]
    http://www.schelstraete.org
    http://www.linkedin.com/in/bschelst

  • Losing connection using facetime and wifi drops off. Why?

    Try connecting on facetime and when i try it says connection lost and my wifi goes off for a few seconds then comes back on. I tryed turn facetime on and off and it works once. then i try it again and connection is lost and wifi does the same thing.

    Yes, I went to settings and turned wifi off.  Thought at first I wasnt letting it set for a sec or two before shutting the iPad off.  so now I wait like a minute or two  before shutting the iPad down.  didnt  seem to help.  Tried  actually logging out of  facebook when I was  done with it,  worked for about  4 days, and now it has started  coming on and coming online again,,  I  went through my notifications and  shut things off,   Well  see if it works.  thank you.

  • Simple remote connection using Cisco AnyConnect and ISR router

    Hi all,
    I am just wondering what the easiest and simplest method would be to make remote PCs (running Cisco AnyConnect) establish a VPN IPsec to a Cisco ISR (881/887, 1900s,2900s series). I used to use EasyVPN method (simple and fast to configure and no need for special licences other than crypto licence) but since Cisco VPN Client is no longer supported I had to resort to WebVPN which requires a licence depending on the number of clients to support (SSL licences for 10,20 users and so forth). I've read a bit about FlexVPN but I can't find an easy example to what I want to do. The closest is this one (FlexVPN and Anyconnect IKEv2 Client Configuration Example):
    http://www.cisco.com/c/en/us/support/docs/security/flexvpn/115941-flexvpn-ikev2-config-00.html
    But that example makes use of RADIUS. Is there a way to make use of local database (users configured on the router) instead of RADIUS?
    Basically what I am after is the following
    - Remote users install Cisco AnyConnect to establish a VPN connection to HQ
    - HQ ISR (880s, 1900s, 2900s) terminates that VPN connections and allows access to local resources (shared drives, applications...).Authentication method would be local database on the router. No need of RADIUS/ACS as this is for very small companies with no IT resources to maintain and configure a RADIUS/ACS server.
    I think what I need is this AnyConnect to IOS Headend Over IPsec with IKEv2 and Certificates Configuration Example:
    http://www.cisco.com/c/en/us/support/docs/security/flexvpn/115014-flexvpn-guide-cert-00.html
    But the example is too highlevel for me to follow, basically I don't know how to generate such certificates and distribute it to remote clients.
    Any help as to how to create such certificates or how to configure FlexVPN to just requiring the user to enter usr/pass (using local database not RADIUS nor ACS) would be highly appreciated.
    Cheers
    Alvaro

    If you insist .. try this:
    http://www.cisco.com/c/en/us/support/docs/security/flexvpn/116032-flexvpn-aaa-config-example-00.html
    http://www.cisco.com/c/en/us/support/docs/security/flexvpn/115907-config-flexvpn-wcca-00.html
    http://www.cisco.com/c/en/us/support/docs/security-vpn/ipsec-negotiation-ike-protocols/50282-ios-ca-ios.html

  • Connecting to Remote Desktop using proxy and Remote Desktop Gateway?

    I have setup a Remote Desktop Gateway server using Windows Server 2012 R2. I am using the Remote Desktop Gateway as an intermediary between to provide the remote desktop session over 443 since 3389 is blocked at many client locations.
    However, I ran into a problem with a client who's using a web proxy.
    Is is possible to configure Remote Desktop to connect via web proxy? If so, how? If not does any one have any suggestions on how to provide a Remote Desktop session via 443 over proxy for situations where you don't control the client's PC or network? Does RemoteApps
    allow for access via web proxy when using RD Gateway?
    The error message is below:
    Your computer can't connect to the remote computer because the web proxy server requires authentication. To allow unauthenticated traffic to an RD Gateway server through your web proxy server, contact your network administrator.
    Thanks for any help!

    Hi,
    My suggestion is to setup a RD Web Access server and make it available for your clients via proxy.
    Remote Desktop Web Access (RD Web Access)
    http://technet.microsoft.com/en-us/library/cc731923.aspx
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • How to connect to remote computer using ARD and AE

    Does anyone have detailed instructions on how I can us my AirPort Extreme and setup all the ports to allow the use of ARD remotely?

    You can configure your AirPort Extreme for ARD using the AirPort Utility. ARD is one of the choices under Port Mapping.
    You get to the port mapping option, as follows:
    Run the AirPort Utility.
    Select the AirPort Extreme, and then, select Edit.
    Select the Network tab to enable it.
    Click on the "+" button under the Port Settings field.
    Click on the drop-down arrow to the right of the Description field. (see image below)
    Select Apple Remote Desktop. This will automatically populate the other fields on the page.
    Select Save, and then, select Update.
    Allow the base station to reset.

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

  • Remote Connection using Back to my Mac for Time Capsule?

    How do I connect to my Time Capsule and connected usb drive/printer now that Back to my Mac for Mobile Me is disabled and iCloud is running Back to my Mac?
    More information:
    I used to use the Mobile Me's version of Back to my Mac to enable connecting with my time Capsule, but how is this done now that iCloud has taken over Back to my Mac and I have upgraded to Lion.
    I have a Feb2011 MBP and a 2010 minimac the macmini is always connected to the time capsule, but I would like to be able to connect directly to the time capsule without having to go through the macmini.
    Thank you for your help

    It is possible but I am not sure it is worth the hassle..
    Your key issue here is public IP for your network.. if you have a static ip you are fine.. but very few people have this. It also depends on how the TC is setup.. is it the main router for the network or plugged into a modem router which has the role of main router, even if you use the TC as a secondary router.
    Without more info..
    1. This is easy if you have a static public IP and the TC is the main router and gets the public IP on the wan port.. just go to disk sharing in the airport utility manual setup and check for wan (internet access).
    2. If you have a dynamic IP, then you will have to sort out how you are going to find that IP.. the normal method to use dyndns account is not directly applicable because the TC has no client. It is possible to set up dyn dns but you will need to purchase your own domain name.
    3. You may find it easier to use standard router and bridge the TC. A standard router can be setup to port forward 548 AFP files service to the TC ip address. You may or maynot be able to access the printer. Certainly would be easier if the printer has IPP services. And is a true network printer.
    4. Use vpn.. get a vpn router so you can setup proper vpn endpoints.. then you use VPN service to access your local network.. this is far more secure and will work with dyndns just fine.

Maybe you are looking for

  • My itunes crashes and I can't open it all. HELP

    My itunes crashes and I can't open it all. Just installed the latest version 10.5.1. I can't even get it to open to try and figure out what is wrong. Can I uninstall it and reinstall the less recent version which was working? Help!! I am not a comput

  • Displaying messages in procedure

    I have a procedure which displays the total count of students from college. CREATE OR REPLACE FUNCTION count_stu RETURN number AS temp NUMBER(4); BEGIN SELECT count (distinct ID) INTO temp FROM registration; RETURN temp; END; If i want to display a m

  • Service type documents

    Dear All When i copy the service type of GRPO to AP Invoice i am changing the GL code but system automatically delete the base document link. How to stop this?

  • I have installed nvidia 1.0-9742 beta with the "run&quo

    and pcman tried to downgrade: Targets: readline-5.2-1 bash-3.2-1 nvidia-utils-1.0.9629-2 beryl-core-svn-1133-1 beryl-manager-svn-1136-1 beryl-plugins-svn-1130-1 beryl-settings-svn-1135-1 cairo-1.2.6-1 ed-0.3-1 inputproto-1.4-1 kbproto-1.0.3-1 kdebase

  • Blue vertical line

    i am responding to an email that was sent to me. they asked if i clicked on the line to see what it did. nothing happen when i did that . what is the next step to get rid of the line. i have restarted my imac, and it is still there. i also unplugged