Arch Linux

digitalone

Member

Registered: 2011-08-19

Posts: 350

Re: The IWD thread

It should work though, no dhcpcd needed. Iwd has an internal dhcp client. Don't give up immediately. Make sure you're using the latest version (0.19 right now) and send the contents of /etc/iwd/main.conf and systemctl status iwd when you've started it with the config file (and without dhcpcd)

It's not working.

0.19 here, boot log:

iwd[430]: Skipping optional configuration file /etc/iwd/main.conf
iwd[430]: netconfig: Network configuration with the IP addresses is disabled

main.conf

[General]
enable_network_config=true

It's ignored.

Last edited by digitalone (2019-08-23 17:30:07)

jpegxguy

Member

From: Earth

Registered: 2018-06-18

Posts: 38

Re: The IWD thread

That's the behavior of iwd when it can't see such a file. How do the permissions look on /etc/iwd and /etc/iwd/main.conf?

Last edited by jpegxguy (2019-08-23 18:11:00)

---

hi

digitalone

Member

Registered: 2011-08-19

Posts: 350

Re: The IWD thread

That's the behavior of iwd when it can see such a file. How do the permissions look on /etc/iwd and /etc/iwd/main.conf?

When it sees the file, does it "skip"?

drwxr-xr-x 2 root root 4096 Aug 23 19:35 /etc/iwd
-rw-r--r-- 1 root root 68 Aug 23 19:35 /etc/iwd/main.conf

It's not even renaming interface as "wlan0". I noticed this behavior in the last days.

Last edited by digitalone (2019-08-23 17:56:13)

jpegxguy

Member

From: Earth

Registered: 2018-06-18

Posts: 38

Re: The IWD thread

It's not even renaming interface as "wlan0". I noticed this behavior in the last days.

If you move main.conf to another location and reboot (assuming iwd is enabled in systemctl) does iwd take control of the interface? AFAIK you can check this because if iwd has taken control of the interface and you kill is process (systemctl stop will do), the interface goes with it as well.

---

hi

digitalone

Member

Registered: 2011-08-19

Posts: 350

Re: The IWD thread

It's not even renaming interface as "wlan0". I noticed this behavior in the last days.

If you move main.conf to another location and reboot (assuming iwd is enabled in systemctl) does iwd take control of the interface? AFAIK you can check this because if iwd has taken control of the interface and you kill is process (systemctl stop will do), the interface goes with it as well.

No, because I created main.conf today and I already had interface name assigned by udev from the last few days. By default iwd should rename it to wlan0, but it's not happening.

Anyway, I returned to use wpa_supplicant to see if I get same issues with networkmanager. Using iwd, sometimes networkmanager loses connection without remembering the password, even if I already set it. That's why I wanted to try iwd alone and wanted to configure it, but I can't.

amish

Member

Registered: 2014-05-10

Posts: 475

Re: The IWD thread

I have been using main.conf with enable_network_config=true from few weeks now and it seems to be working fine. i.e. it is parsing it.

However, IWD does not connect immediately to Wifi AP.

I need to restart iwd 4-5 times and then it will connect.

Very rarely it connects on its own at system boot. (i.e. on first attempt)

digitalone

Member

Registered: 2011-08-19

Posts: 350

Re: The IWD thread

Well, don't know what to say. I tried everything.

Maybe the only difference is that I'm using an USB wifi adapter I bought to replace an Intel wifi card of my laptop which its driver is bugged and causes connection to drop. That's why I tried to use iwd, I though to resolve with it but the issue happened the same. It's a driver issue.

Then I bought an Asus usb adapter that's working better but networkmanager with iwd sometimes loses connection telling me the put the password I already inserted before. Using iwd alone I can't configure it.

I see if the issue will occur with wpa_supplicant, I'd like to keep using networkmanager having plasma-nm applet in the system tray.

Last edited by digitalone (2019-08-24 06:53:33)

jpegxguy

Member

From: Earth

Registered: 2018-06-18

Posts: 38

Re: The IWD thread

Using

iwd 0.18-1
networkmanager 1.18.0-1

Networkmanager actually starts iwd normally without having to enable it in systemctl. Nice.
I wonder if it works with eduroam though. The combination of these 2 didn't work before

This was actually random BTW. To this day I have iwd enabled in order for NetworkManager to play nicely with it. Otherwise I have to restart one of the 2.

https://gitlab.freedesktop.org/NetworkM … issues/101

Last edited by jpegxguy (2019-08-25 01:28:51)

---

hi

SRSR333

Member

Registered: 2019-05-09

Posts: 7

Re: The IWD thread

So, for some reason, iwd refuses to connect to my university's wireless network. In iwctl, I can scan for, and attempt to connect to the network, but after exiting iwctl and sending a ping to google.com, I receive an error.

The output of journalctl -b | grep iwd after attempting to connect:

Aug 26 10:34:04 archlinux iwd[753]: EAP server tried method 13 while client was configured for method 25
Aug 26 10:34:04 archlinux iwd[753]: PEAP: Tunnel has disconnected with alert: close_notify
Aug 26 10:34:09 archlinux iwd[753]: 4-Way handshake failed for ifindex: 4, reason: 15
Aug 26 10:34:09 archlinux iwd[753]: EAP server tried method 13 while client was configured for method 25
Aug 26 10:34:09 archlinux iwd[753]: PEAP: Tunnel has disconnected with alert: close_notify
Aug 26 10:34:14 archlinux iwd[753]: 4-Way handshake failed for ifindex: 4, reason: 15
Aug 26 10:34:14 archlinux iwd[753]: EAP server tried method 13 while client was configured for method 25
Aug 26 10:34:14 archlinux iwd[753]: PEAP: Tunnel has disconnected with alert: close_notify
Aug 26 10:34:19 archlinux iwd[753]: 4-Way handshake failed for ifindex: 4, reason: 15
Aug 26 10:34:20 archlinux iwd[753]: authentication timed out
Aug 26 10:34:20 archlinux iwd[753]: authentication timed out
Aug 26 10:34:20 archlinux iwd[753]: authentication timed out

My network's configuration file located in /var/lib/iwd/SSID.8021x (personal information obfuscated):

[Security]
EAP-Method=PEAP
EAP-Identity=anonymous
#EAP-PEAP-CACert=/path/to/cert.pem
EAP-PEAP-Phase2-Method=MSCHAPV2
EAP-PEAP-Phase2-Identity=domain\\user

[Settings]
Autoconnect=true

Otherwise, my entire network stack has only got three services running: systemd-networkd, systemd-resolved, and this, iwd. I was hoping to simply the bloat of NetworkManager + wpa_supplicant + dhcpcd + netctl and so on.

Does anyone know how I might contact the developers for further information? Thanks

progandy

Member

Registered: 2012-05-17

Posts: 5,263

Re: The IWD thread

iwd is located here:
https://git.kernel.org/pub/scm/network/ … git/about/
Mailing list:     https://lists.01.org/mailman/listinfo/iwd
IRC:    irc://irc.freenode.net/#iwd

Last edited by progandy (2019-08-26 07:42:34)

---

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Stellarator

Member

Registered: 2019-01-12

Posts: 32

Re: The IWD thread

So, for some reason, iwd refuses to connect to my university's wireless network. In iwctl, I can scan for, and attempt to connect to the network, but after exiting iwctl and sending a ping to google.com, I receive an error.

Check this and try to play with EAP-Method. I would recommend starting with:

[Security]
EAP-Method=TTLS
EAP-TTLS-CACert=/path/to/cert.pem
EAP-TTLS-Phase2-Method=MSCHAPV2
EAP-TTLS-Phase2-Identity=...
EAP-TTLS-Phase2-Password=...

SRSR333

Member

Registered: 2019-05-09

Posts: 7

Re: The IWD thread

Check this and try to play with EAP-Method. I would recommend starting with:

[Security]
EAP-Method=TTLS
EAP-TTLS-CACert=/path/to/cert.pem
EAP-TTLS-Phase2-Method=MSCHAPV2
EAP-TTLS-Phase2-Identity=...
EAP-TTLS-Phase2-Password=...

Works like a charm! Thank you very much.

Would you mind explaining why setting EAP-TTLS works, while EAP-PEAP doesn’t, even though the network configuration guide for my university’s network state that it’s supposed to be PEAP?

Last edited by SRSR333 (2019-08-26 16:18:30)

digitalone

Member

Registered: 2011-08-19

Posts: 350

Re: The IWD thread

Running wpa_supplicant from 3 days and no disconnection issues with networkmanager. I have to stay to wpa_supplicant since iwd were causing connection to drop asking me the password that I already inserted. Tried also to run iwd alone (disabling networkmanager), but I couldn't configure it because /etc/iwd/main.conf file was not parsed by the daemon which I enabled at boot. Maybe it's an incompatibility issue between iwd and usb wifi adapters since iwd was not even renaming interface name to wlan0 as it should do by default.

I'm sorry to say that, but iwd on my system is not a better replacement of wpa_supplicant. I orphaned networkmanager-iwd on AUR, feel free to adopt it if you want.

Stellarator

Member

Registered: 2019-01-12

Posts: 32

Re: The IWD thread

Would you mind explaining why setting EAP-TTLS works, while EAP-PEAP doesn’t, even though the network configuration guide for my university’s network state that it’s supposed to be PEAP?

I can assume the obvious thing - outdated KB guide/article or something. Both types of encapsulation are quite (most?) popular (with the caveat that EAP-TTLS is not supported on Windows 7 or less). Therefore, I mean that some kind of transition occurred in your network, which was not reflected in the documentation in a timely manner.

Interestingly, the daemon gives a hint:

iwd[753]: EAP server tried method 13 while client was configured for method 25

This info is a bit cryptic but with some effort you can understand what is going on.

It would be nice if the daemon could adapt to the server’s responses, especially since your case is quite typical (or am I wrong?) and the daemon already has all the necessary information in the config (CACert, Phase2-Method, Phase2-Identity, Phase2-Password) to proceed with different encapsulation protocol (or at least try to do so). But it seems like no one has thought about it yet (here I can also be wrong, because I am not involved in the project at the proper level).

maxplayer

Member

Registered: 2019-08-28

Posts: 1

Re: The IWD thread

had issue with the latest version of iwd 0.19-1 on my x201 laptop

02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)

[ 5074.706361] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
[ 5074.947940] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
[ 5089.390751] wlan0: authenticate with 3c:28:6d:75:c0:bd
[ 5089.393587] wlan0: send auth to 3c:28:6d:75:c0:bd (try 1/3)
[ 5089.409481] wlan0: authenticated
[ 5089.412699] wlan0: associate with 3c:28:6d:75:c0:bd (try 1/3)
[ 5089.415170] wlan0: RX AssocResp from 3c:28:6d:75:c0:bd (capab=0x1011 status=0 aid=3)
[ 5089.418158] wlan0: associated
[ 5089.430669] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 5089.510298] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 3c:28:6d:75:c0:bd
[ 5090.081133] iwd[2865]: segfault at 73824f01018b ip 0000563935acbcd9 sp 00007ffd49729e38 error 4 in iwd[563935a53000+7f000]
[ 5090.081219] audit: type=1701 audit(1567026126.692:101): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=2865 comm="iwd" exe="/usr/lib/iwd/iwd" sig=11 res=1
[ 5090.408177] audit: type=1131 audit(1567026127.019:103): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 5090.420367] wlan0: deauthenticating from 3c:28:6d:75:c0:bd by local choice (Reason: 3=DEAUTH_LEAVING)
[ 5090.672378] audit: type=1130 audit(1567026127.282:105): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5090.672595] audit: type=1131 audit(1567026127.282:106): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5090.693941] audit: type=1130 audit(1567026127.305:107): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

I got connected, and right after disconnected, falling back to iwd 0.18-2 got it back stabled

a new Upstream commit has just been done for 0.20 i will give it a try once released for arch

patrickmcnamara

Member

From: Dublin, Ireland

Registered: 2019-08-29

Posts: 2

Website

Re: The IWD thread

Since 0.20, iwd is renaming my network interfaces despite the "use_default_interface=true" option in my config. If anyone knows a fix, it would be appreciated.

Moo-Crumpus

Member

From: Hessen / Germany

Registered: 2003-12-01

Posts: 1,488

Re: The IWD thread

Can someone help me with this result of systemctl status iwd:

Aug 31 11:14:33 hostname iwd[5865]:         Bands: 2.4 GHz 5 GHz
Aug 31 11:14:33 hostname iwd[5865]:         Ciphers: CCMP TKIP BIP
Aug 31 11:14:33 hostname iwd[5865]:         Supported iftypes: ad-hoc station
Aug 31 11:14:33 hostname iwd[5865]: No control_port_over_nl80211 setting, defaulting to True
Aug 31 11:14:33 hostname iwd[5865]: Could not register frame watch type 00d0: -95
Aug 31 11:14:33 hostname iwd[5865]: Could not register frame watch type 00d0: -95
Aug 31 11:14:33 hostname iwd[5865]: Could not register frame watch type 00d0: -95
Aug 31 11:14:33 hostname iwd[5865]: Received error during CMD_TRIGGER_SCAN: Invalid argument (22)
Aug 31 11:14:33 hostname iwd[5865]: Could not register frame watch type 00d0: -95
Aug 31 11:14:33 hostname iwd[5865]: Received error during CMD_TRIGGER_SCAN: Invalid argument (22)

---

Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]

Moo-Crumpus

Member

From: Hessen / Germany

Registered: 2003-12-01

Posts: 1,488

Re: The IWD thread

... and what about this? Weird.

                                
[iwd]# station wlan0 show
                                 Station: wlan0                                
--------------------------------------------------------------------------------
  Settable  Property            Value                                          
--------------------------------------------------------------------------------
            Scanning            no
            State               disconnected

[iwd]# station wlan0 scan 
Argument type is wrong             

---

Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]

Kakashiy

Member

Registered: 2018-01-31

Posts: 13

Re: The IWD thread

Hello I've also got Problems with my iwd setup (WPA Enterprise)

Sep 23 10:38:26 ArchLinuxLaptop systemd[1]: Starting Wireless service...
Sep 23 10:38:26 ArchLinuxLaptop iwd[472]: Wireless daemon version 0.20
Sep 23 10:38:26 ArchLinuxLaptop iwd[472]: netconfig: Network configuration with the IP addresses is disabled.
Sep 23 10:38:26 ArchLinuxLaptop systemd[1]: Started Wireless service.
Sep 23 10:38:26 ArchLinuxLaptop iwd[472]: Wiphy phy0 will only use the default interface
Sep 23 10:38:26 ArchLinuxLaptop iwd[472]: Wiphy: 0, Name: phy0
Sep 23 10:38:26 ArchLinuxLaptop iwd[472]:         Permanent Address: XX:XX:XX:XX:XX:XX
Sep 23 10:38:26 ArchLinuxLaptop iwd[472]:         Bands: 2.4 GHz 5 GHz
Sep 23 10:38:26 ArchLinuxLaptop iwd[472]:         Ciphers: CCMP TKIP BIP
Sep 23 10:38:26 ArchLinuxLaptop iwd[472]:         Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
Sep 23 10:38:26 ArchLinuxLaptop iwd[472]: No control_port_over_nl80211 setting, defaulting to True
Sep 23 10:38:33 ArchLinuxLaptop iwd[472]: 4-Way handshake failed for ifindex: 2, reason: 15
Sep 23 10:38:38 ArchLinuxLaptop iwd[472]: 4-Way handshake failed for ifindex: 2, reason: 15
Sep 23 10:38:45 ArchLinuxLaptop iwd[472]: 4-Way handshake failed for ifindex: 2, reason: 15
Sep 23 10:38:45 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:46 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 5, from_ap: true
Sep 23 10:38:47 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 5, from_ap: true
Sep 23 10:38:48 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 7, from_ap: true
Sep 23 10:38:49 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:50 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:51 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:52 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:52 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:53 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:54 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:55 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:56 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:57 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:58 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:38:59 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 7, from_ap: true
Sep 23 10:39:00 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:39:01 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true
Sep 23 10:39:02 ArchLinuxLaptop iwd[472]: Received Deauthentication event, reason: 3, from_ap: true

Config:

[Security]
EAP-Method=TTLS
EAP-TTLS-CACert=/etc/ssl/certs/T-TeleSec_GlobalRoot_Class_2.pem
EAP-Itendity=eduroam@ruhr-uni-bochum.de
EAP-TTLS-Phase2-Method=Tunneled-PAP
EAP-TTLS-Phase2-Identity=...@ruhr-uni-bochum.de
EAP-TTLS-Phase2-Password=....

[Settings]
Autoconnect=True

and according to http://www.noc.rub.de/web/wlan it should be correct.

I've no idea whats wrong wpa_supplicant works without any problems but its slow

ormsgard

Member

Registered: 2018-08-08

Posts: 1

Re: The IWD thread

Anybody else has trouble with the built-in dhcp server? (version 0.21 and 0.22)

If I run with this main.conf:

[General]
enable_network_config=true
dns_resolve_method=systemd

I'll get this error when restarting the wifi after switching it off:

netconfig: Failed to re-start DHCPv4 client for interface 6

(the number of interface varies).

Everything works if I remove enable_network_config and use the external dhcpd.

digitalone

Member

Registered: 2011-08-19

Posts: 350

Re: The IWD thread

Tried this morning to test the latest version of iwd, which I dropped two months ago due to some issues.
Used with networkmanager and I got a random disconnection after one hour. Never happened with wpa_supplicant. The road is still long.

Mortimer Houghton

Member

Registered: 2014-09-28

Posts: 88

Re: The IWD thread

Does anyone know how to get IWD to play nice with linux-5.3.*?  When I use it with anything higher than 5.2.14 it fails to discover any networks.  This is the error I am getting:

Oct 29 18:06:51 HP-255-G6 iwd[499]: Wireless daemon version 0.23
Oct 29 18:06:51 HP-255-G6 iwd[499]: Loaded configuration from /etc/iwd/main.conf
Oct 29 18:06:51 HP-255-G6 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 29 18:06:51 HP-255-G6 kernel: audit: type=1130 audit(1572390411.625:20): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 29 18:06:51 HP-255-G6 iwd[499]: Wiphy: 0, Name: phy0
Oct 29 18:06:51 HP-255-G6 iwd[499]:         Permanent Address: c0:b6:f9:af:47:c7
Oct 29 18:06:51 HP-255-G6 iwd[499]:         Bands: 2.4 GHz 5 GHz
Oct 29 18:06:51 HP-255-G6 iwd[499]:         Ciphers: CCMP TKIP
Oct 29 18:06:51 HP-255-G6 iwd[499]:         Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
Oct 29 18:06:52 HP-255-G6 audit[499]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=499 comm="iwd" exe="/usr/lib/iwd/iwd" sig=11 res=1
Oct 29 18:06:52 HP-255-G6 iwd[499]: Received error during CMD_TRIGGER_SCAN: Input/output error (5)
Oct 29 18:06:52 HP-255-G6 systemd[1]: iwd.service: Main process exited, code=dumped, status=11/SEGV
Oct 29 18:06:52 HP-255-G6 systemd[1]: iwd.service: Failed with result 'core-dump'.
Oct 29 18:06:52 HP-255-G6 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 29 18:06:52 HP-255-G6 systemd-coredump[777]: Process 499 (iwd) of user 0 dumped core.
                                                 #0  0x000055e7ad3ab733 n/a (iwd)
                                                 #1  0x000055e7ad3ac6c7 n/a (iwd)
                                                 #7  0x000055e7ad38f662 n/a (iwd)
                                                 #9  0x000055e7ad38fdce n/a (iwd)

Adapter:

Intel Dual Band Wireless-AC 3168NGW [Stone Peak]

alu1

Member

Registered: 2014-05-16

Posts: 19

Re: The IWD thread

i've been using iwd since v0.5 with no problems.

as of today v0.23, starting iwd with stock systemd unit, it fails with result core-dump.

rolling back to v0.22-3 has the same result.

v0.22-1 and prior work fine.

the only thing i can see of relevance that got upgraded yesterday was dhcpcd (8.0.6-1 -> 8.1.1-1), but rolling that back and using iwd v0.23 still fails.

i have the stock iwd systemd unit file and main.conf (i live with iwd renaming wlo1 to wlan0).

any ideas?

progandy

Member

Registered: 2012-05-17

Posts: 5,263

Re: The IWD thread

alu1, As of today iwd v1.0 is in the community repo. DId you try that?

---

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

sammynx

Member

Registered: 2013-02-10

Posts: 1

Re: The IWD thread

FYI I had the same issue with iwd 0.23. Just updated to iwd 1.03 and it works fine again.