I recently started messing with SD-WAN in my home-lab. As my Lab setup heavily relies on zones (simplifies ruleset management) and I dod not want that SD-WAN Interfaces disrupt my design, I came up with the glorious idea of adding also internal interfaces to the SD-WAN zone.
Turns out, this works great as long as only firewall rules are involved, and some quirks around Multicast Rules and Central NAT (needs plain interface) works as expected.
The only trouble I found was the transparent proxy (i.e. using firewall with http(s) redirect and Proxy policy in transparent proxy mode), I did not get any rule hits (in the proxy policy). Changing the source interface to any return the functionality, but at loss of some security. (there is a reason, why FortiGate is a zone based firewall)
Alternatively disabling the http(s) redirect on the firewall policy, and use flow based security policy works as well.
But I am a fan of neither.
Question: Am I mis-using SD-WAN for a setup that is was never intended? of did I hit (another) FortiBug?
PS. for the destination Interface, an SD-WAN interface can be used. the issue only appears, if the source interface is a SD-WAN Interface.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.