Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
HANDL_Eric
New Contributor

FortiGate Phantom Traffic

Alright,

 

so we just migrated our datacenter firewall from a Cisco ASA to new FortiGate boxes, and inside this DC is our primary/active FortiManager VM. Well with this migration we pre-created the DNAT policy to map a public address to the inside IP of the FortiMAnager VM but intentionally did not create a security policy expecting all the traffic would be blocked and all the external/remote boxes would disconnect.

 

To our surprise, after the migration was completed we logged into FortiManager and found that all the remote firewalls are still connected and fully communicating. After this discovery we quickly logged into the edge firewall and do not see a single trace of that traffic outside of hit counters on the DNAT rules. It's as if this traffic doesn't exist - the only thing demonstrating it exists are all the connected devices.

 

The firewall is running in policy-based mode, and there is currently a 1:1 DNAT rule, but no security policies for the flow. Has anyone experienced this or know why this could be occurring? We opened a support case but the engineer seemed stumped and is escalating the issue internally. Figured id ask the group as we obviously want to ensure out FortiManager and any other potential systems aren't exposed.

1 REPLY 1
syordanov
Staff
Staff

Hello HANDL_Eric ,

Did you check the session on the FortiGate which allows the traffic to/from your FortiManager?
If not, try the following commands :


List the sessions where your FortiManager is acting as destination :

diag sys session filter dst XXXXX.XXXXX.XXXX.XXXX <---- destination IP / FortiManager
diag sys session list


List the sessions where your FortiManager is acting as a source:

diag sys session filter clear
diag sys session filter src XXXXX.XXXXX.XXXX.XXXX <---- destination IP / FortiManager
diag sys session list


This will give more info, if there are sessions to or from your FortiManager IP address.

Another usefull output could be to grep the sessions where the IP address of your FortiManager is matched :

get system session list | grep x.x.x.x <---- IP address of your FortiManager.

 

Best regards,
Fortinet

.
Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors