On a couple of our production AWS On-Demand Fortigates, no logging is
visible in the UI. I know logging is occurring because we also log to
ELK. Additionally I cannot start a packet capture in the UI. I have
double checked that informational logging ...
About 9 days ago we started receiving netflow data from a customer's
FortiGate firewall. At that time, the date/times in the flows were about
12 days in the past. I have confirmed the "bad" times exist in the
incoming raw packets. Over the next 8 day...
I've created policies to restrict traffic to the internet sourced from a
FortiGate 6.2 device itself, but they're not working. They're at the top
of the policy list, and Deny in enabled. Is this possible?
I'm trying to set up an aggregated site-to-site ipsec tunnel to take
advantage of load balancing/redundant WANs. The purpose the the tunnel
is to export netflow to a remote collector, using VIPs as the source and
destination of the netflow. The probl...
I have a Fortigate instance in AWS that I cannot get to with ssh or
https. It was accessible since creation (months), then all of a sudden
it was not. I can ping it, and (by using nmap) can see that ports 22,
443, 500 and 4500 are accessible and list...
The firewall's system time has been confirmed to be correct. The time
difference in the netflows have gone from being 12 days behind to 3 days
ahead over the course of a week and a half.
Version is 6.2.4. I did inspect a pcap, that's how I identified the
problem. I took the current seconds, subtracted the sysuptime, then
added the duration seconds.
I'm just testing using Fabric Connector in policies, and just picked
outbound traffic to test.I can test with inbound as well, if I can use
Fabric Connector objects in a local-in-policy.
