FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
This article describes the WAD process on FortiGate models with 2 GB RAM.
Scope
FortiGate models with 2 GB RAM or less starting from version 7.4.4 and 7.6.0.
Solution
To optimize memory usage for FortiGate models with 2 GB RAM or less starting from version 7.4.4 and 7.6.0, FortiOS no longer supports proxy-related features.
This led to some wrong expectations that the WAD process also get removed on FortiGate models with 2 GB RAM, however this is not the case as the WAD Mandatory process (i.e. manager, config-notify) and wadBasic mandatory (i.e. single worker, informer, user-info, dev-vuln, user-info-history, debug) will still spawn on this model.
To verify, run the commands:
diagnose debug enable diagnose test application wad 1000 Process [0]: WAD manager type=manager(0) pid=179 diagnosis=yes. Process [1]: type=worker(2) index=0 pid=300 state=running diagnosis=no debug=enable valgrind=supported/disabled Process [2]: type=informer(4) index=0 pid=295 state=running diagnosis=no debug=enable valgrind=unsupported/disabled Process [3]: type=user-info(5) index=0 pid=296 state=running diagnosis=no debug=enable valgrind=supported/disabled Process [4]: type=dev-vuln(6) index=0 pid=297 state=running diagnosis=no debug=enable valgrind=supported/disabled Process [5]: type=debug(13) index=0 pid=298 state=running diagnosis=no debug=enable valgrind=unsupported/disabled Process [6]: type=config-notify(14) index=0 pid=299 state=running diagnosis=no debug=enable valgrind=unsupported/disabled
