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.

[Elfving]

Hello,

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.

Hehe supporting people creating custom drivers isn't easy. Any particular reason why you didn't want to use the default ones?

Regards,

Elfving

[esmart-engineering]

It's a linux driver and the one Nordic provides has limited functionality. For these particular issues I understand that I most likely won't get a fix. Its mostly bringing attention to the issue in case someone else is running into the problem and for Nordic to at least have the issue on their radar.