mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-01-03 12:50:17 +01:00
read-only mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager
4de66efbd4
* Remove 'debug' extern global from all files since we now use syslog() * src/NetworkManager.[ch] - Break out routine that get the net.interface property from HAL, removing that logic from nm_create_device_and_add_to_list() - (nm_create_device_and_add_to_list): make this a bit more general so it doesn't do the talking to HAL. Also add arguments to facilitate the create of test devices. - (nm_data_mark_state_changed): rename from nm_data_set_state_modified() - (nm_data_new, main, nm_print_usage): add new argument "--enable-test-devices" which makes NetworkManager listen for dbus commands to create test devices, which have no backing hardware. Use when you're on a plane for example, and/or forgot your wireless card at home. Test devices _cannot_ be created unless NM is started with --enable-test-devices. * src/NetworkManagerDbus.[ch] - New "getLinkActive" method for devices - New "setLinkActive" method for devices (only works on test devices) - New "createTestDevice" method on NetworkManager object to create a test device of a specified type (ie wired, wireless). UDI is created from scratch, as is the interface name. Only works when NM is started with --enable-test-devices switch. - New "removeTestDevice" method on NetworkManager object which removes a test device. Only works when NM is started with --enable-test-devices * src/NetworkManagerDevice.[ch] - Logic to facilitate test devices. Add variables to NMDevice struct to indicate whether a device is a test device or not, and what its link status is. - Deal with test devices in most functions. For those that work directly on hardware special-case test devices. - (nm_device_new): don't create a test device if test devices weren't enabled on the command-line. - (nm_device_update_link_active): split out logic for wired and wireless device link checking to separate functions to facilitate test device link checking. - (nm_device_set_enc_key): Since some drivers for wireless cards are daft and don't make a distinction between System Authentication and Encryption (namely Cisco aironet), we use Open System auth when setting a WEP key on the card. We don't deal with Shared Key auth yet. - (nm_device_activation_worker): split the activation cancel check logic out into a separate routine nm_device_activation_cancel_if_needed() - (nm_device_activation_signal_cancel): rename from nm_device_activation_cancel() - (nm_device_fake_ap_list): Test wireless devices obviously cannot scan, so create a list of fake access points that they can "see" - (nm_device_is_test_device): return whether or not a device is a test device * src/NetworkManagerPolicy.c - (nm_policy_get_best_device): attempt to deal with wireless network selection, previously if you "locked"/forced NM to use a wireless device but then selected a wireless network for NM to use, it would switch to a wired device. So, if the active device is wireless and it has a "forced" best AP, use it if the "forced" best AP is still valid - (nm_state_modification_monitor): deal with NULL best devices, for example there were no usable network devices, or the last one was removed * src/backends/NetworkManager*.c - Deal with test devices, mostly just return success for operations like getting a DHCP address * test/nmtestdevices.c - Test tool to create/remove/link-switch test devices git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@112 4912f4e0-d625-0410-9fb7-b9a5a253dbdc |
||
|---|---|---|
| dispatcher-daemon | ||
| examples/python | ||
| info-daemon | ||
| initscript | ||
| panel-applet | ||
| po | ||
| src | ||
| test | ||
| .cvsignore | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.in | ||
| CONTRIBUTING | ||
| Makefile.am | ||
| 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.