linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Multiple-BSSID issues with hostapd
@ 2014-11-28  9:27 Arend van Spriel
  2014-12-04 12:03 ` Rafał Miłecki
  2015-03-01 17:12 ` Jouni Malinen
  0 siblings, 2 replies; 5+ messages in thread
From: Arend van Spriel @ 2014-11-28  9:27 UTC (permalink / raw)
  To: Jouni Malinen; +Cc: hostap@lists.shmoo.com, linux-wireless@vger.kernel.org

Hi Jouni,

For the brcmfmac we started working on Multiple-BSSID support and came
across some issues with hostapd that are listed listed below.

BSS1 setup on netdev wlan0
BSS2 setup on netdev wlan0_0

* get_station() done on wrong netdev

observed:
Upon association of STA1 with BSS2 (wlan0_0) a get_station() is done for
STA1 with wlan0 as netdev.
expected:
get_station() for STA1 with wlan0_0 as netdev. We verified that wlan0_0
ifindex was used in NL80211_CMD_NEW_STATION event.

* cleanup of wlan0_0 not done upon terminating hostapd

observed:
Upon terminating hostapd, only change interface from AP->STA is received
for wlan0_0 and wlan0. The stop_ap is only done for BSS1. So ending up
with additional netdev, ie. wlan0_0.
expected:
following sequence seems more appropriate:
stop_ap() for BSS2
if_remove() for BSS2
stop_ap() for BSS1
if_change() AP->STA for BSS1

Do you think it makes sense to correct these scenarios according the
described expected behaviour? Maybe the behaviour is only expected by me
and there is a good reason for the current behaviour.

Regards,
Arend



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2015-03-01 17:30 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-28  9:27 Multiple-BSSID issues with hostapd Arend van Spriel
2014-12-04 12:03 ` Rafał Miłecki
2014-12-04 19:04   ` Arend van Spriel
2015-03-01 17:12 ` Jouni Malinen
2015-03-01 17:30   ` Rafał Miłecki

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).