Closed EdTheBearded closed 2 months ago
I wanted to hear you opinion on this. Ok, this is something we already have to to whenever we're trying to enable AP on a device, but for this specific connection issue, there might be a possibility of fix. This is one workaround that was also shared in the issue, so it's not like the issue is a blocker anymore....
I don't really like this and would rather wait to see if we get a proper fix on this. What do you guys think?
@EdTheBearded, the BSP team accepts the issue as a driver bug.
I would suggest we accept this solution of unmanaging UAP in the short-term, and then revert this once the BSP bug is fixed.
Doing this as a short term solution seems sensible to me, as long as we keep a reminder for undoing it later once the driver problem is solved.
Doing this as a short term solution seems sensible to me, as long as we keep a reminder for undoing it later once the driver problem is solved.
Maybe we could have a ticket on our backlog to remove this. @leograba?
Since NetworkManager can't play nice with uap interfaces, we're marking them as unmanaged, so this won't affect other connections.