mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager
synced 2024-07-21 18:24:49 +00:00
b6df634a51
* TODO - Remove bit about static IP address support * src/NetworkManagerUtils.c - (nm_spawn_process): Add some error reporting * src/NetworkManagerDevice.c - (nm_device_activation_configure_ip): hook up to the static config routines in the backends * src/backends/NetworkManagerRedHat.c - (nm_system_device_update_config_info): use shvar.c routines to parse the config file iformation, not our own - (nm_system_device_setup_static_ip4_config): new function, based heavily on 'ifup' script and 'ipcalc' tool code. Set up a device with a static IP address and gateway * src/backends/shvar.[ch] - Parser (filched from initscripts package) for ifcfg-* files * src/backends/NetworkManagerSystem.h src/backends/NetworkManagerGentoo.c src/backends/NetworkManagerDebian.c src/backends/NetworkManagerSlackware.c - Stub nm_system_device_update_config_info() and nm_system_device_setup_static_ip4_config() git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@212 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
30 lines
1.8 KiB
Plaintext
30 lines
1.8 KiB
Plaintext
TODO items for NetworkManager
|
|
-----------------------------
|
|
|
|
Any of these items are of course fair game for anyone, patches are greatly welcome. It also serves as a "what still needs to be done" list.
|
|
|
|
- Access Point link checking thresholds
|
|
|
|
Wireless link checking could be enhanced to check the signal strength of an access point and switch if the current access point a wireless card is associated with has dropped below say, 20%.
|
|
|
|
|
|
- Gracefully recover from dbus and hal dropouts
|
|
|
|
There is currently no logic to gracefully recover from a crashed/killed dbus or hal. There are dbus functions for notification when services come up and go away which could be used here. Remeber that when dbus dies, hal also dies at the moment.
|
|
|
|
|
|
- Deal with blank ESSIDs
|
|
|
|
Access points can be set not to broadcast their ESSIDs, which the client must know. These appear as blank ESSIDs to cards doing wireless scanning, even though the rest of the AP's information is known (channel, rate, etc). There has to be a way to deal with this as many companies do not broadcast ESSIDs for security measures. Workarounds for this practice could include brute-forcing the Allowed Networks list if no suitable wireless network is found to begin with. Obviously, there would be no way to detect if a WEP key was wrong, because unless the ESSID and WEP key are both correct, we cannot associate with the access point to see if we have a link. Code exists to do this for wireless cards that do not support wireless scanning, and this code could be adapted.
|
|
|
|
|
|
- Store Allowed Network WEP keys in gnome-keyring
|
|
|
|
These keys should probably be encrypted, rather than being stored in GConf.
|
|
|
|
|
|
- Support 40/64 bit passphrases
|
|
|
|
Allow user to enter passphrases and convert them to 40/64 bit WEP keys on the fly. Unfortunately, the algorithm for 40/64 bit passphrases is kind of messy.
|
|
|