wiki.archlinux.org Network configuration

Medium-specifics are handled in the /Ethernet and /Wireless subpages.

wiki.archlinux.org Network configuration/Ethernet

This article describes Ethernet specifics, general network configuration is covered in Network configuration.

wiki.archlinux.org Network configuration/Wireless

The main article on network configuration is Network configuration.

wiki.archlinux.org netctl

broadcom-wl for Toshiba Satellite

wiki.archlinux.org/ broadcom_wireless broadcom-wl

There are two variants of the restrictively licensed driver:

the regular variant: broadcom-wl

the DKMS variant: broadcom-wl-dkms

Tip: The DKMS variant broadcom-wl-dkms

is kernel agnostic. This means it supports different kernels you may use (e.g. linux-ckAUR).
is kernel-release agnostic, too. It will be automatically rebuilt after every kernel upgrade or fresh installation. If you use broadcom-wl or another kernel release dependant variant (e.g. broadcom-wl-ckAUR), it may happen that kernel upgrades break wireless from time to time until the packages are in sync again.
will need the linux-headers package for the installed kernel(s) in order to build the module. Those packages are optional to the DKMS package and will need to be installed manually.

Interface is showing but not allowing connections

        Append the following kernel parameter:
        
        b43.allhwsupport=1

wiki.archlinux.org/ Driver selection

To know what driver(s) are operable on the computer’s Broadcom wireless network device, the device ID and chipset name will need to be detected. Cross-reference them with the driver list of supported brcm80211 and b43 devices.

        $ lspci -vnn -d 14e4:

b43 Two reverse-engineered open-source drivers are built-in to the kernel: b43 and b43legacy. b43 supports most newer Broadcom chipsets, while the b43legacy driver only supports the early BCM4301 and BCM4306 rev.2 chipsets. To avoid erroneous detection of your WiFi card’s chipset, blacklist the unused driver.

Both of these drivers require non-free firmware to function. Install b43-firmware AUR or b43-firmware-classic AUR.

wiki.archlinux.org iwd

iwd (iNet wireless daemon) is a wireless daemon for Linux written by Intel. The core goal of the project is to optimize resource utilization by not depending on any external libraries and instead utilizing features provided by the Linux Kernel to the maximum extent possible.

iwd can work in standalone mode or in combination with comprehensive network managers like ConnMan, systemd-networkd and NetworkManager.

jlk.fjfi.cvut.cz Arch manual pages - iwd.config - Configuration file for wireless daemon

wiki.archlinux.org Iwd#Optional configuration

wiki.archlinux.org systemd-networkd

systemd-networkd is a system daemon that manages network configurations. It detects and configures network devices as they appear; it can also create virtual network devices. This service can be especially useful to set up complex network configurations for a container managed by systemd-nspawn or for virtual machines. It also works fine on simple connections.

The systemd package is part of the default Arch installation and contains all needed files to operate a wired network. Wireless adapters, covered later in this article, can be set up by services, such as wpa_supplicant or iwd.

wiki.archlinux.org/ Systemd-networkd Basic_usage

wiki.archlinux.org Systemd-resolved

wiki.archlinux.org/ Systemd-resolved Installation

systemd-resolved is a part of the systemd package that is installed by default.

wiki.archlinux.org/ Systemd-resolved Configuration

wiki.archlinux.org Listing network interfaces

Both wired and wireless interface names can be found via ls /sys/class/net or ip link. Note that lo is the loop device and not used in making network connections.

Wireless device names can also be retrieved using iw dev. See also /Wireless#Get the name of the interface.

bbs.archlinux.org Index» Networking, Server, and Protection» The IWD thread

wiki.archlinux.org iwd installation and usage notes

Installation:

Install the iwd package.

Usage

The iwd package provides the client program iwctl, the daemon iwd and the Wi-Fi monitoring tool iwmon.

Start/enable iwd.service so it can be controlled using the iwctl command.

iwd.wiki.kernel.org iwd start

Introduction iNet Wireless Daemon (iwd) project aims to provide a comprehensive Wi-Fi connectivity solution for Linux based devices. The core goal of the project is to optimize resource utilization: storage, runtime memory and link-time costs. This is accomplished by not depending on any external libraries and utilizes features provided by the Linux Kernel to the maximum extent possible. The result is a self-contained environment that only depends on the Linux Kernel and the runtime C library.

iwd.wiki.kernel.org iwd

iNet Wireless Daemon (iwd) project aims to provide a comprehensive Wi-Fi connectivity solution for Linux based devices. The core goal of the project is to optimize resource utilization: storage, runtime memory and link-time costs. This is accomplished by not depending on any external libraries and utilizes features provided by the Linux Kernel to the maximum extent possible. The result is a self-contained environment that only depends on the Linux Kernel and the runtime C library.

iwd.wiki.kernel.org Getting Started with iwd

So you want to try out iwd but do not know where to start? You’re in the right place. This document will cover building iwd from source and basic WPA-Personal (pre-shared key) type use cases. For WPA-Enterprise / 802.1X authentication setup, see the relevant topic pages.

Connecting to a Network

For this HOWTO we will be using iwd’s command line client, iwctl, starting it from the iwd build directory. iwctl should be shipped by default with most distributions, so if you are using iwd from a distribution package, you can simply invoke ‘iwctl’.

iwd.wiki.kernel.org iwd Network configuration settings

IWD stores information on known networks, and reads information on pre-provisioned networks, from small text configuration files. Those files live in $LIBDIR/iwd, by default /var/lib/iwd. You can create, modify or remove those files. IWD monitors the directory for changes and will also modify these files in the course of network connections as necessary.

For most up-to-date information on network settings see the iwd.network(5) man page shipped with IWD (source), which incorporates most of this page’s content now.

All Systems Go! youtube iwd - State of the union - Sep 21, 2019

media.ccc.de iwd - State of the union by Marcel Holtmann - 2019-09-21

The Linux Foundation youtube The New Wi-Fi Experience for Linux - Marcel Holtmann, Intel - Oct 25, 2018

All Systems Go! youtube 2017 Update on new WiFi daemon for Linux - Oct 22, 2017

Kai Hendry youtube iwd: a wpa_supplicant alternative for Archers?

wiki.archlinux.org WPA supplicant

wpa_supplicant is a cross-platform supplicant with support for WEP, WPA and WPA2 (IEEE 802.11i). It is suitable for desktops, laptops and embedded systems. It is the IEEE 802.1X/WPA component that is used in the client stations. It implements key negotiation with a WPA authenticator and it controls the roaming and IEEE 802.11 authentication/association of the wireless driver.

w1.fi/ Linux WPA/WPA2/IEEE 802.1X Supplicant

wireless.wiki.kernel.org wpa_supplicant Linux documentation page

wpa_supplicant is a userspace application which works as a WPA supplicant and SME (to handle initiating MLME commands). This page is dedicated only to the documentation relating to the Linux aspects of wpa_supplicant.

wiki.archlinux.org wpa_supplicant

Kernel Parameters

wiki.archlinux.org/ Kernel_module#Blacklisting

cyberciti.biz/ How to view Linux kernel parameters for currently booted system

documentation.commvault.com Kernel Parameters Configuration - Linux

gerardnico.com/ Linux - Kernel parameters (configuration files)

dhcpcd and wpa_supplicant

wiki.archlinux.org WPA supplicant - Connection

Tip:

dhcpcd has a hook that can launch wpa_supplicant implicitly, see dhcpcd#10-wpa_supplicant. While testing arguments/configuration it may be helpful to launch wpa_supplicant in the foreground (i.e. without the -B option) for better debugging messages.

wiki.archlinux.org Dhcpcd#10-wpa_supplicant

Enable this hook by creating a symbolic link, which ensures the current version is used, even after package updates:

         # ln -s /usr/share/dhcpcd/hooks/10-wpa_supplicant /usr/lib/dhcpcd/dhcpcd-hooks/

The 10-wpa_supplicant hook, if enabled, automatically launches WPA supplicant on wireless interfaces. It is started only if:

        no wpa_supplicant process is already listening on that interface.
        a wpa_supplicant configuration file exists. dhcpcd checks
        /etc/wpa_supplicant/wpa_supplicant-interface.conf
        /etc/wpa_supplicant/wpa_supplicant.conf
        /etc/wpa_supplicant-interface.conf
        /etc/wpa_supplicant.conf

Arch Network Configuration