Question No ping to LAN gateway

[spider48]

This issue seems normal but i need a solution which i haven't found since a long time. I have IPSEC connection in one of my branch ( 10.100.0.7/24 ) from the head office (10.100.0.1/24 ). LAN network of branch is 192.168.16.0/24. All the signal seems fine, ping request is reachable from the LAN network of head office (192.168.10.10/24 ) to the branch office, and the internet is working fine in the LAN network of branch but the main issue is i cannot ping the LAN gateway (192.168.16.1) from any remote branch LAN ip. Let's take it as 192.168.16.50
What's the actual issue ?
Internet is working fine in the branch, ping is made to the google and so far as per the networking term, to reach the google IP, that ICMP must move through the remote LAN gateway but ping is not reachable to the LAN gateway IP 192.168.16.1 from any one of the remote LAN ip.
Is there anyone who can solve this issue ?
Positive feedback would be highly appreciated.

 

[failboat]

Are you setting up site-to-site? do any other connections work from remote to LAN?
For site-to-site the route on the client needs the CIDR of the LAN and the LAN needs the CIDR of the remote site. You can monitor interfaces with iftop to see if connections are coming in and if they use their client ip (s2s) or the tun ip not site-to-site. then check that ip on the route table to see if it's got a correct path to next hop.
If it's not supposed to be s2s then the LAN would need the tun CIDR routes to drop it back into the VPN.

If you daisy chained the sites then you need to add routes in a few more places. A->b->c c needs to send A packs to b.
a->c<-b if remote sites only need access to c this would work. if a<->b is required then b would need to route A CIDR to C.