mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-02-25 03:40:37 +01:00
read-only mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager
Tighten up handling of wireless devices that don't support wireless scanning (ie, Orinoco). Due to restructuring of code, these devices hadn't been doing pseudo-scanning for a while either and would just spin waiting for an access point. They are now manual devices where the user must choose the access point from the menu every time. All "allowed" access points are listed in the applet's menu regardless of whether or not they can be seen by the card, since it can't scan anyway. * src/NetworkManager.c - (nm_wireless_link_state_handle): new function, but only update the "best" ap for non-scanning devices when its not activating, and when no device is being forced on the card - (nm_link_state_monitor): split wireless link state handling out into separate function * src/NetworkManagerDevice.c - (nm_device_copy_allowed_to_dev_list): new function - (nm_device_new): populate non-scanning cards' AP lists with access points from the "allowed" list - (nm_device_new): don't start a scanning timeout for devices that can't scan - (nm_device_activation_schedule_finish): new parameter, should be the AP that failed to be connected to, pass it on to the activation finish function in NetworkManagerPolicy.c - (nm_device_activate_wireless): don't ever try to get a new AP for non-scanning devices, just fail. The user must choose a new access point manually. - (nm_device_activate): grab the AP that failed connection and pass it on - (nm_device_update_best_ap): Clear the best AP if we don't have a link to it, user must manually choose a new one - (nm_device_do_pseudo_scan): remove function - (nm_device_wireless_process_scan_results): remove bits for non- scanning cards since they never get here - (nm_device_wireless_scan): remove bits for non-scanning devices, and fake the scan list for test devices a bit earlier * src/NetworkManagerPolicy.c - (nm_policy_activation_finish): use the failed_ap that we get passed rather than getting the best_ap from the card, which may have changed since we were scheduled - (nm_policy_allowed_ap_list_update): for non-scanning devices, update their scan list directly from the allowed list when we get updates to the allowed list from NetworkManagerInfo * src/NetworkManagerPolicy.h - New member for failed access point in NMActivationResult ------------------------------------- Driver Notification patch: notifies the user when their driver sucks. Gives them the option to ignore further insertions of the card that has the sucky driver. * NetworkManager.h - Remove the SEMI_SUPPORTED member from the NMDriverSupportLevel enum and replace it with NO_CARRIER_DETECT and NO_WIRELESS_SCAN * panel-applet/NMWirelessApplet.[ch] - Merge essid.glade -> wireless-applet.glade - Implement the "Your driver sucks" notification dialog * panel-applet/NMWirelessAppletDbus.c - Change stuff from getSupportsCarrierDetect->getDriverSupportLevel - Grab hardware address for each device from NM too - Check whether the driver for each device sucks or not whenever a new device is noticed * panel-applet/NMWirelessAppletOtherNetworkDialog.c - Deal with stuff being in wireless-applet.glade now rather than essid.glade * src/NetworkManager.c - Fix a double-unref on device removal * src/NetworkManagerUtils.c - Set appropriate driver support level on a device that doesn't support scanning or carrier detection * src/nm-dbus-device.c - New "getHWAddress" dbus method on devices - getSupportsCarrierDetect -> getDriverSupportLevel git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@534 4912f4e0-d625-0410-9fb7-b9a5a253dbdc |
||
|---|---|---|
| dhcpcd | ||
| dispatcher-daemon | ||
| docs | ||
| examples/python | ||
| info-daemon | ||
| initscript | ||
| libnm_glib | ||
| named | ||
| panel-applet | ||
| po | ||
| src | ||
| test | ||
| utils | ||
| .cvsignore | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.in | ||
| CONTRIBUTING | ||
| Makefile.am | ||
| NetworkManager.h | ||
| NetworkManager.pc.in | ||
| NEWS | ||
| README | ||
| TODO | ||
THEORY OF OPERATION: NetworkManager attempts to keep an active network connection available at all times. It is intended only for the desktop use-case, and is not intended for usage on servers. At this time, it does not support static IP addresses on network interfaces, and requires DHCP to be used instead. The point of NetworkManager is to make networking configuration and setup as painless and automatic as possible. If using DHCP, NetworkManager is _intended_ to replace default routes, obtain IP addresses from a DHCP server, and change nameservers whenever it sees fit. If you have special needs, we'd like to hear about them, but understand that NetworkManager is not intended to serve the needs of all users. From a list of all adapters currently installed on the system, NetworkManager will first try a wired and then a wireless adapter. Wireless adapters that support wireless scanning are preferred over ones that cannot. NetworkManager does not try to keep a connection up as long as possible, meaning that plugging into a wired network will switch the connection to the wired network away from the wireless one. For wireless networking support, NetworkManager keeps two lists of wireless networks: a Trusted list, and a Preferred list. The Trusted list contains networks the user specifically adds to it, while the preferred list contains networks the user forces NetworkManager to connect to. For example, while the company's wireless network and WEP/WPA key would be preloaded into the Trusted Networks list, if the user wished to use the wireless network in a Starbucks, the user would explicitly tell NetworkManager to associate with that network. NetworkManager does not try to use _any_ available network in the area (a possible security risk), but will associate with any Trusted Network first, and Preferred Networks later. Preferred Networks are ones the user has explicitly made NetworkManager associate with at some previous time. So if the user walks into a Starbucks and explicitly asks NetworkManager to associate with that Starbucks network, NetworkManager will remember the Starbucks network information from that point on. Upon returning to that Starbucks, NetworkManager will attempt to associate _automatically_ with the Starbucks network since it is now in the Preferred Networks list. The point of this is to ensure that only the user can determine which wireless networks to associate with, and that the user is aware which networks are security risks and which are not. STRUCTURE: NetworkManager runs as a root-user system level daemon, since it must manipulate hardware directly. It communicates over DBUS with at least one other daemon, the info-daemon. Since Trusted and Preferred Networks are user-specific, there must be some mechanism of getting this information per-user. NetworkManager cannot store that information as it is user-specific, and therefore communicates over DBUS to the info-daemon which provides those lists. NetworkManager also provides an API over DBUS for any DBUS-aware application to determine the current state of the network, including available wireless networks the computer is aware of and specific details about those networks. This API also provides the means for forcing NetworkManager to associate with a specific wireless network. Use of DBUS allows separation of NetworkManager, which requires no user-interface, and the parts of the user interface which might be desktop environment specific. The info-daemon provides a DBUS service called NetworkManagerInfo, which should provide to NetworkManager the Trusted and Preferred Networks lists upon request. It also should be able to display a dialog to retrieve a WEP/WPA key or passphrase from the user when NetworkManager requests it. The GNOME version of NetworkManagerInfo, for example, stores Trusted and Preferred Networks in GConf, and proxies that information to NetworkManager upon request. Other UI bits might include a user-visible application (for example, the included GNOME Panel applet) providing a list of available wireless networks to the user and a means to manually select one to associate with.