Hi,
We use Fortimanager (FM) to administer several Fortigates (FG). Under Central-Management in the CLI, we set the fmg-source-ip to the FG's Loopback address. We have configured a server-list entry pointing to FM, which acts as an "internal" Fortiguard server. Lastly, we left the public Fortiguard servers enabled as a fallback.
An issue occurs when a FG tries to use the public servers. The packet leaving on the WAN interface has its source address set to the private Loopback address. I can’t find a way to specify using NAT for this local-out traffic on the WAN interface.
Does anyone have any suggestions?
Thank you for your time.
Larry
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hi Larry,
I'm afraid this is not possible, because self originating traffic is not handled by policies and nat rules. Maybe the latest firmware has some new features I don't know about yet, but in my experience for this to work you need to put this loopback interface in an own VDOM and then create the NAT rules and so on in the other VDOM.
Kind regards
Thank you oheigl. I was suspecting this to be the case. I hadn't thought of separating with VDOMs...
Larry
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1709 | |
1093 | |
752 | |
446 | |
231 |
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.
Copyright 2024 Fortinet, Inc. All Rights Reserved.