Iwd - Revision history

Prabuanand: rearranged page and removed a hack related to Loss of connectivity due to changes in interface names

2025-08-18T07:23:36Z

rearranged page and removed a hack related to Loss of connectivity due to changes in interface names

← Older revision		Revision as of 07:23, 18 August 2025
Line 40:		Line 40:
	=== iwd with ifupdown-ng ===		=== iwd with ifupdown-ng ===

	[[ifupdown-ng]] ~~can be used to~~ do network ~~management for iwd~~. ~~Refer [[#ifupdown-ng configuration~~\|~~ifupdown-ng configuration]] section.~~		iwd can delegate the responsibility dealing with IP address assignment (either static or DHCP) to [[ifupdown-ng]]. To do this edit the {{Path\|/etc/network/interfaces}} file. For example, if you are using DHCP on the wlan0 interface: {{Cat\|/etc/network/interfaces\|auto lo
			iface lo inet loopback

			auto wlan0
			iface wlan0 inet dhcp
			}}

	== Configuration ==		== Configuration ==

			=== Service configuration ===

			{{ic\|iwd}} service can be managed using standard [[OpenRC]] commands. Once iwd service has been fully configured and [[Configure_Networking#Connectivity_testing\|tested]], then add the {{ic\|iwd}} service and disable the {{ic\|networking}} boot service:{{cmd\|<nowiki># rc-update add iwd boot
			# rc-update del networking boot</nowiki>}}

	To proceed with the configuration of iwd, ensure that {{ic\|wpa_supplicant}} service is stopped before starting iwd service:{{cmd\|<nowiki># rc-service wpa_supplicant stop		To proceed with the configuration of iwd, ensure that {{ic\|wpa_supplicant}} service is stopped before starting iwd service:{{cmd\|<nowiki># rc-service wpa_supplicant stop
	# rc-service iwd start</nowiki>}}		# rc-service iwd start</nowiki>}}

	{{Tip\|~~The configuration steps using {{ic\|iwctl}}~~ can be done in GUI using [[#iwgtk\|'''iwgtk''']] utility. ~~Other steps have to~~ be ~~done~~ from ~~CLI only~~.}}		=== Connection management ===

			{{Tip\|Basic connection management can be done in GUI using [[#iwgtk\|'''iwgtk''']] utility.}}

			{{ic\|iwctl}} tool can be run both in interactive and non-interactive mode. The non-interactive commands can be issued from the shell by suffixing {{ic\|iwctl}} like {{ic\|$ iwctl device list}} or {{ic\|$ iwctl known-networks list}}.

			The example below shows the step-by-step procedure to configure iwd in an interactive mode. Begin by starting the {{ic\|iwctl}} as follows:{{Cmd\|$ iwctl}}

			The prompt should display:

			<span style="color:green;">[iwd]</span>#

	~~To configure iwd in an interactive mode using the CLI based client program {{ic\|iwctl}}, start the client:{{Cmd\|$ iwctl}}~~
	To list all available commands:		To list all available commands:
	<span style="color:green;">[iwd]</span># help		<span style="color:green;">[iwd]</span># help

	=== To connect to a network ===		==== To connect to a network ====

	To list all Wi-Fi devices:		To list all Wi-Fi devices:
Line 82:		Line 101:
	* iwd only supports PSK pass-phrases from 8 to 63 ASCII-encoded characters. }}		* iwd only supports PSK pass-phrases from 8 to 63 ASCII-encoded characters. }}

	=== Disconnect from a network ===		==== Disconnect from a network ====

	To disconnect from a network:		To disconnect from a network:
Line 88:		Line 107:
	<span style="color:green;">[iwd]</span># station ''device'' disconnect		<span style="color:green;">[iwd]</span># station ''device'' disconnect

	=== Show device and connection information ===		==== Show device and connection information ====

	To display the details of a WiFi device, like MAC address:		To display the details of a WiFi device, like MAC address:
Line 98:		Line 117:
	<span style="color:green;">[iwd]</span># station ''device'' show		<span style="color:green;">[iwd]</span># station ''device'' show

	=== Manage known networks ===		==== Manage known networks ====

	To list networks you have connected to previously:		To list networks you have connected to previously:
Line 115:		Line 134:
	* channel utilization		* channel utilization
	* time since the last connect.}}		* time since the last connect.}}

	~~=== ifupdown-ng configuration ===~~

	If [[ifupdown-ng]] is used for network configuration management with iwd, edit the {{path\|/etc/network/interfaces}} file based on instructions in [[Configure_Networking#Interface configuration\|Network configuration]] page.

	Whenever system wakes up from sleep/suspend, the wireless interface name may change from {{ic\|wlan0}} to {{ic\|wlan1}}, {{ic\|wlan2}} and so on resulting in loss of connectivity when using [[ifupdown-ng]]. To avoid this issue, create and add the following two files. The {{path\|/etc/iwd/main.conf}} file should have:{{cat\|/etc/iwd/main.conf\|<nowiki>[DriverQuirks]
	~~DefaultInterface=wlan0</nowiki>}}~~
	If mac address of {{ic\|wlan0}} interface is "50:91:e3:71:83:d2", then file {{Path\|/etc/udev/rules.d/70-persistent-net-wlan0.rules}} should be as follows:{{cat\|/etc/udev/rules.d/70-persistent-net-wlan0.rules\|<nowiki>SUBSYSTEM=="net", ACTION=="add", ATTRS{address}=="50:91:e3:71:83:d2", NAME="wlan0"</nowiki>}}
	~~The command{{ic\|cat /sys/class/net/wlan0/address}} shows the mac address of your wireless interface {{ic\|wlan0}}.~~
	~~For the above changes to take immediate effect, reload Udev rules:{{Cmd\|<nowiki># udevadm control --reload-rules~~
	~~# udevadm trigger</nowiki>}}~~
	~~A reboot is usually necessary for the changes to fully take effect.~~

	~~=== Service configuration ===~~
	~~{{Seealso\|OpenRC}}~~
	~~Manage iwd service using the standard start, stop and restart options. For eg: To start the iwd service immediately issue the command: {{cmd\|# rc-service iwd start}}~~

	Once iwd service has been fully configured and [[Configure_Networking#Connectivity_testing\|tested]], add the {{ic\|iwd}} service and disable the {{ic\|networking}} boot service:{{cmd\|<nowiki># rc-update add iwd boot
	~~# rc-update del networking boot</nowiki>}}~~


	== Troubleshooting ==		== Troubleshooting ==
Line 155:		Line 154:

	The above error message may occur whenever the networking service gets loaded by openrc after iwd. Refer to [[#Service configuration\|Service configuration]] section.		The above error message may occur whenever the networking service gets loaded by openrc after iwd. Refer to [[#Service configuration\|Service configuration]] section.

			=== Loss of connectivity due to changes in interface names ===

			Whenever system wakes up from sleep/suspend, the wireless interface name may change from {{ic\|wlan0}} to {{ic\|wlan1}}, {{ic\|wlan2}} and so on resulting in loss of connectivity. If you expereince this issue, if [[eudev]] is used as device manager refer to [[eudev#Predictable network interface names\|predictable network interface names]] section.

	== See also ==		== See also ==

Prabuanand: typo change

2025-03-31T07:46:40Z

typo change

← Older revision		Revision as of 07:46, 31 March 2025
Line 11:		Line 11:
	== Installation ==		== Installation ==

	Install {{Pkg\|iwd\|arch=}} package and ~~the optional GUI utility~~ {{Pkg\|iwgtk\|arch=}} package using the command:{{Cmd\|# apk add ~~{{Pkg\|~~iwd~~\|arch=}} {{Pkg\|~~iwgtk~~\|arch=}}(optional)~~}}		Install {{Pkg\|iwd\|arch=}} package and {{Pkg\|iwgtk\|arch=}} package for the ''optional'' GUI utility [[#iwgtk\|iwgtk]] using the command:{{Cmd\|# apk add iwd iwgtk}}

	=== iwgtk ===		=== iwgtk ===

Prabuanand: moved heading

2025-03-31T07:32:10Z

moved heading

← Older revision		Revision as of 07:32, 31 March 2025
Line 11:		Line 11:
	== Installation ==		== Installation ==

	Install {{Pkg\|iwd\|arch=}} package and the optional GUI utility ~~[[#~~iwgtk\|~~iwgtk]]~~ using the command:{{Cmd\|# apk add {{Pkg\|iwd\|arch=}} {{Pkg\|iwgtk\|arch=}}(optional)}}		Install {{Pkg\|iwd\|arch=}} package and the optional GUI utility {{Pkg\|iwgtk\|arch=}} package using the command:{{Cmd\|# apk add {{Pkg\|iwd\|arch=}} {{Pkg\|iwgtk\|arch=}}(optional)}}

	Next, choose one among the three ~~options~~ listed below on how iwd ~~will be used~~ before proceeding further.		=== iwgtk ===
			[[File:Iwgtk screenshot.png\|thumb\|right\|100px\|alt=iwgtk showing list of networks\|iwgtk]]

			[https://github.com/J-Lentz/iwgtk iwgtk] is a wireless networking GUI utility for iwd with supported functionality similar to that of <code>iwctl</code>. Features include viewing and connecting to available networks, managing known networks, provisioning new networks via WPS or Wi-Fi Easy Connect, and an
			indicator (tray) icon displaying connection status and signal strength.

			== Network management mode ==

			Next, choose one among the three modes listed below on how Network management will done with iwd before proceeding further.

	=== Standalone mode ===		=== Standalone mode ===
Line 127:		Line 135:
	# rc-update del networking boot</nowiki>}}		# rc-update del networking boot</nowiki>}}

	~~== iwgtk ==~~
	~~[[File:Iwgtk screenshot.png\|thumb\|right\|100px\|alt=iwgtk showing list of networks\|iwgtk]]~~

	[https://github.com/J-Lentz/iwgtk iwgtk] is a wireless networking GUI utility for iwd with supported functionality similar to that of <code>iwctl</code>. Features include viewing and connecting to available networks, managing known networks, provisioning new networks via WPS or Wi-Fi Easy Connect, and an indicator (tray) icon displaying connection status and signal strength.

	== Troubleshooting ==		== Troubleshooting ==

Prabuanand: rephrased sentence

2025-03-31T05:54:50Z

rephrased sentence

← Older revision		Revision as of 05:54, 31 March 2025
Line 11:		Line 11:
	== Installation ==		== Installation ==

	Install {{Pkg\|iwd\|arch=}} package and the optional GUI utility [[#iwgtk\|iwgtk]] using the command:{{Cmd\|# apk add iwd iwgtk(optional)}}		Install {{Pkg\|iwd\|arch=}} package and the optional GUI utility [[#iwgtk\|iwgtk]] using the command:{{Cmd\|# apk add {{Pkg\|iwd\|arch=}} {{Pkg\|iwgtk\|arch=}}(optional)}}

	Next, choose one among the three options listed below on how iwd will be used before proceeding further.		Next, choose one among the three options listed below on how iwd will be used before proceeding further.
Line 39:		Line 39:
	# rc-service iwd start</nowiki>}}		# rc-service iwd start</nowiki>}}

	{{Tip\|The GUI ~~utility~~ [[#iwgtk\|'''iwgtk''']] ~~can~~ be used for configuration when iwd is used in [[#standalone mode\|standalone mode]] or [[#iwd with ifupdown-ng\|with ifupdown-ng]]. Use [[NetworkManager]] GUI/TUI tools when [[#iwd as a networkmanager backend\|iwd is used as networkmanager backend]].}}		{{Tip\|The configuration steps using {{ic\|iwctl}} can be done in GUI using [[#iwgtk\|'''iwgtk''']] utility. Other steps have to be done from CLI only.}}

	To configure iwd in an interactive mode using the CLI based client program {{ic\|iwctl}}, start the client:{{Cmd\|$ iwctl}}		To configure iwd in an interactive mode using the CLI based client program {{ic\|iwctl}}, start the client:{{Cmd\|$ iwctl}}
Line 130:		Line 130:
	[[File:Iwgtk screenshot.png\|thumb\|right\|100px\|alt=iwgtk showing list of networks\|iwgtk]]		[[File:Iwgtk screenshot.png\|thumb\|right\|100px\|alt=iwgtk showing list of networks\|iwgtk]]

	[https://github.com/J-Lentz/iwgtk iwgtk] is a wireless networking GUI utility for iwd with supported functionality similar to that of <code>iwctl</code> ~~available as {{Pkg\|iwgtk\|arch=}} package~~. Features include viewing and connecting to available networks, managing known networks, provisioning new networks via WPS or Wi-Fi Easy Connect, and an indicator (tray) icon displaying connection status and signal strength.		[https://github.com/J-Lentz/iwgtk iwgtk] is a wireless networking GUI utility for iwd with supported functionality similar to that of <code>iwctl</code>. Features include viewing and connecting to available networks, managing known networks, provisioning new networks via WPS or Wi-Fi Easy Connect, and an indicator (tray) icon displaying connection status and signal strength.

	== Troubleshooting ==		== Troubleshooting ==

Prabuanand: removed repetitive information and obsolete info

2025-03-31T05:41:33Z

removed repetitive information and obsolete info

← Older revision		Revision as of 05:41, 31 March 2025
Line 1:		Line 1:
	{{DISPLAYTITLE:iwd}}		{{DISPLAYTITLE:iwd}}
	iNet Wireless Daemon (iwd) project aims to provide a comprehensive Wi-Fi connectivity solution for Linux based devices. iwd provides a self-contained environment that only depends on the Linux Kernel and the runtime C library~~. iwd is supported since [https://alpinelinux.org/posts/Alpine-3.10.0-released.html v3.10] of Alpine Linux~~.		iNet Wireless Daemon (iwd) project aims to provide a comprehensive Wi-Fi connectivity solution for Linux based devices. iwd provides a self-contained environment that only depends on the Linux Kernel and the runtime C library.

	{{Note\|Alpine Linux supports both wireless daemons i.e [[Wi-Fi#wpa_supplicant\|wpa_supplicant]] and [[iwd]]. Using both ~~wireless daemons i.e [[Wi-Fi#wpa_supplicant\|wpa_supplicant]] and [[iwd]]~~ simultaneously ~~lead~~ to conflicts.}}		{{Note\|Alpine Linux supports both wireless daemons i.e [[Wi-Fi#wpa_supplicant\|wpa_supplicant]] and [[iwd]]. Using both simultaneously leads to conflicts.}}

	== Prerequisites ==		== Prerequisites ==

Prabuanand: reworded headings and content to make things easier to follow

2025-03-31T05:37:56Z

reworded headings and content to make things easier to follow

← Older revision		Revision as of 05:37, 31 March 2025
Line 11:		Line 11:
	== Installation ==		== Installation ==

	Install {{Pkg\|iwd\|arch=}} package using the command:{{Cmd\|# apk add ~~{{Pkg\|~~iwd}}}}		Install {{Pkg\|iwd\|arch=}} package and the optional GUI utility [[#iwgtk\|iwgtk]] using the command:{{Cmd\|# apk add iwd iwgtk(optional)}}

	Next ~~decide if you want to use iwd in Standalone mode, or with NetworkManager~~, ~~or with ifupdown-ng. Choose~~ one among the three options ~~and then proceed to [[#Service configuration\|service configuration~~.]]		Next, choose one among the three options listed below on how iwd will be used before proceeding further.

	=== Standalone mode ===		=== Standalone mode ===

	To have iwd do ~~most networking configuration~~ on its own upon connecting to a wi-fi network, requires {{pkg\|openresolv\|arch=}} package, so install it first:{{Cmd\|# apk add {{Pkg\|openresolv}}}}		To have iwd do all network management on its own upon connecting to a wi-fi network, requires {{pkg\|openresolv\|arch=}} package, so install it first:{{Cmd\|# apk add {{Pkg\|openresolv}}}}
	Then edit the configuration file {{path\|/etc/iwd/main.conf}} and set it as follows: {{cat\|/etc/iwd/main.conf\|[General]		Then edit the configuration file {{path\|/etc/iwd/main.conf}} and set it as follows: {{cat\|/etc/iwd/main.conf\|[General]
	EnableNetworkConfiguration{{=}}True		EnableNetworkConfiguration{{=}}True
Line 26:		Line 26:
	To test {{Pkg\|openresolv}} package, issue the command:{{ic\|# resolvconf -u}} to update the nameserver information in {{Path\|/etc/resolv.conf}} file.		To test {{Pkg\|openresolv}} package, issue the command:{{ic\|# resolvconf -u}} to update the nameserver information in {{Path\|/etc/resolv.conf}} file.

	=== ~~Use~~ iwd as a networkmanager backend ===		=== iwd as a networkmanager backend ===
	{{Main\|NetworkManager#iwd_backend}}		{{Main\|NetworkManager#iwd_backend}}
	[[NetworkManager]] can be ~~configured to manage Network configuration~~ for ~~iwd. Since [[Wi-Fi#wpa_supplicant\|wpa_supplicant]] is the default backend in NetworkManager~~, ~~it must be~~ [[NetworkManager#iwd_backend\|~~replaced by~~ iwd]].		[[NetworkManager]] can be used for network management, with [[NetworkManager#iwd_backend\|iwd configured as a wireless backend]].

	=== ~~Use~~ iwd with ifupdown-ng ===		=== iwd with ifupdown-ng ===

	[[ifupdown-ng]] can be used to ~~manage Network configuration~~ for iwd. Refer to [[#ifupdown-ng configuration\|ifupdown-ng configuration]] section.		[[ifupdown-ng]] can be used to do network management for iwd. Refer [[#ifupdown-ng configuration\|ifupdown-ng configuration]] section.

	== Configuration ==		== Configuration ==

	~~{{Note\|~~To ~~avoid conflicts~~, ensure that ~~[[Wi-Fi#Service_configuration~~\|wpa_supplicant~~]] and related services are~~ stopped before ~~continuing.~~}}		To proceed with the configuration of iwd, ensure that {{ic\|wpa_supplicant}} service is stopped before starting iwd service:{{cmd\|<nowiki># rc-service wpa_supplicant stop
			# rc-service iwd start</nowiki>}}

	~~Start iwd service first to proceed with the configuration:~~{{~~cmd~~\|# rc-~~service~~ iwd ~~start~~}}		{{Tip\|The GUI utility [[#iwgtk\|'''iwgtk''']] can be used for configuration when iwd is used in [[#standalone mode\|standalone mode]] or [[#iwd with ifupdown-ng\|with ifupdown-ng]]. Use [[NetworkManager]] GUI/TUI tools when [[#iwd as a networkmanager backend\|iwd is used as networkmanager backend]].}}

	~~The~~ {{~~pkg~~\|~~iwd~~}} ~~package provides the client program <code>iwctl</code>~~, ~~the daemon <code>iwd</code> and the Wi-Fi monitoring tool <code>iwmon</code>.~~		To configure iwd in an interactive mode using the CLI based client program {{ic\|iwctl}}, start the client:{{Cmd\|$ iwctl}}

	~~Begin by starting~~ the client:{{Cmd\|$ iwctl}}
	To list all available commands:		To list all available commands:
	<span style="color:green;">[iwd]</span># help		<span style="color:green;">[iwd]</span># help
Line 122:		Line 121:

	=== Service configuration ===		=== Service configuration ===
			{{Seealso\|OpenRC}}
	To start the iwd service immediately issue the command: {{cmd\|# rc-service iwd start}}		Manage iwd service using the standard start, stop and restart options. For eg: To start the iwd service immediately issue the command: {{cmd\|# rc-service iwd start}}

	Once iwd service has been fully configured and [[Configure_Networking#Connectivity_testing\|tested]], add the {{ic\|iwd}} service and disable the {{ic\|networking}} boot service:{{cmd\|<nowiki># rc-update add iwd boot		Once iwd service has been fully configured and [[Configure_Networking#Connectivity_testing\|tested]], add the {{ic\|iwd}} service and disable the {{ic\|networking}} boot service:{{cmd\|<nowiki># rc-update add iwd boot
Line 129:		Line 128:

	== iwgtk ==		== iwgtk ==

	[[File:Iwgtk screenshot.png\|thumb\|right\|100px\|alt=iwgtk showing list of networks\|iwgtk]]		[[File:Iwgtk screenshot.png\|thumb\|right\|100px\|alt=iwgtk showing list of networks\|iwgtk]]

	[https://github.com/J-Lentz/iwgtk iwgtk] is a wireless networking GUI for iwd with supported functionality similar to that of <code>iwctl</code>. Features include viewing and connecting to available networks, managing known networks, provisioning new networks via WPS or Wi-Fi Easy Connect, and an indicator (tray) icon displaying connection status and signal strength.		[https://github.com/J-Lentz/iwgtk iwgtk] is a wireless networking GUI utility for iwd with supported functionality similar to that of <code>iwctl</code> available as {{Pkg\|iwgtk\|arch=}} package. Features include viewing and connecting to available networks, managing known networks, provisioning new networks via WPS or Wi-Fi Easy Connect, and an indicator (tray) icon displaying connection status and signal strength.
	~~To install the {{Pkg\|iwgtk}} package: {{Cmd\|# apk add {{Pkg\|iwgtk}}}}~~

	== Troubleshooting ==		== Troubleshooting ==

			Resolve [[Wi-Fi#Troubleshooting\|wireless driver issues]] first, if your wireless device is not detected, when the below command is issued:{{cmd\|<nowiki>$ iwctl device list
			Devices
			--------------------------------------------------------------------------------
			Name Address Powered Adapter Mode
			--------------------------------------------------------------------------------
			wlan0 50:91:e3:71:83:d2 on phy0 station
			</nowiki>}}

			=== "The name net.connman.iwd was not provided by any .service files" ===

	If {{ic\|iwctl}} commands fail with the message {{ic\|The name net.connman.iwd was not provided by any .service files Failed to retrieve IWD dbus objects, quitting...}}.		If {{ic\|iwctl}} commands fail with the message {{ic\|The name net.connman.iwd was not provided by any .service files Failed to retrieve IWD dbus objects, quitting...}}.

Prabuanand: updated an alternate solution

2025-03-30T18:10:40Z

updated an alternate solution

← Older revision		Revision as of 18:10, 30 March 2025
Line 125:		Line 125:
	To start the iwd service immediately issue the command: {{cmd\|# rc-service iwd start}}		To start the iwd service immediately issue the command: {{cmd\|# rc-service iwd start}}

	Once iwd service has been fully configured and [[Configure_Networking#Connectivity_testing\|tested]], ~~to have~~ iwd service ~~start automatically on every~~ boot ~~(recommended)~~:{{cmd\|# rc-update add iwd boot}}		Once iwd service has been fully configured and [[Configure_Networking#Connectivity_testing\|tested]], add the {{ic\|iwd}} service and disable the {{ic\|networking}} boot service:{{cmd\|<nowiki># rc-update add iwd boot
			# rc-update del networking boot</nowiki>}}
	~~To avoid conflicts, ensure that <Code>wpa_supplicant~~</~~Code~~> ~~service and <Code>networkmanager</Code> (if not used with iwd) are not started automatically.~~

	~~Refer to [[openRC]] page for more options.~~

	== iwgtk ==		== iwgtk ==
Line 146:		Line 143:
	=== "ip: ioctl 0x8913 failed: No such device" ===		=== "ip: ioctl 0x8913 failed: No such device" ===

	~~When iwd is used with [[ifupdown-ng]], the~~ above error message may occur whenever the networking service gets loaded by openrc after iwd. ~~The solution given in the above~~ [[#~~ifupdown-ng~~ configuration\|~~ifupdown-ng~~ configuration]] ~~will not work if the default [[mdev]] is used~~. ~~A temporary workaround is to edit the file {{Path\|/etc/init.d/iwd}} and replacing {{ic\|before net}} to {{ic\|after net}} in the depends function as follows:{{Cat\|/etc/init.d/iwd\|depend() {~~		The above error message may occur whenever the networking service gets loaded by openrc after iwd. Refer to [[#Service configuration\|Service configuration]] section.
	~~need dbus~~
	~~after net~~
	~~keyword -shutdown~~
	~~provide wlan~~
	}
	}}

	== See also ==		== See also ==

Prabuanand: rephrased sentence

2025-03-30T17:45:39Z

rephrased sentence

← Older revision		Revision as of 17:45, 30 March 2025
Line 144:		Line 144:
	The above error means that the {{ic\|iwd}} daemon is not started. Start the [[#Service configuration\|iwd daemon]]		The above error means that the {{ic\|iwd}} daemon is not started. Start the [[#Service configuration\|iwd daemon]]

	== "ip: ioctl 0x8913 failed: No such device" ==		=== "ip: ioctl 0x8913 failed: No such device" ===

	~~Whenever the networking service gets loaded by openrc after iwd, the above error message may occur when~~ iwd is used with [[ifupdown-ng]]. The solution given in the above [[#ifupdown-ng configuration\|ifupdown-ng configuration]] will not work if the default [[mdev]] is used. A temporary workaround is to edit the file {{Path\|/etc/init.d/iwd}} and replacing {{ic\|before net}} to {{ic\|after net}} in the depends function as follows:{{Cat\|/etc/init.d/iwd\|depend() {		When iwd is used with [[ifupdown-ng]], the above error message may occur whenever the networking service gets loaded by openrc after iwd. The solution given in the above [[#ifupdown-ng configuration\|ifupdown-ng configuration]] will not work if the default [[mdev]] is used. A temporary workaround is to edit the file {{Path\|/etc/init.d/iwd}} and replacing {{ic\|before net}} to {{ic\|after net}} in the depends function as follows:{{Cat\|/etc/init.d/iwd\|depend() {
	need dbus		need dbus
	after net		after net
Line 153:		Line 153:
	}		}
	}}		}}

	== See also ==		== See also ==

Prabuanand: added content based on report from dridri on 2025-03-30 15:48:06 in #alpine-linux IRC channel

2025-03-30T17:43:10Z

added content based on report from dridri on 2025-03-30 15:48:06 in #alpine-linux IRC channel

← Older revision		Revision as of 17:43, 30 March 2025
Line 144:		Line 144:
	The above error means that the {{ic\|iwd}} daemon is not started. Start the [[#Service configuration\|iwd daemon]]		The above error means that the {{ic\|iwd}} daemon is not started. Start the [[#Service configuration\|iwd daemon]]

			== "ip: ioctl 0x8913 failed: No such device" ==

			Whenever the networking service gets loaded by openrc after iwd, the above error message may occur when iwd is used with [[ifupdown-ng]]. The solution given in the above [[#ifupdown-ng configuration\|ifupdown-ng configuration]] will not work if the default [[mdev]] is used. A temporary workaround is to edit the file {{Path\|/etc/init.d/iwd}} and replacing {{ic\|before net}} to {{ic\|after net}} in the depends function as follows:{{Cat\|/etc/init.d/iwd\|depend() {
			need dbus
			after net
			keyword -shutdown
			provide wlan
			}
			}}
	== See also ==		== See also ==

	* [[Configure Networking\|Main Networking page]]		* [[Configure Networking\|Main Networking page]]
	* [[Wi-Fi\|wpa_supplicant]]		* [[Wi-Fi\|wpa_supplicant]]

Prabuanand: updated instructions for ifupdown-ng configuration

2025-03-22T08:22:19Z

updated instructions for ifupdown-ng configuration

← Older revision		Revision as of 08:22, 22 March 2025
Line 28:		Line 28:
	=== Use iwd as a networkmanager backend ===		=== Use iwd as a networkmanager backend ===
	{{Main\|NetworkManager#iwd_backend}}		{{Main\|NetworkManager#iwd_backend}}
	[[NetworkManager]] can be configured to manage Network configuration for iwd. Since [[Wi-Fi#wpa_supplicant\|wpa_supplicant]] is the default backend, it must be [[NetworkManager#iwd_backend\|replaced]].		[[NetworkManager]] can be configured to manage Network configuration for iwd. Since [[Wi-Fi#wpa_supplicant\|wpa_supplicant]] is the default backend in NetworkManager, it must be [[NetworkManager#iwd_backend\|replaced by iwd]].

	=== Use iwd with ifupdown-ng ===		=== Use iwd with ifupdown-ng ===

	~~iwd can delegate the responsibility of network configuration management (either static or DHCP) to~~ [[ifupdown-ng]]. Refer to [[~~Configure_Networking~~#~~Interface~~ configuration\|~~Network configuration]] page edit the {{path\|/etc/network/interfaces}} file.~~		[[ifupdown-ng]] can be used to manage Network configuration for iwd. Refer to [[#ifupdown-ng configuration\|ifupdown-ng configuration]] section.

	~~Whenever system wakes up from sleep/suspend, the wireless interface name may change from {{ic\|wlan0}} to {{ic\|wlan1}}, {{ic\|wlan2}} and so on resulting in loss of connectivity when using [[~~ifupdown-ng]]~~. To avoid this issue, create and add the following two files. The {{path\|/etc/iwd/main.conf}} file should have:{{cat\|/etc/iwd/main.conf\|<nowiki>[DriverQuirks]~~
	~~DefaultInterface=wlan0</nowiki>}}~~
	If mac address of {{ic\|wlan0}} interface is "50:91:e3:71:83:d2", then file {{Path\|/etc/udev/rules.d/70-persistent-net-wlan0.rules}} should be as follows:{{cat\|/etc/udev/rules.d/70-persistent-net-wlan0.rules\|<nowiki>SUBSYSTEM=="net", ACTION=="add", ATTRS{address}=="50:91:e3:71:83:d2", NAME="wlan0"</nowiki>}}
	~~The command{{ic\|cat /sys/class/net/wlan0/address}} shows the mac address of your wireless interface {{ic\|wlan0}}~~.

	== Configuration ==		== Configuration ==
Line 113:		Line 108:
	* channel utilization		* channel utilization
	* time since the last connect.}}		* time since the last connect.}}

			=== ifupdown-ng configuration ===

			If [[ifupdown-ng]] is used for network configuration management with iwd, edit the {{path\|/etc/network/interfaces}} file based on instructions in [[Configure_Networking#Interface configuration\|Network configuration]] page.

			Whenever system wakes up from sleep/suspend, the wireless interface name may change from {{ic\|wlan0}} to {{ic\|wlan1}}, {{ic\|wlan2}} and so on resulting in loss of connectivity when using [[ifupdown-ng]]. To avoid this issue, create and add the following two files. The {{path\|/etc/iwd/main.conf}} file should have:{{cat\|/etc/iwd/main.conf\|<nowiki>[DriverQuirks]
			DefaultInterface=wlan0</nowiki>}}
			If mac address of {{ic\|wlan0}} interface is "50:91:e3:71:83:d2", then file {{Path\|/etc/udev/rules.d/70-persistent-net-wlan0.rules}} should be as follows:{{cat\|/etc/udev/rules.d/70-persistent-net-wlan0.rules\|<nowiki>SUBSYSTEM=="net", ACTION=="add", ATTRS{address}=="50:91:e3:71:83:d2", NAME="wlan0"</nowiki>}}
			The command{{ic\|cat /sys/class/net/wlan0/address}} shows the mac address of your wireless interface {{ic\|wlan0}}.
			For the above changes to take immediate effect, reload Udev rules:{{Cmd\|<nowiki># udevadm control --reload-rules
			# udevadm trigger</nowiki>}}
			A reboot is usually necessary for the changes to fully take effect.

	=== Service configuration ===		=== Service configuration ===