more frequent associated MAC randomization

[thestinger]

It would be nice to leverage wpa_supplicant's associated MAC randomization support rather than only using the pre-association MAC randomization paired with randomization when interfaces are brought up. Users usually between networks without ever turning off WiFi.

[randomice42]

I have read related #147 too and would like to leave a couple of pointers:

• wpa_supplicant defaults to MAC based UUID https://android.googlesource.com/platform/external/wpa_supplicant_8/+/0716c12e57090ce9904fb5948da1285fc36c1fe4/wpa_supplicant/wpa_supplicant.conf#158 (relevant rfc: [https://www.ietf.org/rfc/rfc4122.txt]).
• first sentence of [http://tools.ietf.org/html/rfc4361#section-6.1]

Imagine user associated to home AP, walks out of distance and returns into distance. This is the most regular case of wifi-usage. If the MAC got changed in between, any fast-reauth for the existing dhcp-lease is bound to fail.
In my case (using CM currently): I have a trigger to disable wifi when leaving the home AP coverage, i.e. I have to manually activate it when I get into range again. I think best you can do is offer randomization support for these cases (re-activating wifi again will randomize the MAC, accepting some dhcp authentication delays for networks with existing leases).
Is that the current state of what coperheados does ("when interfaces are brought up")?

[randomice42]

I have read related #147 too and would like to leave a couple of pointers:

• wpa_supplicant defaults to MAC based UUID https://android.googlesource.com/platform/external/wpa_supplicant_8/+/0716c12e57090ce9904fb5948da1285fc36c1fe4/wpa_supplicant/wpa_supplicant.conf#158 (relevant rfc: [https://www.ietf.org/rfc/rfc4122.txt]).
• first sentence of [http://tools.ietf.org/html/rfc4361#section-6.1]

Imagine user associated to home AP, walks out of distance and returns into distance. This is the most regular case of wifi-usage. If the MAC got changed in between, any fast-reauth for the existing dhcp-lease is bound to fail.
In my case (using CM currently): I have a trigger to disable wifi when leaving the home AP coverage, i.e. I have to manually activate it when I get into range again. I think best you can do is offer randomization support for these cases (re-activating wifi again will randomize the MAC, accepting some dhcp authentication delays for networks with existing leases).
Is that the current state of what coperheados does ("when interfaces are brought up")?

[thestinger]

Not currently applicable.

[thestinger]

Not currently applicable.