2018-11-15 21:54:23 +01:00
|
|
|
# Note: The lines starting with # are ignored. To enable any of the
|
|
|
|
# configuration options below, remove # from the beginning of a respective line.
|
|
|
|
|
2016-10-21 23:02:30 +02:00
|
|
|
[EAP]
|
|
|
|
mtu=1400
|
2018-11-15 21:54:23 +01:00
|
|
|
|
2018-04-02 20:47:45 +02:00
|
|
|
[EAPoL]
|
2019-01-10 04:13:53 +01:00
|
|
|
max_4way_handshake_time=5
|
2019-03-19 18:59:08 +01:00
|
|
|
|
|
|
|
[General]
|
2019-09-04 18:21:35 +02:00
|
|
|
|
|
|
|
#
|
|
|
|
# Enable network configuration. Setting this option to 'True' enables iwd to
|
|
|
|
# configure the network interfaces with the IP addresses. There are two types
|
|
|
|
# IP addressing supported by iwd: static and dynamic. The static IP addresses
|
|
|
|
# are configured through the network configuration files located in
|
|
|
|
# '/var/lib/iwd/' directory. For more information on the static configuration
|
|
|
|
# options refer to the wiki page (https://iwd.wiki.kernel.org/ipconfiguration).
|
|
|
|
# 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.
|
|
|
|
#
|
2019-09-16 19:55:27 +02:00
|
|
|
# The network configuration feature is disabled by default.
|
2019-09-04 18:21:35 +02:00
|
|
|
#
|
2019-09-16 19:55:27 +02:00
|
|
|
# enable_network_config=False
|
2019-09-04 18:21:35 +02:00
|
|
|
|
2019-08-29 18:58:54 +02:00
|
|
|
#
|
2019-09-04 18:21:36 +02:00
|
|
|
# Indicate a DNS resolution method used by the system. This configuration option
|
|
|
|
# must be used in conjunction with 'enable_network_config'. The currently
|
|
|
|
# supported methods include: systemd-resolved and the resolv.conf based options
|
|
|
|
# (such as openresolv, etc).
|
|
|
|
# The following configuration 'dns_resolve_method' options are supported:
|
|
|
|
# systemd
|
|
|
|
# resolvconf
|
|
|
|
#
|
|
|
|
# If not specified, 'systemd' is used as default.
|
|
|
|
#
|
|
|
|
# dns_resolve_method=systemd
|
|
|
|
#
|
|
|
|
|
2019-02-18 18:30:42 +01:00
|
|
|
#
|
|
|
|
# Enable/Disable sending EAPoL packets over NL80211. Enabled by default if
|
|
|
|
# kernel support is available. Doing so sends all EAPoL traffic over directly
|
|
|
|
# to the supplicant process (iwd) instead of putting these on the Ethernet
|
|
|
|
# device. Since only the supplicant can usually make sense / decrypt these
|
|
|
|
# packets, enabling this option can save some CPU cycles on your system and
|
|
|
|
# avoids certain long-standing race conditions.
|
|
|
|
#
|
|
|
|
# Note, iwmon cannot currently spy on unicast packets sent over netlink, so
|
|
|
|
# if you need to capture EAPoL packets (e.g. for debugging) then this option
|
|
|
|
# should be set to False.
|
2019-07-30 21:36:50 +02:00
|
|
|
control_port_over_nl80211=True
|
2019-03-21 16:54:04 +01:00
|
|
|
#
|
2019-07-30 21:36:46 +02:00
|
|
|
# Set the threshold RSSI for roaming (default -70)
|
2019-03-21 16:54:04 +01:00
|
|
|
roam_rssi_threshold=-70
|
2019-05-02 17:46:54 +02:00
|
|
|
#
|
|
|
|
# Do not allow iwd to destroy / recreate wireless interfaces at startup,
|
|
|
|
# including default interfaces. Enable this behavior if your wireless card
|
|
|
|
# driver is buggy or does not allow such an operation, or if you do not want
|
|
|
|
# iwd to manage netdevs for another reason. For most users with an upstream
|
|
|
|
# driver it should be safe to omit/disable this setting.
|
|
|
|
# use_default_interface=true
|
2018-11-15 21:54:23 +01:00
|
|
|
|
2019-06-11 01:27:40 +02:00
|
|
|
#
|
|
|
|
# Explicitly enforce/disable management frame protection
|
|
|
|
#
|
|
|
|
# 0 - Disable management frame protection
|
2019-07-30 21:36:46 +02:00
|
|
|
# 1 - Set management frame protection capable (default)
|
2019-06-11 01:27:40 +02:00
|
|
|
# 2 - Management frame protection required
|
|
|
|
#
|
2019-07-30 21:36:48 +02:00
|
|
|
# management_frame_protection=1
|
2019-06-11 01:27:40 +02:00
|
|
|
|
2019-06-26 19:42:54 +02:00
|
|
|
#
|
|
|
|
# Enable/disable ANQP queries. The way IWD does ANQP queries is dependent on
|
2019-08-28 19:33:22 +02:00
|
|
|
# a recent kernel patch (available in Kernel 5.3). If your kernel does not have
|
|
|
|
# this functionality this should be disabled (default). Some drivers also do a
|
|
|
|
# terrible job of sending public action frames (freezing or crashes) which is
|
|
|
|
# another reason why this has been turned off by default. All aside, if you want
|
|
|
|
# to connect to Hotspot 2.0 networks ANQP is most likely going to be required
|
|
|
|
# (you may be able to pre-provision to avoid ANQP).
|
2019-06-26 19:42:54 +02:00
|
|
|
#
|
|
|
|
# disable_anqp=true
|
|
|
|
|
2019-07-01 23:07:23 +02:00
|
|
|
#
|
|
|
|
# Control the behavior of MAC address randomization by setting the
|
|
|
|
# mac_randomize option. iwd supports the following options:
|
|
|
|
# "default" - Lets the kernel assign a mac address from the permanent mac
|
|
|
|
# address store when the interface is created by iwd. Alternatively,
|
|
|
|
# if the 'use_default_interface' is set to true, then the mac address is
|
|
|
|
# not touched.
|
|
|
|
# "once" - MAC address is randomized once when iwd starts. If
|
|
|
|
# 'use_default_interface' is set to true, only the interface(s) managed
|
|
|
|
# by iwd will be randomized.
|
|
|
|
#
|
|
|
|
# One can control which part of the address is randomized using
|
|
|
|
# mac_randomize_bytes option. iwd supports the following options:
|
|
|
|
# "nic" - Randomize only the NIC specific octets (last 3 octets). Note that
|
|
|
|
# the randomization range is limited to 00:00:01 to 00:00:FE. The permanent
|
|
|
|
# mac address of the card is used for the initial 3 octets.
|
|
|
|
# "full" - Randomize the full 6 octets. The locally-administered bit will
|
|
|
|
# be set.
|
|
|
|
#
|
|
|
|
# mac_randomize=default
|
|
|
|
# mac_randomize_bytes=full
|
|
|
|
|
2018-11-15 21:54:23 +01:00
|
|
|
[Scan]
|
|
|
|
#
|
|
|
|
# Disable periodic scan. Setting this option to 'true' will prevent iwd from
|
|
|
|
# issuing the periodic scans for the available networks while disconnected.
|
|
|
|
# The behavior of the user-initiated scans isn't affected.
|
|
|
|
# The periodic scan is enabled by default.
|
2019-07-30 21:36:46 +02:00
|
|
|
#
|
|
|
|
# disable_periodic_scan=false
|
2019-01-16 04:14:57 +01:00
|
|
|
#
|
|
|
|
|
2019-04-02 01:23:03 +02:00
|
|
|
#
|
|
|
|
# Disable roaming scan. Setting this option to 'true' will prevent iwd from
|
|
|
|
# issuing the roaming scans for the available networks while connected.
|
|
|
|
# The behavior of the user-initiated scans isn't affected.
|
|
|
|
# The roaming scan is enabled by default.
|
2019-07-30 21:36:46 +02:00
|
|
|
#
|
|
|
|
# disable_roaming_scan=false
|
2019-04-02 01:23:03 +02:00
|
|
|
#
|
|
|
|
|
2019-01-16 04:14:57 +01:00
|
|
|
#
|
|
|
|
# Disable MAC address randomization. Setting this option to 'true' will prevent
|
|
|
|
# the capable network adapters from randomizing MAC addresses during the active
|
|
|
|
# scans for networks, thus decreasing user privacy.
|
|
|
|
# The MAC address randomization is enabled by default.
|
2019-07-30 21:36:46 +02:00
|
|
|
#
|
|
|
|
# disable_mac_address_randomization=false
|
2019-01-16 04:14:57 +01:00
|
|
|
#
|
2019-01-24 21:56:25 +01:00
|
|
|
|
|
|
|
[Blacklist]
|
|
|
|
#
|
|
|
|
# Configure BSS blacklist time/multipler/max. If a connection to a BSS fails for
|
|
|
|
# whatever reason we can avoid connecting to this BSS in the future by
|
|
|
|
# blacklisting it. These three options configure how long a BSS is blacklisted
|
|
|
|
# for.
|
|
|
|
#
|
2019-03-16 17:45:40 +01:00
|
|
|
# bss_blacklist_time - The initial timeout for a blacklisted BSS in
|
2019-07-30 21:36:46 +02:00
|
|
|
# seconds (default 60)
|
2019-01-24 21:56:25 +01:00
|
|
|
# bss_blacklist_multiplier - What bss_blacklist_time is multiplied by after
|
2019-03-16 17:45:40 +01:00
|
|
|
# future unsuccessful connection attempts in
|
2019-07-30 21:36:46 +02:00
|
|
|
# seconds (default 30)
|
2019-03-16 17:45:40 +01:00
|
|
|
# bss_blacklist_max_time - The maximum time a BSS can be blacklisted for in
|
2019-07-30 21:36:46 +02:00
|
|
|
# seconds (default 86400)
|
2019-01-24 21:56:25 +01:00
|
|
|
#
|
2019-07-30 21:36:46 +02:00
|
|
|
# bss_blacklist_time=60
|
|
|
|
# bss_blacklist_multiplier=30
|
|
|
|
# bss_blacklist_max_time=86400
|
2019-02-26 19:31:59 +01:00
|
|
|
|
|
|
|
[Rank]
|
|
|
|
#
|
|
|
|
# Manually specify a 5G ranking factor. 5G networks are already preferred but
|
|
|
|
# only in terms of calculated data rate, which is RSSI dependent. This means it
|
|
|
|
# is still possible for IWD to prefer a 2.4GHz AP in the right conditions.
|
|
|
|
# This ranking provides a way to further weight the ranking towards 5G if
|
|
|
|
# required. Also, a lower 5G factor could be used to weight 2.4GHz if that is
|
2019-07-30 21:36:46 +02:00
|
|
|
# desired. The default is 1.0, which does not affect the calculated ranking.
|
2019-02-26 19:31:59 +01:00
|
|
|
#
|
2019-07-30 21:36:46 +02:00
|
|
|
# rank_5g_factor=1.0
|