Summary: | net-wireless/wpa_supplicant USE=privsep causes netlink failure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dillon <developer> |
Component: | Current packages | Assignee: | Rick Farina (Zero_Chaos) <zerochaos> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | gentoo, gentoobugs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Output from rc-service; wpa_supplicant fails to start with USE=privsep |
Description
Dillon
2022-05-23 22:10:48 UTC
Please note that this is with USE=privsep and not enabling privsep in configuration when launching manually. The same behaviour is exhibited when launching through networkmanager systemd activation A user in #gentoo on IRC indicated that this problem also exists when using iwlwifi, so perhaps it is not driver-dependent. Created attachment 895086 [details]
Output from rc-service; wpa_supplicant fails to start with USE=privsep
I can confirm that USE=privsep on net-wireless/wpa_supplicant prevents proper wireless operation on an amd64 OpenRC system, using both the stable amd64 version (2.10-r4) and the ~amd64 version (2.10-r5). I use netifrc to start wpa_supplicant in my case, and my wifi driver is iwlwifi if that's relevant. Attached is the output when I try to `rc-service net.wlp0s20f3 restart` on my computer, after building and installing wpa_supplicant with USE=privsep. Please let me know if there's any other output or logs I can include to help bug resolution along and I'll do my best to provide it. Thanks. :) Something interesting I've discovered about this particular bug: it appears to be caused by wpa_supplicant being unable to talk to wpa_priv. I can get wpa_supplicant with USE=privsep to start by doing the following (substitute wlp0s20f3 with your wireless interface). I found these steps by looking at the wpa_priv(8) man page. ``` # groupadd wpapriv # mkdir -m 750 /var/run/wpa_priv # chown root:wpapriv /var/run/wpa_priv # wpa_priv -B -c /var/run/wpa_priv -P /var/run/wpa_priv.pid wext:wlp0s20f3 # useradd -G wpapriv testuser ``` Then, as `testuser`: ``` $ wpa_supplicant -B -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlp0s20f3 Successfully initialized wpa_supplicant ``` What this suggests to me is that wpa_priv might not be getting started the right way when the privsep USE flag is present, or isn't actually getting started at all. When I don't start wpa_priv first, I get the same error messages that I pasted before. |