commit | 8f81e2a3e3e25345d04ab0b93d09e61cb73153aa | [log] [tgz] |
---|---|---|
author | Christopher Wiley <wiley@chromium.org> | Wed Oct 17 16:51:32 2012 -0700 |
committer | Gerrit <chrome-bot@google.com> | Thu Oct 18 11:21:55 2012 -0700 |
tree | 52c747cddbb7160bb1d31313d1d29535fc4d89b3 | |
parent | 4c2aa3341abf5b3774b874cd0067e787ef2cb60d [diff] |
shill: Don't restart L3 configuration on rekeying events We've seen logs where an AP triggered 4-5 rekeying events after association, but before we got an IP. This caused shill to restart dhcpcd for each of those rekeying events, which further delays getting an IP. Stop this by only triggering L3 configuration on the first transition to a completed state according to wpa_supplicant. BUG=chromium-os:35418 TEST=Unit tests Change-Id: Ie849ebd8a1962183a8d6a838b9d8e49e432fd5ba Reviewed-on: https://gerrit.chromium.org/gerrit/35887 Tested-by: Christopher Wiley <wiley@chromium.org> Reviewed-by: Paul Stewart <pstew@chromium.org> Reviewed-by: Darin Petkov <petkov@chromium.org> Commit-Ready: Christopher Wiley <wiley@chromium.org>