Dear @Clive_A and others... WE FINALLY SOLVED IT !!! The problem cause was: - Our Upstream IP Provider did not route ESP Traffic correctly. Why it took so long to solve: - The gateways show the...

@Clive_A > He should've pinged the gateway of the remote end. From 192.168.100.1 to 192.168.2.1, and verify the tunnel status. As described already, any attempt to ping "through the tunnel" failed....

@RaRu > Hmmm, out of curiosity... Can you try to disable Block WAN ping option as well as enable Broadcast Ping? > (Yes, I know that you were also trying to SSH and other thing except the ping. Just...

@RaRu thanks again... > I don't see any issue here... > I'm just trying to compare that with my IPsec config which is working... What is most puzzling to me: the tunnel shows as "connected" under...

@RaRu Thanks! > 1. Do your TP-Link routers have Public IP? Or those are behing a NAT (ISP's device with public IP)? Yes, both sides are NOT behind any NAT, and they DO have fixed static global IPs. >...

First of all thank you everybody for looking into this. Here some clarification and the requested config screenshots. I am using Site-To-Site VPN in "Manual IPsec" Mode. First of all I would like to...