Hold on there: WPA3 connections fail after 11 hours<p><a href="https://rachelbythebay.com/w/2024/01/24/fail/" rel="nofollow">https://rachelbythebay.com/w/2024/01/24/fail/</a><p>"My conclusion: this entire ecosystem is deeply cursed."
<i>iwd</i> is slick as hell. I use it with <i>systemd-networkd</i> and it's so smooth.<p>There's fantastic support for all the weird ways to connect: wifi-p2p/direct, ad-hoc, Device Provisioning Protocol (DPP/Easy Connect), Shared Code Device Provisioning (Pkex). Good debug tools like initiating roam to.<p>It's nice that iwd does less; it just gets wireless connected. NetworkManager does so much, and somehow it's never sparked joy. I've spent time on connman and that was fine enough. I've managed my own wpa-supplicant configs, which worked but was clunky. Iwd has really been a joy to work with for me, so clear & direct, with easy config files & a very pleasant little tui/cli.<p>Systemd-networkd has also been quite simple & direct for me, very configurable. But that's another story.
There is a followup post saying that the module is disconnecting from the network after 11hrs, the cause seems a bit murky (I'd say probably a firmware issue but haven't looked in to it at all)<p><a href="https://rachelbythebay.com/w/2024/01/24/fail/" rel="nofollow">https://rachelbythebay.com/w/2024/01/24/fail/</a>
On my home network I have WPA3 disabled because so many devices seem to do really badly at fast roaming between APs with it, so it's WPA2 everywhere for me. Someday?
Not so fast:<p><a href="https://rachelbythebay.com/w/2024/01/24/fail/" rel="nofollow">https://rachelbythebay.com/w/2024/01/24/fail/</a>
iwd doesn't even work properly with wpa and wpa2:<p><a href="https://www.google.com/search?q=iwd+%22invalid+key%22" rel="nofollow">https://www.google.com/search?q=iwd+%22invalid+key%22</a>