Technical Tip: ip-conn traffic action in logs

kcapecchi · 11-21-2016

DescriptionA FortiGate will communicate with all three ports on boot up, this is regardless of the port configuration on the FortiGate.For example on boot up where 172.18.26.177 is the FortiGate:143.602806 port1 in 172.18.26.177.5726 -> 172.18.26.174...

kcapecchi · 09-29-2016

DescriptionFortiGate units support a floor acceleration of 0.1g/s, this meets the specifications of NEBS (Network Equipment-Building System) and is about Richter Magnitude 5-6 earthquake.Generally speaking: 0.001 g (0.01 m/s²) – perceptible by people...

kcapecchi · 09-09-2016

Description This article provides an explanation of the entry 'action=ip-conn' that may be seen in the traffic logs. For example: Aug 23 03:52:14 10.95.216.1 date=2016-08-23 time=03:52:14 devname=external-fgt-01 devid=FGXXXXXXXX logid=0000000011 type...

kcapecchi · 10-07-2015

PurposeThis article explains how to block access to external proxy such as Tinyproxy or Ultrasurf but without excluding FortiGate Explicit Proxy legitimate traffic. This applies where explicit proxy is configured on the FortiGate unit.Expectations, R...

kcapecchi · 09-22-2015

DescriptionWith agent-based polling mode, there are two methods for getting logon information:.Security Event Log (WinSecLog): Polls the security events on the DC. It does not miss any logon events because events are not normally deleted from the log...

User Statistics

User Activity

Technical Note: Port 80 usage for communication between FortiGate and FortiManager

Technical Note: Maximum vibration limit supported by FortiGate models

Technical Tip: ip-conn traffic action in logs

Technical Note: Blocking communication to external proxy using the FortiGate explicit proxy

Technical Note: Agent-based polling mode methods

Technical Tip: ip-conn traffic action in logs

Technical Note : Logs not displayed because of cor...

Technical Note: FortiManager database checking too...

Fortinet Training Institute

KCS