We used to bring down the interface on network disconnect
which would in turn clean up all the IP addresses.
The interface bringup/shutdown is now handled by wpa_supplicant.
Add netd interface for clearing all IP addresses
Bug: 4676254
Change-Id: I7e24c0ab2e4a412b8d61e9c33ce028966913aaf6
Change I242cda97 introduced a regression where network state
was being modified on any supplicant state change.
Revert the old behavior of only changeing network detailed state
based on supplicant state change in a disconnected state
Bug: 4690073
Change-Id: I927cc5fa36b862cc54661b033939f543cd15d31f
If you do it before you have a race condition and some apps will
manage to reconnect on the dieing network before it goes and then
get no notification when it goes.
bug: 3408025
Change-Id: I5386ff313c759b3f687bc38731454ab43dbe76b8
The driver start and stop events will be removed as they are now
redundant (and incorrect)
Move to using supplicant INTERFACE_DISABLED indication for deciding
if driver has started or stopped
When driver start is given, the supplicant will first switch to
INTERFACE_DISABLED state and then out of it to start connecting.
We should use this indication to find out driver has started
When driver stop is given, the supplicant will just switch to
INTERFACE_DISABLED state and this indicates driver has stopped
Bug: 4550125
Change-Id: I242cda97951a733c8707c8d99cdfcc9a33b75c2d
Latest supplicant introduces the INTERFACE_DISABLED state. This
is entered when the interface is brought down (which is effectively
done by us and tracked already through the driver stop operation)
Also, added is a state for tracking authentication when supplicant acts as
the SME
Change-Id: I76090068d0ebba6df76f16707da559fcbd7512c5
Add DhcpStateMachine for interation with dhcpcd
- Supports wakeup and renewal on dhcp
- Supports multiple controllers to use the state machine
simultaneously
- Optionally, a controller can request a notification prior
to DHCP request/renewal being sent
Change-Id: I5324814b19ff19863aa6fa89f1e3f0a202930c98
- Supports wakeup and renewal on dhcp
- Supports multiple controllers to use the state machine
simultaneously
- Optionally, a controller can request a notification prior
to DHCP request/renewal being sent
Change-Id: I3a9d7e6a02ff26be3a86ddca6964683ad3c28f93
When a user explicitly disables wifi, wait on the supplicant shut down until after
all child states have handled exit - this avoids time outs due to communicating with
supplicant after breaking the socket connection
Bug: 4052161
Change-Id: Iec5bb3e14a2df4a8a12de8bb81d9c10aeb992ad4
Also, allow scan interval for framework and supplicant
to be configured at build time or run time
Bug: 4144882
Change-Id: I877f4bcc872597b44d3f4da85cf2bc0f16e09444
android.permission.WAKE_LOCK permission is required to use WakeLock or
WifiLock, but nowhere is it mentioned that you must declare that
permission to use it.
Change-Id: Ib5f5294d37e39169fe5678743f380d95c4e5a842
We should avoid network id set unless the access point is associating.
Also, we should reset network connection state before sending
out network change broadcast.
Finally, we should reset connect mode settings when we disconnect from
an access point
Bug: 3424635
Change-Id: I41db5399810218abd6a77155166db5a9b1dbd22c
Generates InetAddresses without risking an accidental dns lookup. For use with supposedly
numeric-only ip address strings.
Change-Id: I694f3976ce1c6382854706f6557ea88a289add3a
If PNO is set after the device is disconnected, the scan
alarm should be cleared to prevent both PNO and alarm
being active at the same time
Bug: 3495698
Change-Id: Id48c87fef68a34a05799e6b82de4088e0573009f
Background scanning (preferred network offload) allows us the
host to sleep while the dongle monitors the presence of any
preferred networks. This allows us for significant power savings
since the system does not have to wake up often to initiate
a scan
Bug: 3453021
Change-Id: I73dcf4e1c9ab4de280c40b6df6147a74ac003123
