nRF7002 Callbacks returning wrong interface

[esmart-engineering]

I'm using an STA+AP configuration as well as monitor mode with a custom nrf7002 driver, which currently is working in a basic sense. I have however ran into issues regarding the nrfxlib callbacks that I've built workarounds for but I'm not sure are being addressed yet. They mostly revolve around the callbacks returning the default interface, even though the commands that triggered them were on a different interface. So far I've ran into the issue on `rx_frm_callback_fn`, `chnl_get_callbk_fn`, and `tx_pwr_get_callbk_fn`. 

For `rx_frm_callback_fn`, I'll have monitor mode configured on a second interface, but when packets come in from the callback, they always return the default interface, even though the default interface is in a down state.

For both `chnl_get_callback_fn` and `tx_pwr_get_callbk_fn`, I'm using the get channel and get tx power api functions for the second interface, but the callback will always return the default interface.

While I've gotten around the issue on these callbacks, there may be other ones that have a similar issue.

[Simonr]

Hi

Sorry I didn't get back to you on this. Did you get anywhere or are you still awaiting for my feedback? If so I'll take a look.

To SpeedCrash100 : Just checking. Are you also working with an nRF7002 or some other Wi-Fi module? It doesn't seem directly related to this ticket from what I can see, so please create a ticket of your own if you need technical support.

Best regards,

Simon

[SpeedCrash100]

I am working with same nrf7002 module and just curious about info that ticket creator states he managed to start STA+AP mode while I am seeing some strange behaviour.

In regards of the ticket, I can add that in addition to `rx_frm_callback_fn`, `chnl_get_callbk_fn`, `tx_pwr_get_callbk_fn`, `set_if_callbk_fn` and `cookie_rsp_callbk_fn` are also called with default interface only from what I found.