@TeeCee 

 

Of cource you can set up LAN to LAN VPN and Client to LAN VPN at the same time. But your current firmware version seemly have the conflict issue. Suggest to connect TP-Link Support for help.

 

For the issue that cannot ping PC, maybe caused by firewall of the PC. You can try to close the firewall for both PC then ping again.

@Andone

 

Thaks for your response.

I've reported problem to TP-Link Support and they have solved it. I have beta firmware to test 

 

 

Update: it works! :-D

 

Firewall - it's very likely... Norton Security works in background. I'll try to shut Norton down.

 

Update: Norton is the cause

 

 

So.. thanks!

 

Fairytale gone bad...

 

I try to add second IPSec policy for another Client-Lan user.

The same error. I do not understand it. Why can't I have more than one client having the same acces to the same local subnet???

 

It is annoying... :-/

IPsec VPN will transfer the data based on the remote IP and local IP. For two VPN tunnels, remote IP cannot overlap and local IP cannot overlap. Did you setup the client to LAN and use 0.0.0.0 as remote gateway? If yes, you can only setup one client to LAN entry. Because 0.0.0.0 means all IP address, so other IP address will has overlap. Unless you use different local subnet or WAN interface. You also can use L2TP over IPsec, it can use IPsec encryption so it's also secure.

Thanks for your reply.

My settings are below. I want to have access from different remote host (ID 2 and 3) to the same Local Subnet. I do not use 0.0.0.0 Remote Host.

 

I thought if I can have access to one local subnet from another lan and client (ID 1 and 2) in the same time, I can add another client with different Remote Host...