@manjotsc ok not exactly sure if understand what your wanting to do.. But you have a tunnel setup to your house in india. And you want to ping the india side vs the gateway itself right?
So for example I have a vpn setup to vps of mine ns1vpn here
monitor.jpg
Yeah out of the box when you setup a new gateway, it would monitor the gateway IP, and since its a tunnel it would be your own address as the gateway not the far end. This could still work for monitoring since if the tunnel is down it shouldn't answer pings? Have not played with that because I like to see what the response time is, vs the local zero rtt for pinging yourself.
gateway.jpg
Notice my wan and he gateway ping the actual gateway address. But my ns1vpn while the gateway is .2, the monitor address is .1 (the far end)
So I take it this is what you want to do? The far end of the tunnel your pinging would need to answer, firewall rule maybe on the far end. Setting the monitor to something on the far end would require that you can get there, can you get to 1.1.1.1 via this tunnel to your house in india? Maybe you do not allow that?
And your saying gateway monitor isn't working to the far end IP, but you can actually ping the far end of the tunnel from pfsense.
Looks like your one above the home_india is working, that looks like a tunnel were your gateway is 10.6.14.2 and your pinging 192.168.14.1