1. 07 Aug, 2006 1 commit
  2. 01 Jan, 2006 1 commit
  3. 31 Dec, 2005 1 commit
    • Dan Williams's avatar
      2005-12-31 Dan Williams <dcbw@redhat.com> · 4ed4b491
      Dan Williams authored
      	* refactor NMDevice into a GObject-based framework with separate
      		objects for wired and wireless.  The following files are no
      		longer used but should stick around for a bit so we don't
      		loose code through the cracks:
      			NetworkManagerDevice.c
      			NetworkManagerDevice.h
      			NetworkManagerWireless.c
      			NetworkManagerWireless.h
      
      	The intent here is to allow each device type to manage its own
      	connection & activation life-cycle, ie to allow wireless devices
      	to interface with wpa_supplicant, etc.  There's a fair bit of
      	encapsulation breakage right now that should gradually get pulled
      	back into each device, along with things like periodic property
      	updates and link probing.
      
      
      git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1244 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
      4ed4b491
  4. 07 Dec, 2005 1 commit
  5. 04 Sep, 2005 1 commit
  6. 06 May, 2005 1 commit
  7. 03 May, 2005 1 commit
    • Dan Williams's avatar
      2005-05-03 Dan Williams <dcbw@redhat.com> · 567b5e3d
      Dan Williams authored
      	* 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
      567b5e3d