mirrors/cheat-sheets
1
0
Fork 0
mirror of https://github.com/yuriskinfo/cheat-sheets.git synced 2025-12-21 13:23:11 +01:00
Code Issues Packages Projects Releases Wiki Activity

Added to FGT Debug cheat sheet DHCP debug

Browse Source
This commit is contained in:
Yuri Slobodyanyuk
2022-03-08 17:31:48 +02:00
parent b446369e49
commit 3fe09c48fa
1 changed files with 27 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
cheat-sheets/Fortigate-debug-diagnose-complete-cheat-sheet.adoc
View File

@@ -353,7 +353,7 @@ just clear Fortigate DHCP database and will start over allocating again. You can
|*diagnose debug application dhcps -1*
|enable real-time debug of DHCP server activity.
|enable real-time debug of DHCP server activity. This will show DHCP messages sent/received, DHCP options sent in each reply, details of requesting hosts.
|===
@@ -593,6 +593,32 @@ just clear Fortigate DHCP database and will start over allocating again. You can
|===
== SIP ALG and helper
.SIP proxy or helper debug
[cols=2, options="header"]
|===
|Command
|Description
|*config sys settings*
*get | grep alg*
|Show what is the current SIP inspection mode. If the output is `default-voip-alg-mode: proxy-based` then the full Layer 7
proxy SIP inspection is on (_ALG_ inspection). If the output is `default-voip-alg-mode: kernel-helper-based` then the Layer 4 _helper_ inspection is on. In both modes Fortigate does IP address translation inside SIP packets (if needed), and opens dynamically high ports for incoming media/voice streams ports. In _ALG_ mode, the Fortigate additionally does RFC compliance verification and more. So, the _ALG_ mode is more prone to cause issues but also provides more security.
|*show system session-helper | grep sip -f*
|If using SIP _helper_ and not _ALG_, make sure there is an entry for SIP in the helpers list, usually on port 5060, but may be custom as well.
|*diagnose debug application sip -1*
|Display SIP debug in real-time (lots of output). It shows IP replacement inside SIP packets if NAT involved, all SIP communication requests (`REGISTER`,`INVITE` etc.), and reply codes.
|===
== DNS server and proxy debug
[cols=2, options="header"]
|===