SSLVPN natting traffic to resource behind 2nd Fortigate
Hi
We have a SSLVPN Web portal on one Fortigate. When using it to get to resources behind a tunnel on another Fortigate, it seems to NAT the traffic despite the policy having NAT turned off.

FG2 sees the source address of traffic to AWS being 192.168.1.1 instead of 10.10.1.1
Can anyone explain what's going on here?
