Bug 21828 - wpa_supplicant per interface
Summary: wpa_supplicant per interface
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard: MGA6TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-10 15:29 CEST by Frederik Vos
Modified: 2023-10-21 22:24 CEST (History)
2 users (show)

See Also:
Source RPM: wpa_supplicant, systemd,
CVE:
Status comment:


Attachments

Description Frederik Vos 2017-10-10 15:29:41 CEST
First of all, i know that it's not the default way to configure wireless interfaces, but maybe it's a nice idea to create wpa_supplicant service file per device as an option. So you have the choice between /etc/sysconfig/wpa_supplicant and this one.

$ cat /etc/systemd/system/wpa_supplicant@.service

[Unit]
Description=WPA Unit
Before=network.target
Wants=network.target
Requires=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device dbus.service 

[Service]
Type=simple
ExecStart=/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant-%i.conf -i %i

[Install]
Alias=multi-user.target.wants/wpa_supplicant@%i.service
Comment 1 Marja Van Waes 2017-10-10 18:58:08 CEST
Assigning to the wpa_supplicant maintainer to decide what to do with this enhancement request.

@ tmb

As of today, most users no longer have unrestricted edit rights in our Bugzilla. Also, the bugs they file will be set to "UNCONFIRMED" by default.

Enhancement requests aren't usually about bugs that need to be confirmed, but I'll leave changing the status to NEW (or to whatever you prefer), because don't understand enough about networking to understand this request.

Source RPM: (none) => wpa_supplicant, systemd,
Whiteboard: (none) => MGA6TOO
Version: 6 => Cauldron
CC: (none) => marja11
Assignee: bugsquad => tmb

Comment 2 Frederik Vos 2017-10-11 08:12:47 CEST
@ Marja,
What I really like about Mageia is that it's already using systemd-networkd/systemd-resolved, but is also using the /etc/init.d/network script.
It's relatively easy to migrate to systemd only, Mageia is extremely flexible!
The only problem here is wireless, the wpa_supplicant service unit file is configured to work with NetworkManager, and can not be used together with systemd-networkd. However, there is no reason to remove this file, if you add a wpa_supplicant service unit that works per network interface. 
If you have more questions, just mail me.

Greetings from the Netherlands :)
Comment 3 Marja Van Waes 2017-10-11 13:14:56 CEST
s/UNCONFIRMED/NEW/ because I understand this enhancement request is needed to solve bug 17706

@ Frederik
Greetings back from the Netherlands ;-)

Status: UNCONFIRMED => NEW
Ever confirmed: 0 => 1
Blocks: (none) => 17706

Comment 4 w unruh 2018-02-17 22:03:14 CET
I do not see how this request is required to solve bug 17706. It would be an enhancement there too. The main problem in 17706 is that Mageia Network Center still uses iwlist rather than iw to discovering networks.

CC: (none) => unruh

Comment 5 Marja Van Waes 2023-10-21 22:24:21 CEST
(In reply to w unruh from comment #4)
> I do not see how this request is required to solve bug 17706. It would be an
> enhancement there too. The main problem in 17706 is that Mageia Network
> Center still uses iwlist rather than iw to discovering networks.

Sorry, hadn't seen this comment. You are right! I have no idea what I thought when I set 17706 to depend on this report.

Blocks: 17706 => (none)


Note You need to log in before you can comment on or make changes to this bug.