How do I set up a PPTP VPN connection?
I've just arrived at uni to find that in my dorm I don't get wifi reception, and the lack of ethernet port in my MacBook Air means I can't just connect via the ethernet port in the wall. Luckily I brought my AirPort Express with me.
Now the uni internet operates by VPN over a PPTP connection, and given that they do state they're happy for students to connect whatever routers they like, I went right ahead. Trouble is, despite listing the fact that the AirPort Express supports PPTP, I'm not sure how to go about setting it up. A quick google revealed very little. The IT department was happy to provide the logon domain and server address, but I don't know where in the interface to put them, much less where to select PPTP.
I've been able to get an IP on the thing, but not one indicative of having logged in to the VPN.
Ideas? Thoughts?
Hello @mhernandez808,
Welcome to the HP Support Forums! I see you would like to connect your HP Officejet 4622 to your Wireless network. I would like you to click on the link below to get started:
Setting Up the Printer for a Wireless network for the HP Officejet 4622
Please follow all steps listed above to connect to your Home network. Once connected you will be walked through setting up the wireless printer on your Computer.
I hope this helps, if you have any questions please ask away!!
Thanks,
HevnLgh
I work on behalf of HP
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to the left of the reply button to say “Thanks” for helping!
Similar Messages
-
Hello, how could I setup or deploy several PPTP-VPN connections via AppleScript? (System Preferences-Network-Add Interface-VPN-PPTP)
Thanks in advance!I must confess that I don't know much about network connections. However, using [GUI Scripting|http://www.macosxautomation.com/applescript/uiscripting/index.html], the following script (tested on my MacBook Pro) should add one "VPN (PPTP)" connection to the Network pane of you System Preferences:
tell application "System Preferences"
reveal pane "Network"
activate
tell application "System Events"
tell process "System Preferences"
tell window 1
click button "Add Service"
tell sheet 1
click pop up button 1
click menu item "VPN" of menu 1 of pop up button 1
delay 1
click pop up button 2
click menu item "PPTP" of menu 1 of pop up button 2
click button "Create"
end tell
click button "Apply"
end tell
end tell
delay 1 -- optional (just for visual feedback)
keystroke "w" using {command down}
end tell
end tell
Before using this script, the Accessibility Frameworks must have been enabled by clicking the checkbox labeled "Enable access for assistive devices" in the Universal Access System Preference pane.
Message was edited by: Pierre L. -
How to Configure an Cisco 5505 for PPTP VPN connectivity
I currently have a Cisco ASA 5505(ASA Version 8.2(1), and ASDM gui version 6.2) and a Windows 2008 R2 server with one NIC card. Currently the router is connected to the interent sucessfully using the 'outside' interface(devices connected to the 'inside' interface have access to the internet and are assigned IP addresses via DHCP on the Windows 2008 Server which is also connected to the 'inside' interface) When connected with a client on the inside interface I can establish a VPN connection with the W2008 server, however when I try to connect through the internet I cannot. I have tried researching this on the internet, but have not had much luck. I know it has something to do with pptp port and allowing gre, but I am not familiar enough with configuring Cisco devices or the language they use, to configure this router. I feel as though I am missing something small but very critical. Any help or feedback you can provide regarding this issue is most appreicated, thank you.
*Edit: I have attached a network diagram of what I am trying to accomplish, and I have also attached a dump of the current running-config.Hi,
Below is the link to the admin guide for the RV042. Chapter 9 covers the configuration of site to site VPN’s and begins on page 123.
http://www.cisco.com/en/US/docs/routers/csbr/rv0xx/administration/guide/rv0xx_AG_78-19576.pdf
If you need further assistance please feel free to contact Cisco Small Business for help in configuring and troubleshooting your VPN.
Thank you,
Jason Nickle -
Internet stops with PPTP VPN connections to ASUS RT-N66U VPN Router
I have a client with a small office network that has a few people working remotely from Windows 7 and 8 PCs. As an inexpensive solution the client opted to use a VPN router (ASUS RT-N66U) that supports PPTP so remote users could access the shared
files and SQL DB server.
The VPN connectivity for one client was working fine and then stopped working altogether so when the VPN connection is established all Internet and VPN access is stopped. This was especially troubling for me since I work remotely and cannot test or debug after
the VPN session has been connected. I checked the error logs and found nothing. Also there had been no new programs installed. And finally, I ran a full system antivirus scan with no issues found.
In case you are facing a similar issue, before trying something remotely that may not work, use the shutdown with reboot command in a COMMAND window and set a timer for something like 3 minutes to reboot in case you get stuck. (e.g. shutdown -r -t 180).
Problem: The two symptoms of the VPN connection failure are:
1) All Internet browsing stops working locally
2) No data can pass through the VPN tunnel
I created a virtual machine on my local network and replicated the client's environment. I experimented with nearly every setting in the VPN dialogue until and came to the final solution.
Solution: For the VPN adapter on the remote machines I configured DNS settings and used the remote as the default gateway.
* VPN adapter Networking IPV4 Properties for:
- DNS server 1: Main Office VPN Router IP Address
- DNS server 2: A public DNS server (Google is 8.8.8.8)
- I also checked the box to "register this connection addresses in DNS"
Note: Perhaps the local router would also have worked and DNS2 but I didn't test it.
I have documented this because after reading and searching among many Technical articles and the Microsoft support website, I was unable to find the solution that I came up with so I hope to help someone else.
Question1: - Can anyone tell me why the connectivity only works when 'use default gateway on remote network' is checked?
- I have disabled this option with some business class VPN routers and the connectivity still worked to the remote network but it does not work to the Asus router.
Question2: From the information provided can I determine where the problem lies?
Is it the:
1) Remote client PC
2) Remote client router
3) Home office VPN router (Asus RT-N66U)
If the true culprit cannot be determined yet, what steps do you recommend so I can isolate the true cause of the failure.
I appreciate any help so that I can be sure my solution is valid and pass along the findings to ASUS if it is their issue.Thank you for the suggestion. I have successfully connected through the VPN router when the one client was unable to get VPN throughput working.
I looked at the routing tables with and without the VPN connection established. The differences are that:
1) when VPN is NOT active, there is a route from the local NIC IP to the Internet IP address of the local gateway
destination 68.109.82.xx
mask 255.255.255.0
gateway 192.168.0.1
interface 192.168.0.11
metric 21
2) when VPN IS active, the route to the Internet IP address of the local gateway is deleted and a persistent route to the VPN router local network has been added
Persistent route:
destination 192.168.21.0
mask 255.255.255.0
gateway 192.168.0.1
interface 192.168.0.11
metric 1 -
An ip address keeps showing up in the proxy setting under the "Bypass proxy settings for these Hosts & Domains." I keep erasing them and they pop back in.
An ip address keeps showing up in the proxy setting under the "Bypass proxy settings for these Hosts & Domains." I keep erasing them and they pop back in.
-
Cannot Make PPTP VPN Connection in 10.7.4
As far as I can tell everything is setup correctly but every time I try to connect I get this message:
You were disconnected by the communication device. Try reconnecting. If the problem continues, verify your settings.
Console Log:
6/25/12 5:11:40.382 PM pppd: PPTP connection established.
6/25/12 5:11:40.443 PM pppd: Connect: ppp0 <--> socket[34:17]
6/25/12 5:11:40.447 PM pppd: PPTP error when reading socket : EOF
6/25/12 5:11:40.447 PM pppd: PPTP error when reading header : read -1, expected 12 bytes
6/25/12 5:11:40.447 PM pppd: PPTP hangup
6/25/12 5:11:40.448 PM pppd: Connection terminated.
6/25/12 5:11:40.454 PM pppd: PPTP disconnecting...
6/25/12 5:11:40.455 PM pppd: PPTP disconnected
I am trying to connect to a Linux based VPN server. I have double checked my username and password multiple times, made sure the MTU is set the same on client, server, and router, and tried turning the encryption off and on on the server and the client. Nothing has made a difference, I get the same error every time. I am able to FTP and SSH into the Linux box.
Any suggestions of other things to try would be much appreciated. I saw some threads about editing config files on my mac but this is a brand new machine that I have had for a week running an OS that is on it's fourth point release. I really should not have to muck around with config files but at this point I'm ready to try anything.Looks like it might be a configuration error on the server's end. The VPN makes a connection and tries to read the server's configuration to create a socket for communication, but runs into a formatting error when it is passed an "End of File" character instead of a required component of the socket. Can you try connecting to another VPN server, or perhaps try an L2TP connection instead of PPTP?
-
How do I set up Mozilla to accept connections on port "The World Wide Web service (HTTP)"?
When attempting to embed a video in PowerPoint 2013, the message "Sorry we are having some temporary service issues" appears.
In researching the problem at Microsoft. com, the following message was received: Mozilla is not set up to accept connections on port "The World Wide Web service (HTTP)."Hmm... PowerPoint should use Windows to connect to the internet and not Firefox.
Which method are you using?
(1) Insert > Video > Online Video
Apparently there was an update this month that enables this, as described in this support post (see top Answer just after the question): [http://answers.microsoft.com/en-us/office/forum/office_2013_release-powerpoint/embedding-online-you-tube-video-in-powerpoint-2013/0bc00dde-420c-4c6a-bd47-3fb105ce40fc Embedding online you tube video in powerpoint 2013 - Microsoft Community]
Here's how it should work after the update: [http://office.microsoft.com/en-us/powerpoint-help/insert-or-link-to-a-video-on-youtube-HA104192855.aspx Insert or link to a video on YouTube - PowerPoint]
(2) Developer > More Controls > Shockwave Flash Object
As documented on other sites, such as: https://www2.palomar.edu/pages/atrc/2013/09/17/how-to-embed-youtube-video-in-powerpoint-2013/ -
How good does Indesign work over a VPN connection?
We are a small, widely distributed publisher using Adobe Indesign, Incopy etc. We would like to allow access to our server for outside designers, and are looking into a VPN solution. We have implemented a test of VPN, and it appears to work OK for file access, however the load and save times are rather long.
Is anyone using these tools with file access over VPN in a production environment? Please let me know issues, such as reliability, file corruption or other issues. Also, what sort of non-standard configurations do you recommend for the software.
Thanks in advance for discussing this type of environment, because there are a number of advantages for distributed users.
Mark SellersHi Bob,
From my perspective, direct file access on a single server that is backup up every night has a lot of advantages, including:
Easy and familiar access
Fast access for in-house users, slower but reliable access for remote users
Better security
Easier for users - double click and go
Simpler workflow - no copying files from a "master" source to a third-party cloud drive
Basically, extending the identical resources that are provided in the office through the server, to remote locations seems logical.
Why do you believe that Dropbox and other cloud based solutions are better? I don't see the advantages over VPN.
Mark Sellers -
i had set ip addresses for my home wifi network manually,and now i want to connect my iPhone5 to this network.the phone can't connect.what i have to do?after changing the wifi network setting (channels and another things)i cant connect even.i want to reslove this problem.would you help me?!
Just thought I would bump this up in the conversation. Doing a further search I came across this discussion which is similar: Connecting to a wireless network via applescript?
However, I tried to build the Automator application as discussed and cannot get it to work. Very much a novice at Applescript and Shell Script but have created customized Automator services before. All I get now is "Shell Script command encountered an error". No more detail. I copied and pasted the script as shown in the email thread. Is there any other line or command I need to place in front of it?
Thanks again for any help -
Can't find PPTP option for making a new VPN connection
I'm trying to set up a new VPN connection. It needs to be a PPTP connection.
I opened System Preferences --> Network, and clicked on the "+" sign to set up a new VPN connection. I can't find an option to make it a PPTP connection. I think the default is the other kind (don't know the name, but it starts with "L").
How do I specify that a new VPN connection will be PPTP?
I tried looking for the "Internet Connect" application, but couldn't find it. Did that application disappear in OS 10.5?That solved my question - thanks Bob.
When I created the VPN account, I didn't notice the L2TP option that was selected by default, and It looks like you can't change that setting after an account is created. I deleted the account I had created incorrectly and created a new one - and it worked perfectly the first time.
Thanks. -
Hello Arch Community!
I'm trying to set up a PPTP VPN that automatically connects and routes all traffic on startup. The Wiki page still has instructions for rc.d. I've tried the following, but it doesn't seem to work
/etc/systemd/system/multi-user.target.wants/pia.service
[Unit]
Description=Starts PIA_CALI.
[Service]
Type=Simple
ExecStart=/usr/bin/pon PIA_CALI
[Install]
WantedBy=multi-user.target
When I run systemctl start pia it acts like it works, but the ppp0 device is never created. It works fine when i simply run sudo pon PIA_CALI.
Any help would be greatly appreciated!
Thanks
drsn0wHi slreno,
Based on this link: http://support.microsoft.com/kb/314076, the following ports and protocol must be enabled for PPTP on all firewalls and routers that are between the VPN client and the VPN server:
Client ports Server port Protocol
1024-65535/TCP 1723/TCP PPTP
But as what you've posted, you have a modem/router from timewarner, then you might also need to open those ports on that device.
If everyone needs to believe in something, I believe I'll have another beer.. -
I recently added a new printer to a 2005 vintage PC that is running windows 7. It used to go through a router in my wifes upstairs office to the time capsule by wired ethernet (cat5) but when I added her new local printer thought I would network it, big mistaked, lost all my ethernet connection and she cannot get to the internet. Wireless not an option. How do i set up again the ethernet connection and i will only USB the printer locally this time for the windows pc?
Tried windows diagnostics, and besides telling me to reset everything and turn router off and on etc. I am in an endless loop.
Other Mac products are not impacted by this issue.I see no direct connection.. a printer and the computer setup for internet are not related.
But it sounds like the router in the wife's office is now in the wrong mode..
If you have an existing main router replace the second router for a switch .. that is the easy way.
Otherwise you need to bridge the router if it has that option.. most do not. Or use wan bypass.. where you turn off the dhcp server in the router and fix its ip to match the range of the main router.. this is the hassle of using router as a switch.
BUT I am making a huge number of assumptions.
What I need is the full network layout.. a quick picture would help.
I need main modem.. main router.. (maybe same box or different).. make model and current IP address and how dhcp is setup.
I need secondary router.. if that is what it is, IP and settings.
I want the printer type and model. How it is connected.
BTW I much prefer to see a network printer plugged into the network rather than usb.. it is only a matter of sorting the IP settings and driver pointing to the network rather than local.
Or you should think of it as a broken washing machine and call the technician.. who could fix the whole lot in an hour. -
Remote Desktop/Access shared files over PPTP VPN
Hello,
I just bought the RV180W so I can connect to my office computer from anywhere as a VPN client. The two things I need to do while I am connected as a VPN client is to be able to access my files on my office desktop and be able to remote desktop to it as well. I have Win7 on all of my computers. Ideally, I would like to do that over PPTP VPN connection but if that is not possible I can try Cisco QuickVPN software.
I enabled PPTP on my router and created a user account. I was also able to successfully establish the connection remotely. While I was connected as a PPTP VPN client, I was able to access the Internet and my router setup page which is telling me that the connection is good. However, I was not able to either discover my office PC under my network tab in Win7 nor I was able to remote desktop. I keep my office PC on all the time and it never go to sleep. I did not create any connection policy but maybe this is the problem. Please let me know if you know of a solution.
Thanks!Hi David,
Thank you for the response.
I was able to access the router configuration using the local IP address (in my case 192.168.1.1). I don't think I would have been able to access it using the public IP address since I have the router remote management feature disabled.
Now after reading your email, I was finally able to remote desktop and access shared files through a PPTP VPN connection. Here is what I did:
1- I separted the PPTP VPN IP address range from my DHCP range (in my case, PPTP VPN range is 192.168.1.200 to 210 and my DHCP range is from 192.168.1.100 to 199)
2- I assigned my office desktop PC that I am trying to remote desktop to a fixed IP address (192.168.1.20)
3- For remote desktop, I had to type the IP address (192.168.1.20). Typing the PC name (officepc) or searching for was not working.
4- For shared files, I had to map a network drive as //192.168.1.20/My Pictures for example. I couldn't find my PC when searched for it under Network.
After doing all that, I was able to do kinda what I wanted. Ideally, I would have liked to avoid using fixed IP addresses and be able to access computers by their name and see them under the Network tab. Is their a way to do this? I noticed that RV220W offers SSL VPN, would that help me?
I would appreciate it if you could answer my last two questions.
Thanks!
Mustafa -
After purchasing a wireless account,how do I set up a cellar data connection? Do I just turn the cellar data on?
That should be all that is required.
-
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]
Maybe you are looking for
-
Unable to capture from DV tape
I was given a Mini DV tape and when I try to capture it starts the first few seconds and stop with the following message: "Capture encountered a problem reading the data on your source tape. This could be due to a problem with the tape. Capture has b
-
Portlets Issues:- Included resource or file not found
I am facing some problems in the loading of portlets with Weblogic 9.2.When I access the portal url all the portlets are displayed blank by giving the following error message on the server : <Error> <HTTP> <BEA-101214> <Included resource or file "/my
-
Hello, I'm trying to set up my Arch Linux and I have a problem which I don't know how to solve. Originally I tried to follow these steps https://wiki.archlinux.org/index.php/Au - al_console https://wiki.archlinux.org/index.php/Start_X_at_Boot ( I use
-
Profit Centre Document Not Generating
Hello All, I have made GR entry and later on in the month end i found it as goods received but no invoice and done GR clearing using MR11. The issue is that the MR11 document is not generating the profit centre dcoument along with which it should gen
-
I recently updated my Adobe Air from 2.0 to 2.7. Doesn't this mean that my Flash CS5.5 will also have the option of using this version of Air as a player? I checked but I couldn't find it. It went only till Air 2.6 The Reason I updated Air was becaus