C. read the kernel debug buffer to obtain debug messages.
D. enable kernel debugging.
3 Comments on “The command fw ctl kdebug <params> is used to:”
Sidzasays:
Reads the debug buffer and obtains the debug messages. If there is no debug buffer, the command will fail.
0
0
prosto_marussiasays:
fw ctl debug
A – This will SET various debug flags. You will use this to turn on VPN on NAT (among MANY others) debugging, but won’t print the debug logs.
fw ctl kdebug
A – This will start PRINTING the debug logs. Using this command, you can print the debug logs to the console/SSH screen, or to a file.
fw ctl zdebug
A – This is a “Shortcut” combination of the above 2 debug commands. This is TYPICALLY used as “fw ctl zdebug drop” to start printing FW Drop logs to the screen.
0
0
prosto_marussiasays:
fw ctl debug
A – This will SET various debug flags. You will use this to turn on VPN on NAT (among MANY others) debugging, but won’t print the debug logs.
Reads the debug buffer and obtains the debug messages. If there is no debug buffer, the command will fail.
0
0
fw ctl debug
A – This will SET various debug flags. You will use this to turn on VPN on NAT (among MANY others) debugging, but won’t print the debug logs.
fw ctl kdebug
A – This will start PRINTING the debug logs. Using this command, you can print the debug logs to the console/SSH screen, or to a file.
fw ctl zdebug
A – This is a “Shortcut” combination of the above 2 debug commands. This is TYPICALLY used as “fw ctl zdebug drop” to start printing FW Drop logs to the screen.
0
0
fw ctl debug
A – This will SET various debug flags. You will use this to turn on VPN on NAT (among MANY others) debugging, but won’t print the debug logs.
0
0