[TW] Trying to get wpa_supplicant working
System is Tumbleweed with KDE Plasma desktop. I have been following the "Network Manager and my 'Use Case' thread with interest and have managed to setup a working ethernet network connection using systemd-networkd, thanks to the examples posted there. I also have a wireless card in this computer, and was using Network Manager to manage both wired and wireless connections. Now that I have disabled Network Manager, I would like to find a similar systemd-networkd solution for my wireless card. I believe I have to use wpa_supplicant to communicate passwords etc with the router, followed by the systemd-networkd configuration. I have created /etc/wpa_supplicant.conf --- ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel # home network; allow all valid ciphers network={ ssid="Hillingdon Wi-Fi" <== Name as seen by mobile phone, for example scan_ssid=1 key_mgmt=WPA-PSK psk="my-wifi-password" <=== not the real password } --- But when I do # wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -d wpa_supplicant v2.10 Successfully initialized wpa_supplicant Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf' Reading configuration file '/etc/wpa_supplicant.conf' ctrl_interface='/var/run/wpa_supplicant' ctrl_interface_group='wheel' Priority group 0 id=0 ssid='Hillingdon Wi-Fi' Could not read interface wlan0 flags: No such device nl80211: Driver does not support authentication/association or connect commands nl80211: deinit ifname=wlan0 disabled_11b_rates=0 nl80211: Remove monitor interface: refcount=0 netlink: Operstate: ifindex=0 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP) Could not read interface wlan0 flags: No such device wlan0: Failed to initialize driver interface Failed to add interface wlan0 wlan0: Cancelling scan request wlan0: Cancelling authentication timeout Off-channel: Clear pending Action frame TX (pending_action_tx=(nil) QM: Clear all active DSCP policies wlan0: CTRL-EVENT-DSCP-POLICY clear_all There seem to be two problems: 1. No such device (fatal!) 2. Driver does not support authentication - but NM succeeded in setting up a connection. Can anyone suggest what I'm missing here, please? TIA -- Bob Williams No HTML please. Plain text preferred. https://useplaintext.email/
On Thu, 27 Apr 2023 13:36:56 +0300 Andrei Borzenkov wrote:
On Thu, Apr 27, 2023 at 12:51 PM Bob Williams <usenet@karmasailing.uk> wrote:
Could not read interface wlan0 flags: No such device
Are you sure your interface is called wlan0?
No. It could be wlp2s0. Ah, that works. Thank you. Does wpa_supplicant start automatically during the boot sequence, or do I have to enable it? -- Bob Williams No HTML please. Plain text preferred. https://useplaintext.email/
On Thu, Apr 27, 2023 at 3:01 PM Bob Williams <usenet@karmasailing.uk> wrote:
On Thu, 27 Apr 2023 13:36:56 +0300 Andrei Borzenkov wrote:
On Thu, Apr 27, 2023 at 12:51 PM Bob Williams <usenet@karmasailing.uk> wrote:
Could not read interface wlan0 flags: No such device
Are you sure your interface is called wlan0?
No. It could be wlp2s0. Ah, that works. Thank you.
Does wpa_supplicant start automatically during the boot sequence, or do I have to enable it?
Hopefully experts recommending you systemd-networkd will provide the necessary guidance.
On Thu, 27 Apr 2023, 14:03:49 +0200, Andrei Borzenkov wrote:
On Thu, Apr 27, 2023 at 3:01 PM Bob Williams <usenet@karmasailing.uk> wrote:
On Thu, 27 Apr 2023 13:36:56 +0300 Andrei Borzenkov wrote:
On Thu, Apr 27, 2023 at 12:51 PM Bob Williams <usenet@karmasailing.uk> wrote:
Could not read interface wlan0 flags: No such device
Are you sure your interface is called wlan0?
No. It could be wlp2s0. Ah, that works. Thank you.
Does wpa_supplicant start automatically during the boot sequence, or do I have to enable it?
Hopefully experts recommending you systemd-networkd will provide the necessary guidance.
I don't actually recommend using systemd-networkd for WiFi, but this page might help: https://wiki.somlabs.com/index.php/Connecting_to_WiFi_network_using_systemd_... HTH, cheers. l8er manfred
On Thu, 27 Apr 2023 14:16:01 +0200 Manfred Hollstein wrote:
On Thu, 27 Apr 2023, 14:03:49 +0200, Andrei Borzenkov wrote:
On Thu, Apr 27, 2023 at 3:01 PM Bob Williams <usenet@karmasailing.uk> wrote:
On Thu, 27 Apr 2023 13:36:56 +0300 Andrei Borzenkov wrote:
On Thu, Apr 27, 2023 at 12:51 PM Bob Williams <usenet@karmasailing.uk> wrote:
Could not read interface wlan0 flags: No such device
Are you sure your interface is called wlan0?
No. It could be wlp2s0. Ah, that works. Thank you.
Does wpa_supplicant start automatically during the boot sequence, or do I have to enable it?
Hopefully experts recommending you systemd-networkd will provide the necessary guidance.
I don't actually recommend using systemd-networkd for WiFi, but this page might help:
https://wiki.somlabs.com/index.php/Connecting_to_WiFi_network_using_systemd_...
HTH, cheers.
l8er manfred
Thank you. Yes, that page helps. Any particular reason not to recommend systemd-networkd for wifi? -- Bob Williams No HTML please. Plain text preferred. https://useplaintext.email/
Hi Bob, On Thu, 27 Apr 2023, 14:25:14 +0200, Bob Williams wrote:
On Thu, 27 Apr 2023 14:16:01 +0200 Manfred Hollstein wrote:
On Thu, 27 Apr 2023, 14:03:49 +0200, Andrei Borzenkov wrote:
On Thu, Apr 27, 2023 at 3:01 PM Bob Williams <usenet@karmasailing.uk> wrote:
On Thu, 27 Apr 2023 13:36:56 +0300 Andrei Borzenkov wrote:
On Thu, Apr 27, 2023 at 12:51 PM Bob Williams <usenet@karmasailing.uk> wrote:
Could not read interface wlan0 flags: No such device
Are you sure your interface is called wlan0?
No. It could be wlp2s0. Ah, that works. Thank you.
Does wpa_supplicant start automatically during the boot sequence, or do I have to enable it?
Hopefully experts recommending you systemd-networkd will provide the necessary guidance.
I don't actually recommend using systemd-networkd for WiFi, but this page might help:
https://wiki.somlabs.com/index.php/Connecting_to_WiFi_network_using_systemd_...
HTH, cheers.
l8er manfred
Thank you. Yes, that page helps.
great!
Any particular reason not to recommend systemd-networkd for wifi?
Well, I have a different use-case. When I'm in my home network all systems are connected via cable. I only use WiFi when I'm travelling, which I then cover with NetworkManager. HTH, cheers. l8er manfred
On Thu, Apr 27, 2023 at 3:25 PM Bob Williams <usenet@karmasailing.uk> wrote:
Any particular reason not to recommend systemd-networkd for wifi?
Lack of end-user UI (in particular, to switch between AP), need to manually maintain multiple configuration files for multiple applications. At the end you are using the same wpa_supplicant anyway so the better question is - why would anyone recommend *replacing* NetworkManager with systemd-networkd? What is missing in NetworkManager?
On Thu, 27 Apr 2023, 14:43:25 +0200, Andrei Borzenkov wrote:
[...] At the end you are using the same wpa_supplicant anyway so the better question is - why would anyone recommend *replacing* NetworkManager with systemd-networkd? What is missing in NetworkManager?
I always failed to bring up a bridge interface in NetworkManager. In the end I gave up when it worked absolutely flawlessly using systemd-networkd, which I now use exclusively for my cable network, while NetworkManager is used for WiFi only. Cheers. l8er manfred
On Thu, Apr 27, 2023 at 4:11 PM Manfred Hollstein <mhollstein@t-online.de> wrote:
On Thu, 27 Apr 2023, 14:43:25 +0200, Andrei Borzenkov wrote:
[...] At the end you are using the same wpa_supplicant anyway so the better question is - why would anyone recommend *replacing* NetworkManager with systemd-networkd? What is missing in NetworkManager?
I always failed to bring up a bridge interface in NetworkManager. In the
OK, that would be a reason. Strange, bridge has been supported by NetworkManager for years so I can only think of another matching connection profile that gets activated in preference. But whatever works for you.
end I gave up when it worked absolutely flawlessly using systemd-networkd, which I now use exclusively for my cable network, while NetworkManager is used for WiFi only.
So you did not really *replace* it :)
On Thu, 27 Apr 2023, 15:46:49 +0200, Andrei Borzenkov wrote:
On Thu, Apr 27, 2023 at 4:11 PM Manfred Hollstein <mhollstein@t-online.de> wrote:
[...] end I gave up when it worked absolutely flawlessly using systemd-networkd, which I now use exclusively for my cable network, while NetworkManager is used for WiFi only.
So you did not really *replace* it :)
I never said that ;) Cheers. l8er manfred
On Thu, 27 Apr 2023 15:43:25 +0300 Andrei Borzenkov wrote:
On Thu, Apr 27, 2023 at 3:25 PM Bob Williams <usenet@karmasailing.uk> wrote:
Any particular reason not to recommend systemd-networkd for wifi?
Lack of end-user UI (in particular, to switch between AP), need to manually maintain multiple configuration files for multiple applications.
At the end you are using the same wpa_supplicant anyway so the better question is - why would anyone recommend *replacing* NetworkManager with systemd-networkd? What is missing in NetworkManager?
Nothing is missing in Network Manager. I am trying to learn about systemd, as it is evidently here to stay. I have already switched all my cronjobs to systemd timers, so this is my next systemd project. One of the benefits of Linux is that home users like me can tinker under the bonnet (hood in US parlance) and still revert to safe and tested methods if things don't work. -- Bob Williams No HTML please. Plain text preferred. https://useplaintext.email/
participants (3)
-
Andrei Borzenkov -
Bob Williams -
Manfred Hollstein