b3921db426
When ACS is configured in multiple BSS case, sometimes a virtual AP interface does not come up as the channel context information between different BSSs of the same band does not match. Same behavior is observed in case of multiple band/hardware under a single wiphy, when we bring up multiple virtual interface in various bands simultaneously and the kernel maps a random channel as it has more than one channel context, e.g., say a 2.4 GHz channel to a 5 GHz virtual AP interface when the start AP command is sent. This is because the frequency information is not present in the command. Add the frequency information into the start AP netlink command so that the kernel maps the appropriate channel context by parsing it instead of using a previous set channel information. Signed-off-by: Harshitha Prem <quic_hprem@quicinc.com> |
||
---|---|---|
.. | ||
ap | ||
common | ||
crypto | ||
drivers | ||
eap_common | ||
eap_peer | ||
eap_server | ||
eapol_auth | ||
eapol_supp | ||
fst | ||
l2_packet | ||
p2p | ||
pae | ||
pasn | ||
radius | ||
rsn_supp | ||
tls | ||
utils | ||
wps | ||
build.rules | ||
lib.rules | ||
Makefile | ||
objs.mk |