IPSEC Tunnel up but can't reach networks from either side

Question

We can ping both ends of the tunnel. AWS shows tunnel up and configuration looks good but pings or traceroute from either side fails.   
  
This is from a mikrotik router to AWS. Not sure but I'm not certain the static routes in the VPC are setup correctly; this is one area where the documentation and interface are confusing. We have two route tables in the VPC (why two?). The main one has:  
  
Destination: 192.168.168.0/24	  
Target: local  
Status: active  
Propagated: no   
  
On route propagation tab:   
vgw-098a9408c7a7644ef | test gateway	  
propagation:Yes

**Second route table has:   
  
Destination: 192.168.168.0/24	  
Target: local  
Status: active  
Propagated: no  
   
Destination: 0.0.0.0/0	  
Target: igw-07f6a79ff6d669caf  
Status: active  
Propagated: no   
  
On propagation tab:  
vgw-098a9408c7a7644ef | test gateway	  
propagate: Yes  
  
Could I get someone at AWS to review the setup? VPC ID is vpc-0f67bbadf9545712c

Answer

Problem solved. Problem was on other end.

Answer

Care to share how you fixed it?  I'm in the same boat right now.  Tunnel is up for both, everything is set up correctly.  I have an instance fired up and the correct route on my end for that /24 to go through the tunnel.   I am unable to get a ping even though I allow it through the security group and acls etc.    
  
Been over all the instructions backward and forward.

IPSEC Tunnel up but can't reach networks from either side

Contenido relevante