tested with net.ifnames=0:
WiPi adapter: no longer I see "unavailable" in all ~25 cold boots.
TP-LINK TL-WN725N: no longer see "unavailable", but it's 2 times from ~25 attems becomes "disconnected", as it simply does not "see" any WiFi networks which is not correct. Rescan does not help. Replugging device make it work again.
So I guess TP-LINK has additional issues - sometimes it does not "boots up" correctly and does not see any networks.
But in the end, net.ifnames=0 workaround helps to avoid "unavailable" state at least.
I guess that's kinda proves NetworkManager issue due to device renames? Rare race condition?
WiPi adapter: no longer I see "unavailable" in all ~25 cold boots.
TP-LINK TL-WN725N: no longer see "unavailable", but it's 2 times from ~25 attems becomes "disconnected", as it simply does not "see" any WiFi networks which is not correct. Rescan does not help. Replugging device make it work again.
So I guess TP-LINK has additional issues - sometimes it does not "boots up" correctly and does not see any networks.
But in the end, net.ifnames=0 workaround helps to avoid "unavailable" state at least.
I guess that's kinda proves NetworkManager issue due to device renames? Rare race condition?
Statistics: Posted by Talkless — 2024-12-17 14:46