SSLVPN remote client can't ping the internal interface of the FGT.

[thikfly]

I have set up the sslvpn, remote client can connect the sslvpn and can ping the turst lan, but only can't ping the internal interface of the FGT.

remote client   <-->   (wan1)FGT(internal(172.30.26.1))  <---> other server(172.30.26.251)

How to do ?

diagnose sniffer packet ssl.root icmp interfaces=[ssl.root] filters=[icmp] pcap_lookupnet: ssl.root: no IPv4 address assigned 23.606374 10.212.134.200 -> 172.30.26.1: icmp: echo request 28.539743 10.212.134.200 -> 172.30.26.1: icmp: echo request 33.538525 10.212.134.200 -> 172.30.26.1: icmp: echo request 38.541238 10.212.134.200 -> 172.30.26.1: icmp: echo request 46.002575 10.212.134.200 -> 172.30.26.251: icmp: echo request 46.003417 172.30.26.251 -> 10.212.134.200: icmp: echo reply 46.998720 10.212.134.200 -> 172.30.26.251: icmp: echo request 46.999369 172.30.26.251 -> 10.212.134.200: icmp: echo reply 47.999794 10.212.134.200 -> 172.30.26.251: icmp: echo request 48.001342 172.30.26.251 -> 10.212.134.200: icmp: echo reply 49.001606 10.212.134.200 -> 172.30.26.251: icmp: echo request 49.002319 172.30.26.251 -> 10.212.134.200: icmp: echo reply

[MikePruett]

1. Is PING enabled on said interface?

2. Is policy built to allow it?

3. Split tunnel or full tunnel?