Talk:Iwd

Optional configuration - No need to give example of default file created by iwctl

This edit in Optional configuration makes no sense because thats the minimal file that iwctl will create. So instead of giving example we should encourage to use iwctl.

Other examples are sufficient to indicate how to customize further.

-- Amish (talk) 14:20, 29 December 2018 (UTC)

In my case, iwd didn't accept my 64 digit passphrase. I'm sure all chars and special chars are in the valid range of a wpa2/psk passphrase, no of my other clients complains. So I used iwd to connect to a simple guest WIFI instead, and looked into the created config file as example, duplicated it and modified it for my real WIFI - which works.

The example in the wiki would be an blueprint for others who have the same trouble, or want to create a WIFI connection by script.

Maybe iwd:Troubleshooting would be a better place ?

Ua4000 (talk) 18:17, 29 December 2018 (UTC)

Thats one off case. You probably need to ask upstream to fix it. Also you added it to Optional Configuration but your edit it not really optional configuration. Its a part of mandatory configuration which happens automatically by iwctl. May be others can opine too. Regards.

-- Amish (talk) 08:59, 30 December 2018 (UTC)

A 64 digit psk is not valid. WPA2-PSK requires a preshared key between 8 and 63 characters, inclusive.

JumperPunk (talk) 14:05, 12 October 2021 (UTC)

Troubleshoot: Systemd unit fails on startup due to device not being available

Hi, my English is not so good, but i hope someone with more articulation can edit the page. Also i am not 100% sure it helps. That "race condition" could affect more people. Users with customized Link Name have issues, but also people like me, who need a custom Mac Address. As far as i have see it in iwd/iwctl there is no way to set a custom Mac. I have on something like that:

/etc/systemd/network/20-custom-mac.link

[Match]
MacAddress=FF:FF:FF:55:22:55

[Link]
MacAddress=00:00:00:aa:bb:cc

I get following error:

Sep 02 14:40:06 burpcorp systemd-udevd[9771]: Could not set Alias=, MACAddress= or MTU= on wlan0: Device or resource busy

May be someone could incorporate that info in the wiki, i think in the right form it could be valuable for some people. I think that "Alias MACAddress or MTU" part could be inserted somehow. Maybe that mentioned workaround works. At the time i didn't really noticed that entry, the mash of solutions i hastily misinterpreted did not work and i configured wpa_supplicant. Thanks

—This unsigned comment is by John0 (talk) 16:24, 3 September 2019‎. Please sign your posts with ~~~~!

John0 (talk) 17:11, 3 September 2019 (UTC)

I can't comment on the race condition, but `iwd` does (now)66 support setting a specific MAC address. Use `AddressOverride` under `[Settings]`. JumperPunk (talk) 16:52, 8 February 2021 (UTC)

‎Optional configuration: escaping corrected

[1]

Since SSID and password can have ! or $ charcters, the example should be corrected from " to ', else the result of wpa_passphrase is invalid.

Ua4000 (talk) 14:40, 10 June 2020 (UTC)

People should know the shell they are using and this is not a shell guide. -- Lahwaacz (talk) 06:20, 13 June 2020 (UTC)

Add Section Regarding Network Priority

Mention that unlike [wpa_supplicant], we cannot directly set a network connection priority.

Iwd uses a set of its own metrics from [here](https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/doc/automatic-net-selection.txt) based on network strength and security.

Darkspine (talk) 05:02, 21 May 2021 (UTC)

Troubleshooting: Restarting iwd.service after boot

Why not doing something like this instead?

[Service]
ExecStartPre=ip link set wlan0 up

This is suggested here: https://bugzilla.kernel.org/show_bug.cgi?id=208599#c2

Itaranto (talk) 19:07, 11 October 2021 (UTC)

Select DNS manager (resolvconf)

If resolvconf is selected as the DNS manager, iwd.service needs to be modified to allow access:

RuntimeDirectory=resolvconf
ReadWritePaths=/etc/resolv.conf

—This unsigned comment is by Owenthewizard (talk) 09:18, 8 June 2022. Please sign your posts with ~~~~!

Troubleshooting: Encrypted Network Profiles

@NullPointerException describe the problem you were experiencing here. Nu4425 (talk) 04:11, 14 December 2023 (UTC)

The example steps I provided assumed the system has full tpm2 support, which I plan to change since this may not always be the case such as the Steam Deck. You can determine this via the output of "systemd-creds has-tpm2". However, after following the commands, in your case the profiles became successfully encrypted, were able to be decrypted, but you were unable to connect to any network, correct? Nu4425 (talk) 04:20, 14 December 2023 (UTC)

Wireless device is not renamed by udev

For me the hint

ln -s /dev/null /etc/systemd/network/80-iwd.link

does not enable predictable renaming of wireless device in the section "Wireless device is not renamed by udev".

But

touch /etc/systemd/network/80-iwd.link

does it for me. Stm038842 (talk) 12:35, 27 January 2024 (UTC)