Iwd: Difference between revisions
Philipwilk (talk | contribs) Add troubleshooting step for disconnect-info reason: 2 for Qualcomm QCNCM865 chipsets |
Fixed an error in prior change (forgot Network) |
||
| (7 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:iwd}} | |||
[https://archive.kernel.org/oldwiki/iwd.wiki.kernel.org/ iwd] (iNet wireless daemon) is a Linux-only wireless daemon aiming to decrease the time spent making connections. | [https://archive.kernel.org/oldwiki/iwd.wiki.kernel.org/ iwd] (iNet wireless daemon) is a Linux-only wireless daemon aiming to decrease the time spent making connections. | ||
| Line 18: | Line 19: | ||
{ | { | ||
networking.wireless.iwd.settings = { | networking.wireless.iwd.settings = { | ||
Network = { | |||
EnableIPv6 = true; | |||
}; | }; | ||
Settings = { | Settings = { | ||
| Line 51: | Line 52: | ||
<syntaxhighlight lang="nix"> | <syntaxhighlight lang="nix"> | ||
networking.networkmanager.wifi.backend = "iwd"; | networking.networkmanager.wifi.backend = "iwd"; | ||
</syntaxhighlight> | </syntaxhighlight>{{Warning|Setting this will silently turn off MAC address randomization as Networkmanager does not control the MAC address randomization features of `iwd` for which it is turned off by default.<ref>https://bbs.archlinux.org/viewtopic.php?id=280657</ref><ref>https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1111</ref> | ||
To remediate this, configure iwd directly using the `AddressRandomization` option.}} | |||
=== iwd as backend for Connman === | === iwd as backend for Connman === | ||
| Line 71: | Line 73: | ||
</pre> | </pre> | ||
Your desktop manager may not enable some secrets management service you may need to enable one: | Your desktop manager may not enable some secrets management service you may need to enable one: | ||
< | <syntaxhighlight lang="nix"> | ||
{ | { | ||
services. | services.gnome.gnome-keyring.enable = true; | ||
} | } | ||
</ | </syntaxhighlight> | ||
=== rfkill blocks wireless device === | === rfkill blocks wireless device === | ||
| Line 93: | Line 95: | ||
=== desconnect-info reason: 2 === | === desconnect-info reason: 2 === | ||
When using certain chipsets, such as the Qualcomm qcncm865<ref>https://community.frame.work/t/guide-successful-wi-fi-7-802-11be-on-framework-13-amd-with-qualcomm-qcncm865-and-arch-linux/44723</ref>, you need to use legacy EAPoL packets<ref>https://lkml.org/lkml/2020/10/14/1101</ref> to prevent a disconnect loop. In <code>iwd.service</code> this | When using certain chipsets, such as the Qualcomm qcncm865<ref>https://community.frame.work/t/guide-successful-wi-fi-7-802-11be-on-framework-13-amd-with-qualcomm-qcncm865-and-arch-linux/44723</ref>, you need to use legacy EAPoL packets<ref>https://lkml.org/lkml/2020/10/14/1101</ref> to prevent a disconnect loop. In <code>iwd.service</code> this issue shows up as:<syntaxhighlight> | ||
SA Query timed out, connection is invalid. Disconnecting... | SA Query timed out, connection is invalid. Disconnecting... | ||
Feb 26 10:17:10 probook iwd[4486]: event: disconnect-info, reason: 2 | Feb 26 10:17:10 probook iwd[4486]: event: disconnect-info, reason: 2 | ||