Business Community > All Threads > VPN with IPSec not working as expected
< All Threads

VPN with IPSec not working as expected

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

VPN with IPSec not working as expected

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
VPN with IPSec not working as expected
VPN with IPSec not working as expected
2019-03-20 20:12:01 - last edited 2021-04-19 11:54:03
Model: TL-R600VPN  
Hardware Version: V2
Firmware Version: 1.2.1 Build 130831 Rel.63039n

Hi!  I'm trying to connect a new remote office to the main office,  using a IPSec VPN tunnel.

 

I have two identical routers, one labeled as "ROUTER A" and the other as "ROUTER B", both are TL-R600VPN v2

 

The main office has a private LAN 192.168.0.0/24 and external IP 190.188.xxx.xxx (static)

 

The remote (new) office has a private LAN 192.168.35.0/24 and external IP 190.175.xxx.xxx (not static but for the test purpose I put IP as IPSec gateway to the other side)

 

 

I have the tunnel up looking at the SA Status and/or System log in both routers.

 

 

 

I do NOT HAVE a route established in ROUTER A to access the subnet at ROUTER B, and viceversa, in ROUTER B there is not a route to access to ROUTER A subnet.

 

 

 

I've made all steps from TPLink FAQ to make Lan-To-Lan VPN IPSec: https://www.tp-link.com/en/support/faq/380/

 

If I try to made a SATATIC ROUTE the system alert about an "IPsec policy conflicts with static route"

 

 

What I'm missing to redirect all traffic thru my vpn tunnel?

 

Thanks in advance!

01000111 01100101 01110010 01100001
  0      
 
  0      
 
#1
Options
4 Reply
Re:VPN with IPSec not working as expected
2019-03-21 07:07:35 - last edited 2021-04-19 11:54:03

Hi 

 

IPsec VPN is not based on routing. So you will not see the routing on the routing table. PPTP and L2TP is based on routing.

The router will detect the destination IP address. If it is in the range of remote subnet you set, the data will be forwarded into VPN tunnel.

  1  
  1  
#2
Options
Re:Re:VPN with IPSec not working as expected
2019-03-22 12:15:53 - last edited 2021-04-19 11:54:03

Now its working!!!!   

 

remote office Lan --- 192.168.35.10--[TL-R600VPN]--190.188.345.345-----(INTERNET)----190.188.678.678--[CISCO RV-042]--192.168.0.4---main office Lan

 

(Obviously the public IP are fakes.... hehehehe!)

 

I've replaced one of my TL-R600VPN to a Cisco RV042 (actually is the router to access internet at main office). The tunnel is up and I have ping from remote subnet to my main office router's subnet IP (i.e. I can ping from 192.168.35.10 to 192.168.0.4)

 

Thanks Andone for your reply!!

 

 

Gerardo

 

 

01000111 01100101 01110010 01100001
  0  
  0  
#3
Options
Re:VPN with IPSec not working as expected
2019-09-19 11:41:28 - last edited 2021-04-19 11:54:03

@Gerardo-ARG 

I am trying to set up a site to site VPN in our lab. I had it working last week and all the sudden I couldn't get it connected. So I reset it back to factor and set it up from scratch and I still have nothing.

 

Any thoughts on the config? It was very easy to set up the first time. I am able to ping both WAN interfaces from the opposite router.

  0  
  0  
#5
Options
Re:VPN with IPSec not working as expected
2019-09-20 09:17:41 - last edited 2021-04-19 11:54:03

@Lindaawilsoon 

 

If you are using IPsec VPN, please confirm both routers use the same encrypted option. 

If the router is behind other router, you need to set port forwarding on other router.

  0  
  0  
#6
Options

Information

Helpful: 0

Views: 4693

Replies: 4

Related Articles
Microsoft Azure Site to Site IPSEC VPN with TL-R600VPN
4572 0
TL-R600VPN IPSec VPN drops
308 0
TL-R600VPN Throughput de VPN IPsec
2330 0
VPN IPSec Failover
532 0
R600VPN - IPSEC VPN Tunnel - Internet access
1511 0
Not getting expected speeds
924 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.