Main Page

2025-12-08T03:00:56Z

Sunrat: /* HowTo */ Added Root, sudo etc.

== About ==
About:
* [[Debian User Forums]]
* [[The Debian Project]]
* [[Archive AI Use]]
* [[Forum jokes, lingo, and memorable quotes|Forum jokes, lino, and memorable quotes]]

== HowTo ==
HowTo:

* [https://forums.debian.net/viewtopic.php?p=338577#p338577 Root, sudo, su, and su -]

* [[To install Firefox from Mozilla repo|Installing Firefox from Mozilla repo]]
* [[WiFi Signal Strength and Sharing]]
* [[REFInd USB Drive (for emergency boot)]]
* [[Trixie iwd]]

== Licensing ==
Licensing:
* [[Publish using CC International licencing and your Forum name]].

Trixie iwd

2025-12-08T02:53:09Z

Sunrat:

Had working iwd wifi on Bookworm and systemd-networkd.

Works also in [https://www.debian.org/releases/trixie/ Trixie], but took a few hours to figure out how wifi is up at boot.

The solution was to edit /etc/iwd/main.conf

<code>arto@niuzu:~$ cat /etc/iwd/[https://wiki.debian.org/WiFi/HowToUse#iwd main.conf]
# For complete description of supported configuration options, refer to
# 'man 5 iwd.config'.

[General]
# iwd is capable of performing network configuration on its own, including
# DHCPv4 based address configuration. By default this behavior is
# disabled, and an external service such as NetworkManager, systemd-network
# or dhcpclient is required. Uncomment the following line if you want iwd
# to manage network interface configuration.
#
EnableNetworkConfiguration=true</code>

and setting in the [General] section EnableNetworkConfiguration on by removing '''#''' from the front of it.

This article was posted by arzgi: https://forums.debian.net/viewtopic.php?t=163650

Edit by sunrat:

Having just set this myself, some more information is needed. The guide in the Debian Wiki was almost all I needed.

I used the standalone setup, no NetworkManager here. Extra packages were required to be install. As well as '''iwd''' it needed dependency of '''libell0,''' and firmware for my device which is '''firmware-atheros'''. Check you have the correct firmware for your device. I also had to enable resolvconf in /etc/iwd/main.conf as I don't have systemd-resolved running.

[c]NameResolvingService=resolvconf[/c]

The rest is copied from Debian Wiki [https://wiki.debian.org/WiFi/HowToUse#iwd WiFiHowToUse]

== IWCtl ==
While also available as backend for ConnMan, NetworkManager, and systemd-networkd, it's also possible to nearly base your entire networking stack on one codebase with IWD alone. It's an all-in-one wireless client, wireless daemon, and even a DHCP client optionally! At its best, your entire networking stack can be as minimal as IWD + systemd-resolved, and this works wonderfully for many scenarios. It has virtually zero dependencies and uses modern kernel features as often as possible. Anecdotal reports suggest that it's much faster to connect to networks than wpa_supplicant, and has better roaming support, among other perceived improvements.

First, install the iwd package. If you've installed wpasupplicant, either uninstall the package, or stop and disable the wpa_supplicant service with:
systemctl --now disable wpa_supplicant
Then, ensure that the newly-installed IWD service is enabled and running with with:
systemctl --now enable iwd

=== Network Configuration ===
If you plan to go the route of using IWD standalone, you should first enable some essential features in IWD's configuration file, which can be found at <code>/etc/iwd/main.conf</code>. Edit this file with root permissions using your favorite editor.

iwd can be configured to configure the network on its own, without requiring external tools or systems to do so. To enable network configuration, add this section to the configuration file:
[General]
EnableNetworkConfiguration=true
Static network configuration can be specified in iwd's network configuration files, as documented in <code>man iwd.network</code> and in the iwd wiki. As per <code>man iwd.config</code>, "If no static IP configuration has been provided for a network, iwd will attempt to obtain the dynamic addresses from the network through the built-in DHCP client."

==== IPv6 ====
To enable IPv6 support, add this section to the configuration file:
[Network]
EnableIPv6=true
'''Note: IPv6 is still somewhat broken as of version 1.19.'''

Enabling IPv6 can cause segmentation faults upon connection. Upstream believes that this has been fixed by commit d0f00698245a ("dhcp6: Switch to BOUND before LEASE_OBTAINED"), but acknowledges that "IPv6 support in iwd is still somewhat experimental since we still lack support for SLAAC," although "DHCPv6 should be mostly functional."

After making changes to iwd's configuration file, restart the service with "<code>service iwd restart</code>" to have them take effect.

=== Configuring iwd Via iwctl ===
Start the IWCtl client by running <code>iwctl</code> as your standard user (not root!), which will start an interactive prompt. You can run <code>help</code> to get a full list of commands here. (If you actually want to '''prevent''' non-root users from configuring iwd, see the directions here.)

To connect to a Wi-Fi network in the most typical scenario, first type <code>device list</code> to find the name of your wireless device. We will use <code>wlan0</code> in this example, but your name may be different, and potentially much longer if your system renames interfaces to a unique name.

After you have the device name, run something like <code>station wlan0 scan</code> to have the device scan for networks. You can then list these networks by running <code>station wlan0 get-networks</code>. After you've found the network you intend to connect to, run <code>station wlan0 connect Router123</code>, replacing <code>Router123</code> with the name of the network. Put the name of the network in double-quotes if it contains a space. (Note that you can use tab completion to enter the network name, and iwd will even help with the quoting.)

IWCtl will then prompt you for the passphrase. After entering this, IWD will connect to the network, and store it permanently in the <code>/var/lib/iwd</code> directory. After being added in this way, IWD will attempt to auto-connect to the network in the future.

Try running <code>ping 1.1.1.1</code> to see if you can reach an IP, and then <code>ping gnu.org</code> to see if you can reach a domain. If you can't reach an IP, something's gone horribly wrong when connecting to the network. If you can't reach a domain but you can reach an IP, you'll need to configure your DNS. The simplest way to accomplish that is ...

=== Setting up DNS resolution for IWD (Simple) ===
If "EnableNetworkConfiguration=true" is set, you'll also need to configure IWD's name resolving service. It supports systemd-resolved and resolvconf. If unspecified, it uses systemd-resolved. Refer to the IWD.CONFIG(5) page if you care about using resolvconf instead.

If DNS is nonfunctional, you likely need to configure systemd-resolved for use with IWD. Enable and start the systemd-resolved service, if it isn't already, by running:
systemctl enable --now systemd-resolved
Then, symlink <code>/etc/resolv.conf</code> to <code>/run/systemd/resolve/stub-resolv.conf</code> by running:
# ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
That should be enough to get you online. If you want to make changes to your DNS configuration, refer to the <code>/etc/systemd/resolved.conf</code> file, and the associated manual page at RESOLVED.CONF(5)
[[index.php?title=Category:HowTo]]
[[index.php?title=Category:Wifi]]

Archive Debian Forums - User contributions [en]

Main Page

Trixie iwd