Minimal TUI Wi-Fi Manager: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
Good news! If you don't want to install third party daemons, gooey GUI things, or bloat just so you can connect to a wireless access point, then don't worry, Linux has all the CLI tools necessary to create a minimal on-demand TUI shell script thing to connect to, and manage these very Wi-Fi connections. The following info is for Debian, however the approach will be the same for other distros, including BSD operating systems that will differ mostly for some of the network commands. | Good news! If you don't want to install third party daemons, gooey GUI things, or bloat just so you can connect to a wireless access point, then don't worry, Linux has all the CLI tools necessary to create a minimal on-demand TUI shell script thing to connect to, and manage these very Wi-Fi connections. The following info is for Debian, however the approach will be the same for other distros, including BSD operating systems that will differ mostly for some of the network commands. | ||
== How does it work? == | |||
=== The things that mater === | |||
* <code>/etc/network/interfaces</code> — network interface configuration for ifup and ifdown | |||
* <code>iw</code> — show/manipulate wireless devices and their configuration | |||
* <code>wpa_cli</code> — WPA command line client | |||
* <code>wpa_supplicant</code> and <code>wpa_supplicant.conf</code> — Wi-Fi Protected Access client and IEEE 802.1X supplicant and its configuration file | |||
* <code>fzf</code> — command line fuzzy finder | |||
=== Use case === | |||
The use case here is as follow: | The use case here is as follow: | ||
| Line 8: | Line 19: | ||
* if the Wi-Fi hotspot is unknown, ask for the password, save it, and connect to it | * if the Wi-Fi hotspot is unknown, ask for the password, save it, and connect to it | ||
'''Note:''' if the Wi-Fi hotspot needs to be configured with specific settings (for instance for specific key management settings of for open networks), it is necessary to edit <code>wpa_supplicant.conf</code> manually. The rationale is that I need this so rarely needed, that quickly editing a file with obscure settings outweighs by far the need to make a more complicated shell script to handle such corner case :) | |||
Revision as of 16:35, 16 June 2024
Good news! If you don't want to install third party daemons, gooey GUI things, or bloat just so you can connect to a wireless access point, then don't worry, Linux has all the CLI tools necessary to create a minimal on-demand TUI shell script thing to connect to, and manage these very Wi-Fi connections. The following info is for Debian, however the approach will be the same for other distros, including BSD operating systems that will differ mostly for some of the network commands.
How does it work?
The things that mater
/etc/network/interfaces— network interface configuration for ifup and ifdowniw— show/manipulate wireless devices and their configurationwpa_cli— WPA command line clientwpa_supplicantandwpa_supplicant.conf— Wi-Fi Protected Access client and IEEE 802.1X supplicant and its configuration filefzf— command line fuzzy finder
Use case
The use case here is as follow:
- don't connect to a Wi-Fi hotspot unless I explicitly ask the COMPUTAR to do so
- if I need to connect to a Wi-Fi hotspot, the COMPUTAR should give me a list of the visible ones
- a user-friendly™ interface with fuzzy search should help me tell the COMPUTER which hotspot I want to connect to
- if the Wi-Fi hotspot is already known, connect to it
- if the Wi-Fi hotspot is unknown, ask for the password, save it, and connect to it
Note: if the Wi-Fi hotspot needs to be configured with specific settings (for instance for specific key management settings of for open networks), it is necessary to edit wpa_supplicant.conf manually. The rationale is that I need this so rarely needed, that quickly editing a file with obscure settings outweighs by far the need to make a more complicated shell script to handle such corner case :)