From what I understand so far, hostapd is a binary which is able to do some network configurations.
However, to enable hostapd debug level, do I need to rebuild the binary? Is there any other approach I can take instead of rebuilding a new one ?
Executing hostapd with no arguments reveals that specifying -d or -dd enables debug messages:
hostapd
-d
-dd
-d show more debug messages (-dd for even more)
It is also possible to configure the event logger verbosity via hostapd's configuration file:
# hostapd event logger configuration # # Two output method: syslog and stdout (only usable if not forking to # background). # # Module bitfield (ORed bitfield of modules that will be logged; -1 = all # modules): # bit 0 (1) = IEEE 802.11 # bit 1 (2) = IEEE 802.1X # bit 2 (4) = RADIUS # bit 3 (8) = WPA # bit 4 (16) = driver interface # bit 5 (32) = IAPP # bit 6 (64) = MLME # # Levels (minimum value for logged events): # 0 = verbose debugging # 1 = debugging # 2 = informational messages # 3 = notification # 4 = warning # logger_syslog=-1 logger_syslog_level=2 logger_stdout=-1 logger_stdout_level=2
Copyright © 2021 Jogjafile Inc.
Executing
hostapd
with no arguments reveals that specifying-d
or-dd
enables debug messages:It is also possible to configure the event logger verbosity via
hostapd
's configuration file: