For the last week or two, I've been seeing a LOT of hits for this trojan
(http://www.fortinet.com/ve?vn=W32%2FXCore.Y%21tr.bdr) across a lot of
customers. For probably a bit over half of them, it appears to be
blocking the install of that Cooking Fev...
version 5.6.7In System -> Settings, the HTTPS cert is set to
"self-sign"but in System -> Certificates, there is no cert with that
name. If I change this to the only other option "Fortinet_Factory", I
notice two things.This is definitely a different c...
Is there a way to generate a complete list of units in FA across all
ADOMS? I would like to be able to find a unit by serial number, if I
could make a list based on name I could figure out what ADOM it's in
from there.
Hi, Got a Fortigate 60E running 5.4.5. Client's ISP wants us to change
public static IP. This morning I added a new route for the new default
gateway, then I went over to WAN1 and updated the new IP and subnet
mask. Hit OK, and instead of changing, i...
Hi! I have a stange issue that I'm hoping someone can provide some
insight on. After upgrading a 90D unit from 5.2.1 to 5.2.3, it's
"hairpin" routes (same source and destination interface) are having
issues. It seems they are working fine for simple ...
oheigl wrote:Just export/backup the configuration and search for the ip
address in the file, then you will find where it is used :) Looks like
one of my coworkers hard coded the source IP for Fortianalyzer: config
log fortianalyzer setting set source...
Reporting that I just ran into this issue on a 60E running 5.4.3. Change
to source IP in firewall policy wasn't taking. Went to start up debug
flow and when I entered "diag debug enable", this error started popping
up every second. killed the most me...
jintrah wrote:This is an old function, you can use below, config system
global set tcp-option disable end This will no longer allow TCP
timestamps from showing up. I believe that will just stop the Fortigate
itself from generating tcp timestamps, it ...
