debug flow trace

Use this command to trace the flow of packets through the FortiWeb appliance’s processing modules and network stack.

Before you will be able to see any debug logs, you must first enable debug log output using the command debug.

To use this command, your administrator account’s access control profile requires only r permission in any profile area. For details, see Permissions.

Syntax

diagnose debug flow trace {start | stop}

Variable	Description	Default
trace {start \| stop}	Select whether to enable (`start`) or disable (`stop`) the recording of packet flow trace debug log messages.	No default.

Example

This example configures a filter based on the packet destination IP 192.0.2.48, enables messages from each packet processing module, enables packet flow traces, then finally begins generating the debug logs that are enabled for output (in this case, only packet trace debug logs).

Because the filters are configured before debug logging is enabled, the administrator can type the filter without being interrupted by debug log output to the CLI.

diagnose debug flow filter server-ip 192.0.2.48

diagnose debug flow filter module-detail status on

diagnose debug flow trace start

diagnose debug enable

Output:

FortiWeb # session_id=251 packet_id=0 policy_name=policy1 msg="Receive packet from client 172.20.120.225:49428"

session_id=251 packet_id=0 msg="HTTP parsing client packet success"

session_id=251 packet_id=0 policy_name="policy1" msg="

Module name:WAF_IP_LIST_CHECK, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_X_FORWARD_FOR_PROCESS, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_GEO_BLOCK_LIST, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_PROTECTED_SERVER_CHECK, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_ALLOW_METHOD_PROCESS, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_HTTP_ACTIVE_SCRIPT, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_HTTP_SESSION_MANAGEMENT, Execution:4, Process error:1, Action:ACCEPT

Module name:WAF_HTTP_DOS_PREVENTION, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_LAYER4_DOS_PREVENTION, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_HTTP_AUTHENTICATION, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_GLOBAL_ALLOW_LIST, Execution:4, Process error:0, Action:ACCEPT

Module name:WAF_URL_ACCESS_POLICY, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_BRUCE_FORCE_LOGIN, Execution:3, Process error:0, Action:ACCEPT

Module name:HTTP_CONSTRAINTS, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_COOKIE_POISON, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_FILE_UPLOAD_RESTRICTION_POLICY, Execution:3, Process error:0, Action:ACCEPT

Module name:ROBOT_CONTROL_PROCESS, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_PARAMETWER_VALIDATION_PROCESS, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_CHUNK_DECODE, Execution:3, Process error:2, Action:ACCEPT

Module name:WAF_FILE_UNCOMPRESS, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_SIG_DETECT_PROCESS, Execution:4, Process error:1, Action:ACCEPT

Module name:WAF_HIDDEN_FIELD_PROCESS, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_URL_REWRITING, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_FILE_COMPRESS, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_CERTIFICATE_FORWARD, Execution:3, Process error:0, Action:ACCEPT

Module name:WAF_AUTOLEARN, Execution:4, Process error:0, Action:ACCEPT

Module name:WAF_HTTP_STATISTIC, Execution:3, Process error:0, Action:ACCEPT

session_id=502 packet_id=0 policy_name=policy1 msg="Receive packet from client 172.20.120.225:49429"

session_id=502 packet_id=0 msg="HTTP parsing client packet success"

session_id=502 packet_id=0 policy_name="policy1" msg="