Ensure wpa_supplicant logs to syslog #1056
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ensure wpa_supplicant logs to syslog
Description
After enabling encryption as described in the documentation I noticed that every so often the
DECRYPT_ME
hotspot is not started.Motivation and Context
Currently wpa_supplicant does not log to its own file or syslog so this issue is hard to pin down. Having wpa_supplicant log to syslog allows for some troubleshooting
#1055
How Has This Been Tested?
Manually updated wpa_supplicant command in pwnlib with additional flags (
-u -s -O
) and rebooted. wpa_supplicant now logs to syslog.Types of changes
Checklist:
git commit -s