Find a file
Dan Williams 567b5e3d31 2005-05-03 Dan Williams <dcbw@redhat.com>
* Kill dhcpcd.  We now use "dhcdbd", a dbus daemon that controls dhclient.
	  This means that NetworkManager shouldn't have DHCP issues anymore.  It also
	  means you need dhcdbd, which you can get here (get the latest one):

		http://people.redhat.com/jvdias/dhcdbd/

	  Technically NetworkManager can use any DHCP daemon that uses the same DBUS
	  interface as dhcdbd.

	* Rewrite device activation to facilitate the new DHCP infrastructure and
	  future improvements.  Its now "activation request" based, ie there is a single
	  activation request composed of the device, access point, and other info which
	  follows the entire activation process.  There are 5 stages of the activation
	  process which correspond to:

		1) Device preparation
		2) Device configuration (bring it up, set ESSID/Key/etc)
		3) IP Config Start (fire off DHCP if we're using it)
		4) IP Config Get (grab config from DHCP or static config files)
		5) IP Config Commit (set device's IP address, DNS, etc)

	  Note that there is no longer a "scanning" step, since the access point must
	  be known _before_ activation starts.  If the access point drops out or does
	  not exist for some reason, the entire activation process fails and must be
	  restarted for a different access point or device.

	Patch from Bill Moss:
	* gnome/applet/applet.c
		- Fix type of vpn_failure dialog -> vpn_banner dialog


git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@597 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2005-05-03 20:41:36 +00:00
dispatcher-daemon 2005-03-14 Ray Strode <rstrode@redhat.com> 2005-03-15 05:30:15 +00:00
docs 2004-10-23 Dan Williams <dcbw@redhat.com> 2004-10-23 06:43:01 +00:00
examples/python 2004-11-02 Bryan Clark <clarkbw@cvs.gnome.org> 2004-11-02 08:24:57 +00:00
gnome 2005-05-03 Dan Williams <dcbw@redhat.com> 2005-05-03 20:41:36 +00:00
initscript 2005-01-29 Dan Williams <dcbw@redhat.com> 2005-01-29 23:34:31 +00:00
po 2005-05-02 Francisco Javier F. Serrador <serrador@cvs.gnome.org> 2005-05-02 19:41:00 +00:00
src 2005-05-03 Dan Williams <dcbw@redhat.com> 2005-05-03 20:41:36 +00:00
test 2005-05-03 Dan Williams <dcbw@redhat.com> 2005-05-03 20:41:36 +00:00
utils 2005-03-25 Dan Williams <dcbw@redhat.com> 2005-03-26 03:42:05 +00:00
vpn-daemons 2005-04-27 Dan Williams <dcbw@redhat.com> 2005-04-27 18:05:16 +00:00
.cvsignore 2004-11-01 Colin Walters <walters@verbum.org> 2004-11-02 04:49:29 +00:00
AUTHORS Initial revision 2004-06-24 14:18:37 +00:00
autogen.sh Dan is stupid 2004-10-21 18:22:25 +00:00
ChangeLog 2005-05-03 Dan Williams <dcbw@redhat.com> 2005-05-03 20:41:36 +00:00
configure.in 2005-05-03 Dan Williams <dcbw@redhat.com> 2005-05-03 20:41:36 +00:00
CONTRIBUTING 2004-08-13 Dan Williams <dcbw@redhat.com> 2004-08-13 15:41:31 +00:00
Makefile.am 2005-05-03 Dan Williams <dcbw@redhat.com> 2005-05-03 20:41:36 +00:00
NetworkManager.h 2005-04-27 Dan Williams <dcbw@redhat.com> 2005-04-27 18:05:16 +00:00
NetworkManager.pc.in 2004-09-01 Colin Walters <walters@verbum.org> 2004-09-02 02:30:03 +00:00
NEWS Tue Oct 19 14:19:24 2004 Jonathan Blandford <jrb@redhat.com> 2004-10-19 18:20:04 +00:00
README 2005-02-25 Dan Williams <dcbw@redhat.com> 2005-02-25 21:23:21 +00:00
TODO Remove Non-broadcasting ESSID entry since I've fixed that 2004-10-14 02:23:30 +00:00

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.