WPA_CONFIG(8)
NAME
wpa_config - a small config manager for wpa_supplicant
DESCRIPTION
wpa_config makes configuration of wpa_supplicant - the only sane way to use WLAN networks - a lot simpler. One of the only drawbacks of using bare wpa_supplicant when compared to unwieldy bloatware like NetworkManager, is the fact that mucking around in a single, large config file for all networks can be quite cumbersome.
With wpa_config, every network is its own file in a folder, as are the options for the wpa_supplicant. It simply merges all these files into a single file, which then becomes your wpa_supplicant.conf. It also provides utility functions for quickly generating new entries.
wpa_config does not manage the operation of wpa_supplicant. It’s a config manager, not a network manager. It might add a facility to restart wpa_supplicant using your init system in the future.
FILES
wpa_config uses three primary config files and a directory for network configurations. All of these are located in the CONFIG_ROOT directory, which by default is /etc/wpa_config.
wpa_config.conf
The configuration file for wpa_config itself. There are no settings so far, but there might be some in the future (for example, choice of init system to restart wpa_supplicant).
wpa_supplicant.conf.head
This file contains settings for wpa_supplicant, for example the ctrl_interface or the eapol_version.
wpa_supplicant.conf.tail
This file is appended to the generated config. It’s a great way to migrate your currently configured networks, no need to reconfigure them.
networks.d/
This directory contains the configurations for the single networks. Every file in it should be in the form “${SSID}.conf”.
COMMANDS
wpa_config has severeal subcommands which do all the work.
add
Create a new file in the network directory. Currently, this only works for WPA secured and open (unencrypted) networks. Specifying more options ( WEP, ad-hoc, etc) will be added later.
del
Delete a network in the network directory, if it exists.
show
Print the configuration of a network.
edit
Open an editor (specified by the EDITOR environment variable) to change the config of a network.
list
List all networks configured through wpa_config. Note that this does not list networks configured in wpa_supplicant.conf.tail.
make
Merge all config and network files into wpa_supplicant.conf, writing it to WPA_SUPPLICANT_CONFIG (usually /etc/wpa_supplicant/wpa_supplicant.conf).
migrate
Migrate your old wpa_supplicant.conf to wpa_config. This extracts all configured (and uncommented) networks from wpa_supplicant.conf, and creates single config files in the networks.d/ directory for them. This strips all comments, so be careful.
help
Show a help message. Same as specifying -h or –help.
SEE ALSO
wpa_supplicant(8)
wpa_supplicant.conf(8)
1 maintainer
Metadata
1 maintainer
Release files for wpa_config 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| wpa_config-0.2.1.tar.gz | 7.6 kB | Without provenance | Details |
Release files / wpa_config-0.2.1.tar.gz
| Download URL | wpa_config-0.2.1.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f974ae5c9eccbb22740a6f227691bc850c70bfcf7f837652dfa5387c4cde081
|
|
BLAKE2b-256 checksum How to use checksums |
595880fd2dfa770dc60aad08801ac0337255dfa2fc276ef91e7b7c18c4cc9f84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for wpa_config 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
