1. 28 Feb, 2012 3 commits
  2. 27 Feb, 2012 18 commits
  3. 26 Feb, 2012 6 commits
  4. 24 Feb, 2012 4 commits
  5. 23 Feb, 2012 2 commits
  6. 22 Feb, 2012 2 commits
  7. 21 Feb, 2012 1 commit
  8. 20 Feb, 2012 4 commits
    • Dan Williams's avatar
      wifi: ensure APs remain in scan list when supplicant updates them · 92412357
      Dan Williams authored
      The port to the new supplicant D-Bus API for NM 0.9 had one unfinished
      piece, which was to remove old APs from the scan list when the
      supplicant returned no scan results or there was a scan error.  In
      this case, the removal code would not be called.  This wasn't much
      of a problem until 836f7d17 which
      began removing APs from the scan list correctly in this case.
      
      This uncovered a bug in NM's wpa_supplicant management code, which
      was that NM only updates its internal AP object 'last seen' timestamp
      when the AP is reported by the supplicant as a completely new BSS
      (in merge_scanned_ap()).  But the new supplicant D-Bus interface
      only reports the BSS as "new" when the supplicant doesn't know about
      the BSS, either because it is a new BSS or because it's been removed
      from the supplicant's scan list at some point in the past.
      
      Thus for BSSes that are consistently kept in the supplicant's scan
      list, because the wifi driver is actually doing its job and reporting
      them consistently in scan results, NM would not be updating the
      'last seen' value for the corresponding NM AP objects.  Due to
      836f7d17 this would cause APs that
      should be kept to be removed from the NM scan list.
      
      To fix this, have the NMAccessPoint object track which supplicant
      dbus object it came from, and have NMSupplicantInterface listen for
      PropertyChanged signals for those APs the supplicant knows about.
      When something changes (like signal strength as the result of updated
      scan results) update the AP's 'last seen' timestamp since it clearly
      still exists in the scan list.  This way we update the timestamp both
      when the supplicant finds a new AP and when it updates the properties
      of existing APs.
      92412357
    • Dan Winship's avatar
      libnm-glib: fix some property-handling warnings · 2c6bade5
      Dan Winship authored
      Fix handle_object_array_property() to deal with receiving an empty
      list correctly (rather than warning and leaving the property with its
      previous value still set).
      
      Also, add two more untracked properties that shouldn't be warned about
      (NMDevice:device-type and NMActiveConnection:vpn, both of which are
      only used at construct time).
      2c6bade5
    • Jiří Klimeš's avatar
      7b9c728b
    • Jiří Klimeš's avatar
      netlink: fix build on libnl1/2 · 261d760a
      Jiří Klimeš authored
      261d760a