TL-R600VPN IPsec VPN error

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

TL-R600VPN IPsec VPN error

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TL-R600VPN IPsec VPN error
TL-R600VPN IPsec VPN error
2015-02-10 11:36:14 - last edited 2021-04-19 11:24:14
Region : UnitedStates

Model : TL-R600VPN

Hardware Version : V2

Firmware Version : 1.2.3 Build 140801 Rel.49374n

ISP : TimeWarner / Verizon FIOS


We stopped requiring one of our four offices being connected to the network so I deleted that specific IPsec policy in our main site router (all routers are TL-R600VPN). After I did this I started noticing the following in our main site router system log:

"VPN ERROR couldn't find configuration."

In our remote site router system logs I saw a different error:

"VPN ERROR invalid flag 0x08."

Based on this information I figured there was a problem with the main site. I have taken the following steps:

1. Rebooted all routers
2. Rebooted all modems
3. Upgraded the firmware of all routers
4. Deleted and re-created the IPsec ad IKE policies for all routers

I am at a loss for what to do. The error doesn't give me much to go on.
  0      
  0      
#1
Options
7 Reply
Re:TL-R600VPN IPsec VPN error
2015-02-11 10:44:51 - last edited 2021-04-19 11:24:14
You may reset all of them to factory defaults and reconfigure them since it has been messed up.
I cannot think up how does it happen but it is abnormal obviously.
Good luck.
  0  
  0  
#2
Options
Couldnt find Configuration
2015-06-03 05:02:59 - last edited 2021-04-19 11:24:14

burrwhiterealty wrote

Region : UnitedStates

Model : TL-R600VPN

Hardware Version : V2

Firmware Version : 1.2.3 Build 140801 Rel.49374n

ISP : TimeWarner / Verizon FIOS


We stopped requiring one of our four offices being connected to the network so I deleted that specific IPsec policy in our main site router (all routers are TL-R600VPN). After I did this I started noticing the following in our main site router system log:

"VPN ERROR couldn't find configuration."

In our remote site router system logs I saw a different error:

"VPN ERROR invalid flag 0x08."

Based on this information I figured there was a problem with the main site. I have taken the following steps:

1. Rebooted all routers
2. Rebooted all modems
3. Upgraded the firmware of all routers
4. Deleted and re-created the IPsec ad IKE policies for all routers

I am at a loss for what to do. The error doesn't give me much to go on.


Did you ever fix this? I am getting that same error. Couldnt Find Configuration. I cannot simply reset these back to factory.. they are at 2 remote sites it is 6 hours of driving. They both have internet up.. one is the main office and has Exchange email and active sync working. How did you fix yours? Please?
  0  
  0  
#3
Options
Re:TL-R600VPN IPsec VPN error
2016-12-10 12:18:20 - last edited 2021-04-19 11:24:14
Curious if anyone has encountered this error, recently. I've had these boxes for a few years and thought I knew their quirks.

This one popped up after I disconnected the router for a few days after prepping the config and ensuring that the VPN did indeed work, even with my obscure setup.


The system is like this...


[Home router] ---> [Unmanaged switch] ---> [PC]
[Home router] ---> [Unmanaged switch] ---> [TL-R600VPN] ---> [PC]


This was working fine by opening the UDP 4500 and 500 ports for my R600's WAN IP (172.16.1.53). I was able to connect to the other site and work on the remote network/systems, just fine.

Take it down to wire it up, properly... don't get around to it a few days; now nothing works.


I'm seeing a new error in the System Log, now.
VPN ERROR couldn't find configuration.

But there's more to it. It seems that the connection is attempted. I'm including a modified log.

12.345.678.90 is the dummy remote IP.


Index Time Type Level Log Content
172 Dec 9 22:57:22 VPN ERROR couldn't find configuration.
171 Dec 9 22:57:15 VPN ERROR phase2 negotiation failed due to time up waiting for phase1. ESP 12.345.678.90[0]->172.16.1.53[0]
170 Dec 9 22:57:14 VPN INFO ISAKMP-SA deleted 172.16.1.53[500]-12.345.678.90[500] spi:xxxxxxxxxx:0000000000000000
169 Dec 9 22:57:05 VPN ERROR couldn't find configuration.
168 Dec 9 22:57:01 VPN ERROR couldn't find configuration.
167 Dec 9 22:56:57 VPN ERROR couldn't find configuration.
166 Dec 9 22:56:54 VPN INFO isakmp_newcookie 2505 Get 16 bytes from urandom.
165 Dec 9 22:56:54 VPN INFO isakmp_newcookie 2499 Get no bytes from random,try /dev/urandom.
164 Dec 9 22:56:54 VPN INFO initiate new phase 1 negotiation: 172.16.1.53[500]<=>12.345.678.90[500]
163 Dec 9 22:56:53 VPN ERROR couldn't find configuration.
162 Dec 9 22:56:49 VPN ERROR couldn't find configuration.
161 Dec 9 22:56:42 VPN ERROR phase2 negotiation failed due to time up waiting for phase1. ESP 12.345.678.90[0]->172.16.1.53[0]
160 Dec 9 22:56:41 VPN INFO ISAKMP-SA deleted 172.16.1.53[500]-12.345.678.90[500] spi:xxxxxxxxxx:0000000000000000
159 Dec 9 22:56:32 VPN ERROR couldn't find configuration.
158 Dec 9 22:56:28 VPN ERROR couldn't find configuration.
157 Dec 9 22:56:24 VPN ERROR couldn't find configuration.
156 Dec 9 22:56:20 VPN INFO isakmp_newcookie 2505 Get 16 bytes from urandom.
155 Dec 9 22:56:20 VPN INFO isakmp_newcookie 2499 Get no bytes from random,try /dev/urandom.
154 Dec 9 22:56:20 VPN INFO initiate new phase 1 negotiation: 172.16.1.53[500]<=>12.345.678.90[500]
153 Dec 9 22:56:20 VPN ERROR couldn't find configuration.
152 Dec 9 22:56:15 VPN ERROR couldn't find configuration.
151 Dec 9 22:56:08 VPN ERROR phase2 negotiation failed due to time up waiting for phase1. ESP 12.345.678.90[0]->172.16.1.53[0]
150 Dec 9 22:56:07 VPN INFO ISAKMP-SA deleted 172.16.1.53[500]-12.345.678.90[500] spi:xxxxxxxxxx:0000000000000000
149 Dec 9 22:55:58 VPN ERROR couldn't find configuration.
148 Dec 9 22:55:54 VPN ERROR couldn't find configuration.
147 Dec 9 22:55:50 VPN ERROR couldn't find configuration.
146 Dec 9 22:55:47 VPN INFO isakmp_newcookie 2505 Get 16 bytes from urandom.
145 Dec 9 22:55:47 VPN INFO isakmp_newcookie 2499 Get no bytes from random,try /dev/urandom.
144 Dec 9 22:55:47 VPN INFO initiate new phase 1 negotiation: 172.16.1.53[500]<=>12.345.678.90[500]
143 Dec 9 22:55:46 VPN ERROR couldn't find configuration.


But what's killer is that the remote site, 12.345.678.90 has two working site-to-site connections during this. AND! It is also showing the " couldn't find configuration." error!


Anyone else have issues like this and figure out what's wrong?


Local and Remote routers are identical:
Firmware Version: 1.2.3 Build 140801 Rel.49374n
Hardware Version: R600VPN v2 00000000

I have tried all manner of reboots, and profile deletes/rebuilds to get these IPSec Connections going.

And again, these ran fine with none of this missing config nonsense, before.
  0  
  0  
#4
Options
Re:TL-R600VPN IPsec VPN error
2016-12-10 13:56:03 - last edited 2021-04-19 11:24:14
So, this issue has evolved a bit, since I posted it.

A key point to keep in mind is that both locations use DynDNS and domains to connect to one another.


The primary site (12.345.678.90) has Dyn set up on the TL-R600VPN say with the domain "office.selfip.com."

The remote location is sitting behind another router with open ports (500 and 4500, UDP). The primary router, here, connects to Dyn with a domain like "somecity.selfip.com."


Now, I can ping somecity.selfip.com, I can find it while running through the router at the remote office, somecity.selfip.com is not the issue.

I must use the IP address associated with somecity.selfip.com in order to connect.


It seems I forgot this was a point in the first setup, as I didn't have the new domain up at the time when first testing.

So now the question is, why is the sub-routed TL-R600VPN not connected to when accessed with a domain?


I'm so tired and lost, now. Sent a message to support. We'll see. Anyone have any thoughts? I'm going to keep trying. Maybe it was a fluke.
  0  
  0  
#5
Options
Re:TL-R600VPN IPsec VPN error
2020-01-18 05:39:07 - last edited 2021-04-19 11:24:14
i found the issue VPN Internet notw working and , so i enabled Multi net NAT For VPN IP Pool then it's working fine
  0  
  0  
#6
Options
Re:TL-R600VPN IPsec VPN error
2020-03-14 03:22:17 - last edited 2021-04-19 11:24:14
Where did you enable the Multi net NAT For VPN IP Pool? I have this problem and I can't find that setting in the PTPP VPN configuration or anywhere else in the admin.
  0  
  0  
#7
Options
Re:TL-R600VPN IPsec VPN error
2020-03-18 10:53:01 - last edited 2021-04-19 11:24:14

@markoan i found that option under Transmission -> NAT ,,

 

add to ip ipsegment to NAT  

  0  
  0  
#8
Options

Information

Helpful: 0

Views: 6608

Replies: 7

Related Articles