Network Configurator sits in the notification area, it's icon representing the overall network state. When attempting to negotiate an address you get a nice animation. A notification bubble is also shown per interface state change. A drop down menu shows available Access Points, which one your connected to, if they're encrypted or not and their overall quality. You can click on one to configure the PSK or WEP key 0 for it.
Here is a screenshot showing the SSID list by clicking on the wireless icon.
The connected SSID is shown first in bold with a green tick. Other SSID's are then shown in a lexical order with icons to show security and strength.
Network Configurator is built on top of libdhcpcd (a C library, currently statically built into all the front ends) to allow the ease of writing a different front end with minimal backend work required. Once I'm happy with the interface, it will probably be available dynamically linked for others to use. Contact me if you want this sooner!
A LXDE Panel plugin is available from the RaspberryPi LXPanel repository
A Curses interface is also supplied, but it's functionality is very basic right now.
dhcpcd-ui is released under the 2 clause BSD license.
dhcpcd-ui bundles icons from The Tango Project (BSD license), Elementary (GPLv3), GNOME (GPLv2) and KDE Oxygen (LGPLv3). These are used if your icon theme of choice does not supply these standardised icons.
dhcpcd-online has no build requirements other than a POSIX C platform.
dhcpcd-curses requires a curses library - most systems ship one.
You will require the following software to build and run dhcpcd-gtk
You optionally require the following notification daemon for use with dhcpcd-gtk
You will require the following software to build and run dhcpcd-qt
wpa_supplicant is required configure connections to Wireless Access Points.
You need to configure wpa_supplicant so it allows config updates over it's control socket.
You do do this by including these two lines at the top of your
# If wheel group does not exist, use root instead ctrl_interface=/var/run/wpa_supplicant GROUP=wheel update_config=1
Neither dhcpcd nor dhcpcd-ui will start wpa_supplicant for you (it's not their job to so don't bother asking), so you'll need to instruct your init system to start it at boot time. For this to work for hot plugged interfaces, such as USB sticks, you'll need to enable interface matching using the -M option (note this reqires wpa_supplicant-2.6 or newer and CONFIG_MATCH_IFACE enabled during it's build) on the command line. I start it like so:
wpa_supplicant -B -M -c /etc/wpa_supplicant.conf
Currently there is just the dhcpcd-discuss mailing list, which is powered by mlmmj. One interacts with mlmmj via email.
To subscribe to the list, send an empty email to email@example.com
Once subscribed to the list, you can post to it by sending an email to firstname.lastname@example.org
To unsubscribe from the list, send an empty email to email@example.com
You can learn more about the capabilities of mlmmj by sending an empty mail to firstname.lastname@example.org
You can also read the dhcpcd-discuss archive