On 4/12/2019 5:00 PM, Denis Kenzior wrote:
Or put another way, besides hardware limitations, are there reasons why
you would not want to randomize probe request address when connected?
I was hoping to find your answer using 'git blame'. You might already
have tried that. The wdev->current_bss check was added by the commit below:
commit ad2b26abc157460ca6fac1a53a2bfeade283adfa
Author: Johannes Berg <johannes.berg@xxxxxxxxx>
Date: Thu Jun 12 21:39:05 2014 +0200
cfg80211: allow drivers to support random MAC addresses for scan
Add the necessary feature flags and a scan flag to support using
random MAC addresses for scan while unassociated.
The configuration for this supports an arbitrary MAC address
value and mask, so that any kind of configuration (e.g. fixed
OUI or full 46-bit random) can be requested. Full 46-bit random
is the default when no other configuration is passed.
Also add a small helper function to use the addr/mask correctly.
Signed-off-by: Johannes Berg <johannes.berg@xxxxxxxxx>
Unfortunately it does not answer your question. My memory is lacking
quite a bit but I think at the time it was not considered useful to have
random mac address for scan while being associated. Your permanent mac
address would be flying around anyway.
Regards,
Arend
