<Ajay.Kathat@xxxxxxxxxxxxx> writes: > On 10/05/22 01:14, Johannes Berg wrote: >> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe >> >> On Mon, 2022-05-09 at 13:49 +0000, Ajay.Kathat@xxxxxxxxxxxxx wrote: >>> As I understand, in WILC "ieee80211_ptr" is used for the station/AP >>> interface but not to configure the monitor interface which gets >>> additionally added in AP mode. In AP mode, for an interface( wlan0 ), an >>> additional monitor interface( mon.wlan0 ) gets created. A netdevice is >>> register for monitor interface(mon.wlan0) to transmit/receive frames >>> from/to hostapd. That interface doesn't explicitly set up >>> 'ieee80211_ptr' because the original interface(wlan0) uses it, so using >>> "cfg80211_register/unregister" API's for mon.wlan0 interfaces fails. >> Btw, this probably should just be removed in favour of using the nl80211 >> based APIs for hostapd ... >> >> But I think as a quick bugfix goes this is fine, but it'd be better to >> remove this and either allow hostapd to create the interface with the >> proper ieee80211_ptr, or to just use the nl80211-based TX/RX. > > > Thanks Johannes. Yes, this patch would help to make the AP mode work. > I will check on using nl80211 based APIs for hostapd but might take some > time to change. Ok, I'll take this as a quick fix but please switch to using proper interfaces. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
