aboutsummaryrefslogtreecommitdiffstats
path: root/wpadebug/project.properties
diff options
context:
space:
mode:
authorPurushottam Kushwaha <pkushwah@codeaurora.org>2019-11-14 09:15:10 (GMT)
committerJouni Malinen <j@w1.fi>2019-11-17 19:04:38 (GMT)
commit783a99b73d243abd1f7ae58fe558fe3099fbed44 (patch)
treeca687614895eca324131ae6353e8a84809050b2f /wpadebug/project.properties
parentf3c077929f0d978f58af073ec94fd5ebbceb55c4 (diff)
downloadhostap-783a99b73d243abd1f7ae58fe558fe3099fbed44.zip
hostap-783a99b73d243abd1f7ae58fe558fe3099fbed44.tar.gz
hostap-783a99b73d243abd1f7ae58fe558fe3099fbed44.tar.bz2
HS2.0: Skip check for roaming_consortium for NAI realm query
Previously ANQP fetch considered NAI realm query only when cred block did not specify roaming_consortium to optimize ANQP operations (NAI realm list can have a very long value). In certain cases, both NAI realm and roaming_consortium are configured in credential block and this resulted in ANQP fetch for NAI realm not being initiated. That could result in not being able to select the highest priority available credential/network. Remove roaming_consortium check for NAI realm query inclusion in ANQP request so that we will request NAI realm information whenever it can result in matching additional networks. This makes the ANQP queries more costly in some cases, but the additional information is needed for correct behavior in network selection. Signed-off-by: Jouni Malinen <jouni@codeaurora.org>
Diffstat (limited to 'wpadebug/project.properties')
0 files changed, 0 insertions, 0 deletions