diff options
author | Dan Williams <dcbw@redhat.com> | 2004-10-12 11:15:47 +0000 |
---|---|---|
committer | Dan Williams <dcbw@redhat.com> | 2004-10-12 11:15:47 +0000 |
commit | b6df634a5141f34b5da9353d68e9990f753bfad5 (patch) | |
tree | 09b2bce5fe1631aa79f121279297f6c87ce26bb9 /TODO | |
parent | c195cbf84152f3c02e0c52a5f6d316f31ee1364e (diff) | |
download | NetworkManager-b6df634a5141f34b5da9353d68e9990f753bfad5.tar.gz |
2004-10-12 Dan Williams <dcbw@redhat.com>
* 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
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 5 |
1 files changed, 0 insertions, 5 deletions
@@ -18,11 +18,6 @@ There is currently no logic to gracefully recover from a crashed/killed dbus or 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. -- Support static IP addresses - -We need to support static IP addresses for interfaces. This should be done by parsing the normal /etc/sysconfig/network-scripts/ifcfg-* files. - - - Store Allowed Network WEP keys in gnome-keyring These keys should probably be encrypted, rather than being stored in GConf. |