2 way TCP connection using IP addresses
Hi All,
I need to pass data in both directions between 2 pc's connected to the internet. I am aware of the various TCP/IP and data socket examples, I am using Labview 7.0. I dont know much about the ptotocol involved but figure I only need a few pieces of info.
If the server machine wants to connect to a client machine on the same network I understand no changes are required to the example vis (ie port 2055 used in Simple Data Server). But what would happen if the server PC wanted to connect to a client in a different country? Is that when IP addresses are needed?
I imagine my final vi front panel will have a "This machines IP Addr" and "Client's IP Addr" text box, operators of the machines then tell the other person their mac
hine IP address which is entered manually to setup a 2 way link.
Is it possible to get Labview to find the full IP address of the machine ready for the other user to type in. Thanks in advance
Regards Chris
On the client side the users will need to fill in the IP address or domain of the server. If that IP is on the Internet or somewhere else that will work as long as the client PC has physical access and permission to open a tcp connection (no firewalls that block the port you are using etc.)
Make a connect dialog that pops up if the user chooses to connect and have the user input the IP there and click OK. You can add functionality like bookmarks and "home page" to make things easier. If a home page / server is defined the client can connect to that upon startup. You may want also to add functionality that will reconnect in the background if the connection is lost.
The client's IP is of less interest. If you need it though just use the string to IP function
and the IP to string function from the tcp/ip palette. Do not wire anything to the former funtion but wire it's output to the latter. The latter will then output the IP of the local PC.
MTO
Similar Messages
-
Anyone else having an issue with TCP connections using iCloud for Windows?
Hi,
Before I asked this question, I did wait to see if any related questions came up, but none did, so I submit it now.
On my admittedly older laptop running Windows 7 64b Home, I've run into difficulties with the iCloud for Windows app to the extent that I had to uninstall it.
It would that, as my laptop was running, in the background, iCloudServices.exe would endlessly iterate TCP connections, which, while not actively sending or receiving any data, after some hours would number over 100 instances, taking up resources, and grinding my laptop's WiFi connection to a grindingly slow pace. I ended up, within the app, turning off everything, iCloud Drive and Photos, (I never used bookmarks), but still this would continue to occur.
I contacted Apple Support, explaining what was going on, and they stated they only dealt with IOS and gave me a Microsoft Support number. When I called Microsoft support, I came more and more to the realization that the issue was specifically with the iCloud for Windows app, as that was the only software that was endlessly creating and not closing TCP connections as it was. How was Microsoft supposed to solve an issue with Apple code?
So I called Apple back, whereupon they insisted it was a Microsoft issue. I explained other cloud services installed on the same computer were not having the same issue, it was unique to ICloudServices.exe. They stated they only dealt with IOS. I stated I purchased an iPad Air less than 7 months ago, and was trying to run iCloud in support of that. They again stated they only dealt with IOS, and suggested I again try Microsoft. I asked them if it was reasonable to expect Microsoft to solve issues with Apple code? They said regardless, there was zero support offered for anything having to do with Windows, and all I could do was uninstall the app, which I did, though that did not feel very satisfactory to me. My thinking is, if Apple writes a Windows app in support of their hardware, they should offer support for it.
Anyway, I was just wondering, is this an issue unique to me? or have others experienced a similar issue? I found this issue by opening the Windows Resource Monitor, looking under the Networking tab, and scrolling through the TCP Connections section to find 100+ concurrent iCloudServices.exe instances listed, whereas even Chrome, with multiple tabs and extensions, topped out at around 20.
My one month old Desktop, DYI, sports a solid Asus 1150 MoBo, i7-4790k cpu, 16GB Ram, and an EVGA GTX 970 video card. I list some specs only to illustrate this computer has no hardware issues in comparison to my long in tooth laptop. On this desktop, running Win 8.1 Pro 64b, at least as many, identifiably Apple, background service TCP connections are created even compared to Chrome, regardless of many tabs being open, many extensions, and even some related apps. Adobe does not even come close, though I run the full CC subscription. On this new computer, running Windows 8.1 Pro 64b, there are currently over 50 TCP connections and loopbacks that do not identify themselves, with just a - for the Image, and PID. With the experience on my laptop, I wonder how many of these are generated by Apple software, if not specifically iCloud software?
The frustrating aspect of these connections is they seem in no way active, While the Chrome and Adobe connections can be seen to be transferring data, as long as I am not running iTunes, or so have my iPad actually plugged in, it seems 99% of the time these iCloudServices.exe connections are just taking up ports, neither sending nor receiving any data discernable to me under the Processes with Network Activity, or Network Activity lists, both displayed in the same window as the TCP Connections in the Windows Resource Monitor.
Though I am fairly ignorant as regards coding, it seems as if there is no call to close a connection, very specifically, iCloudServices.exe, when it is no longer needed, and the next time a connection is needed, a new one is opened, rather than accessing the one previously opened. The only other reason I could imagine this might be occurring is if my Norton Internet Security software might mask and/or block the port after a certain time of inactivity.
Anyone out there have any ideas or advice about this? Thanks in advance.Thanks jared,
I'm still dealing with this issue through Apple. Some time after I posted this, I contacted Apple again. They did start a case up for me, as I was experiencing the same behavior on two different machines, with two different versions of Windows.
So far it remains unsolved. I've logged iClouds for Windows on my desktop, which is brand new, then logged for awhile after completely uninstalling Norton Security Suite, depending on the Microsoft security for some time, and finally logged after I uninstalled iCloud for Windows, restarted, installed a clean download, and connected using a completely different test account, which Apple set up for me. None of this made any difference. Looking at the logs, it seems every 10 minutes, iCloudServices.exe creates a new TCP connection to confirm I'm using less than 5GB on iCloud, (which I am by a good margin, using less than 2GB), it seems this connection is not closed, and when the next iteration rolls around 10 minutes later, a new TCP connection is created. I come very close to having 6 TCP connections created per hour, until I restart my computer. This works out to... 6 x 24 = 144/day.
Perhaps the article you posted will shed some further light on this. I'm thinking seeing the state of the connection through netstats, at the least, could help.
For the last week, I've been putting a hold on further logging, as Apple wants me to create a new user account on one of my computers, install iCloud for Windows there, and log it running in the other account. This however basically means I cannot use my computer for a fair number of hours, and I've been busy enough with work the past week that I haven't the time or energy to afford to set this up and run it. I've had need of my computers too much for the past week. -
Many TCP connections used after 9i install
I've installed 9i personel on XP Pro as a learning aid in advance of installing it to a real server. I notice (using "netstat") that there are now many TCP connections from my machine to localhost (also my machine) on ports from 2192 through 2267. All seem to be in a time_wait state. Are these normal and necessary?
Thanks!I've installed 9i personel on XP Pro as a learning aid in advance of installing it to a real server. I notice (using "netstat") that there are now many TCP connections from my machine to localhost (also my machine) on ports from 2192 through 2267. All seem to be in a time_wait state. Are these normal and necessary?
Thanks! -
hello,
I tried making a simple RMI application to check about the usage of TCP connections for the communication. The client and server are running on different hosts and my observations are:
a) when the client is invoking a method on the server at an interval of about 1 sec, then the same connection is used everytime for the communication.
b) when the client is invoking a method on the server at an interval of about 30 sec, then the a new TCP connection is made everytime for the communication !
The java.rmi.dgc.leaseValue is set to 100 minutes in both cases. Does this not mean that the connection should be maintained for 100 minutes even if there is no communication between the client and server ??thanks, I could not find any parameter in the standard properties list, however in the SUN specific properties we do have sun.rmi.transport.proxy.connectTimeout which should control the connection life. I use IBM's JRE, so I will try to find an equivalent property.
Another question ... what is the benefit of java.rmi.dgc.leaseValue if the TCP connection is closed itself ? Does the gc not happen if the TCP connection itself breaks ? Or does the RMI think about a logical connection which is independent of TCP connection's life ? -
E3000 - WVC210 Cam - Can't Connect Using IP Address
I've searched here and on portforward.com and have read all FAQ's for a solution to my problem with now luck. Prior to contacting Tech Support via telephone thought that I'd try a post here first.
I've had a Linksys WVC54GCA IP Camera running through my E3000 wireless router with zero issues for quite some time. I just added a Cisco WVC210 PTZ IP Cam. My setup went flawlessly and both cameras are operatng independently of one and other and I am able to view both cameras using my DYNDNS.com supplied Web Host URL's away from home and both camera's are working great on my iPhone 3GS.
I have assigned fixed IP addresses to both camera's. 192.168.1.200 for the the WVC54GCA and 192.168.1.201 for the WVC210. I have setup the Port Range Forward as follows:
Cam1 80 to 80 Both 192.168.200
Cam1 1024 to 1024 Both 192.168.1.200
Cam2 1025 to 1025 Both 192.168.1.201
Here's the thing I don't understand. Again, both cams do what they're supposed to, except; on my home network I can connect directly to the older WVC54GCA using its 192.168.1.200 fixed ip address. I CAN NOT connect directly to the new WVC210 using its fixed ip address of 192.168.1.201. I get an IE error.
I have a feeling that there's something I'm not doing on the router or it has something to do with being on port 1025. Any help would be greatly appreciated.I don't think there is any issue with the port 1025 for the second camera.
The port 1025 will be used to see the camera from outside.
If you are able to see both the cameras from out side that means both the cameras are configured properly and working fine.
What error message do you get when you try to see the camera using the IP address of the camera?
Try using another browser and check if you can see the camera in the network.
Try to ping the IP address of the camera. if you get replies from the camera IP address then your computer is able to communicate with the camera.
What is the operating system on your computer? -
Creating connection using NAT address
Can we use ServerSockets to create a connection to a server using the NAT address ? If yes, then does it require something different ?
Do you want to connect an external machine to a machine behind your NAT router? Or is this completely internal? If it's interal you should be able to use the machine's private ip address.
-
Coherence Extend remote address port in TCP Connection
Hi,
From the log below, I see remote address port is picked some random port(48552). (currently i disabled the firewall), If i enable the firewall it could be an issue, is there any way i can specify the remote ports that tcp connection use?
2011-02-24 13:18:18.076/1280.207 Oracle Coherence GE 3.6.0.1 <D6> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=13): Opened: TcpConnection(Id=0x0000012E56A3CA1B0A1F96B688F7EEBCEDA2AA9397203393CF480379B3963D86, Open=true, LocalAddress=10.31.150.182:9099, RemoteAddress=10.31.150.182:48552)
One more question,
I have two proxy servers, is it possible to configure the client to make two connection (redundant) one for first proxy and another for second proxy. is it make sense?
Thanks
Prab
Edited by: 833796 on Feb 24, 2011 2:35 AMHi Prab
The random port is what normally is called an ephemeral port for the client and is usually not a problem for firewalls since this is expected behavior. If you want to control the client port you can do this by adding the <local-address> to the tcp-initiator element.
As for the second question, it doesn't quite work to do as you suggest. The proxy contains state for the client, as this is not replicable between the proxies one cannot continue where the other one left off.
Thanks
/Charlie -
Is there a way to get a permanent address to an afp server?
I am connecting to my other mac in the local network, but I want to use Quicksilver to quickly connect to the server with a hotkey. I checked the afp address in the Sharing preference pane, and it seemed to work fine, but it didn't work the next day. When I checked the address, it had changed. Is there any way to connect using the same address every time?
The way I do that is reserve an IP address in my router.
Then, even though I leave the network setup Using DHCP, it still gets the same IP address all the time. -
Hello folks,
I have a VI that monitors a TCP connection using the function "Not a
Number/Path/Refnum". When the peer (the other side which this VI is
connected is a win program in Visual Basic) closes the connection, my
VI seems unable to detect the closed connection, it is "thinking" that
the TCP refnum is still valid.
How I can handle it?
Thanks!Monitor the error cluster instead of the refnum. th refnum is a local handle that has nothing to do with the actual link. It's just a pointer to the link object. The error cluster holds the information you want to monitor.
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl) -
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
NitinSudarsan 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 -
Is there a way to connect an old Sunflower iMac (OSX 10.4.11) to a new Time Capsule? It used to work with old Airport Extreme network, run from a intel iMac with updates thru Mavericks but now seems to only allow WEP encryption instead of WPA and can't connect to Time Capsule. Airport Extreme Base was controllable from either computer up through Snow Leopard (I didn't do any of the Lion upgrades). Then when I upgraded to Mavericks I lost the ability to use Airport Utility with this hardware on the Sunflower but could still connect wirelessly to network without any problems. But now with the Time Capsule upgrade the Sunflower is blocked from network by a dialogue that requests ony WEP password, not WPA pwd used by Time Capsule. Neither can I use the old airport extreme base to extend the time capsule network since I can't input the correct password/encryption approach to join it. Is there a work around? Would a newer but old Airport Express be able to extend network to Sunflower? Or maybe a third party wireless (such as Netgear, Dlink, etc) that has browser type control rather than special utility?
Another question--before I used MAC addresses to control who could access network. Now on Time Capsule I don't see anything about this--so is it true now that the only access control is via WPA2 pwd now (which appears to be the encryption pwd and not the time capsule pwd)?Is there a way to connect an old Sunflower iMac (OSX 10.4.11) to a new Time Capsule?
I can’t claim to completely grasp the issue(s) you’re describing, but the underlying problem is presumably your iMac’s obsolete AirPort card. Whatever the case, an obvious (if not particularly helpful) answer to your stated question would be to connect your iMac with an ethernet cable, using powerline adapters as an alternative if you don’t want to have wire running all over the place.
My still fully functional clamshell iBook, with an original AirPort card, connects wirelessly to my 4th Generation TC network by means of a cheap 802.11b/g/n USB Wi-Fi adapter. This might be an option for you too.
Another question--before I used MAC addresses to control who could access network. Now on Time Capsule I don't see anything about this
When you edit your TC's settings the access controls appear under the Network tab, don't they? -
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] -
Connect to external device using ip address in lan
Hi,
I have a external device in lan ,
,want to connect this external device using ip address.Dhaval.Yoganandi wrote:
hi ejb,
may be he wants to connect with the 172.16.0.20 via public network ?And ?
That has nothing to do with anything. Whether the resource is on the local network or accesible through the internet only is not relevent here at all. This forum is for Java network programming. If a resouce is not available because you are not connected physically to a network that is a network problem. That is not a Java progamming problem.
Okay?
There's alot of rubbish posted in this forum about "public networks" and what not and not one lick of it is related to Java programming. Yes if you connect through more routers to something there is a better chance that somewhere along the way that you will hit a firewall or other similar issue. But these are all network issues. Not networking programming issues. And not resolvable directly in Java any way you want to think about it. -
OSB using socket Transport ,how to keep a TCP connection open
hi my firends,
i met a problem , our project need build an OSB to control a socket service which is able to transfer a big data file (maybe a voice file,*.wav),and the client program will play the voice file on live.
So my solution is that : keep a socket (tcp) connection open,client listen port and makes date play.
but i can't make the OSB socket transport alway open,it will timeout after a few second if have none date received.
how could i deal with it ... pls let me konw if you have any idea...i will wait you on line
thanks guysHi,
I'm not sure if that's achievable using OSB, and even if it was, I don't think OSB was designed having this type of application in mind...
I understand that you need a media streaming solution and I'm pretty sure that there are plenty of tools out there that can help you in doing that, and maybe some of them can be integrated with OSB in some way...
Cheers,
Vlad -
I just bought a new iMac and now I amtrying to use it as a screen for my Macbook pro, but it don’t have a MiniDisplayPort the new model only have Thunderbolt which my Macbook don’t have. Isthere any way to connect this two mac’s anyway??
Screen sharing setup in 10.5, 10.6 are described by the links by operating system. 10.7 is fairly similar to 10.6.
And if both Macs have Firewire, you can setup a Firewire over IP network for fast communication between machines. Note if you have two different Firewire ports a 6 pin to 9 pin Firewire cable does exist. There are no Firewire to USB cables.
Maybe you are looking for
-
Just upgraded to Mavericks. Now I cannot access scans from my hp scanner. After it complete the scans and I try to save as tiff, jpeg or pdf I get a either a grey blur or a message that says cannot save because the file cannot be written to. I did no
-
Need help on search help on selection screen field
Hi guyz, Please tell me how to pass the parameter or restrict the below search help. *s_bsart FOR ekko-bsart . " Doc. Type* For the above selection screen field i need to display the data only for cat = F if i click search help. Thanks, Mohamed Kalee
-
Hello, I am trying to setup a "right click menu" on a table with menu items related to the cell (or at least to the row) where the right click was hit. For example two such menu items will be "Add new row after" and "Add new row before". For this rea
-
Is there anyway to 'hear' the audio from videos on 4th gen or less iPod
I would like to download some of the 'video podcasts' and only want to 'listen' to them. Is there any way to do this on a 20G iPhoto? I don't need or want the visuals. PC AMD Athlon XP 1600+ OEM Windows XP
-
How is the scarp portion of MO variance calculated?
How is the scarp portion of Manufacturing Order variance calculated?