[Bug 860885] New: wpa_supplicant, ap mode is not supported
https://bugzilla.novell.com/show_bug.cgi?id=860885 https://bugzilla.novell.com/show_bug.cgi?id=860885#c0 Summary: wpa_supplicant, ap mode is not supported Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: epistemepromeneur@free.fr QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 with kde settings/network i create an ap with my wifi adapter then in plasmoid-management i click on the ap to activate it then i fill the root password then ok then nothing happens "wifi network interface stays in state "non connected" i check all with lamarque V souza dev of networkmanager settings are good , my wifi adapter is compliant with ap mode in networkmanager log i have this : <info> Connection 'Radio Wifi AP' auto-activation failed: (5) Access Point (AP) mode is not supported by the supplicant. lamarque says : you need wpa_supplicant 2.0 2.0 is installed lamarque says : Well, ap-mode is a compilation option for wpa_supplicant. Maybe whoever compiled wpa_supplicant for OpenSuse forgot to enable it. then please suplly a wpa_supplicant compiled with the option ap-mode thanks see our conversation here : https://bugs.kde.org/show_bug.cgi?id=330473 Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c1
--- Comment #1 from Episteme PROMENEUR
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c
zhang jiajun
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c2
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c3
Robert Riemann
Repository: openSUSE-13.1-Oss Name: wpa_supplicant Version: 2.0-3.1.2
opensuse 13.1 64 bit. all patches installed. Same output: # strings $(which wpa_supplicant) | grep 'AP mode' AP mode support not included in the build nl80211: Supports Probe Response offload in AP mode nl80211: Skip disabling of Probe Request reporting nl_preq=%p while in AP mode nl80211: Failed to enable Probe Request frame reporting in AP mode AP mode not working. :( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c4
--- Comment #4 from Episteme PROMENEUR
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c5
Libor Pecháček
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c6
--- Comment #6 from Gary Ching-Pang Lin
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c7
--- Comment #7 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c8
Matthias Grießmeier
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c9
--- Comment #9 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c10
Ruediger Meier
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c11
Gary Ching-Pang Lin
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c12
Frederic Crozat
Hi Frederic,
What's the reason to always enable wpa_supplicant.service in the post script?
It is a dbus activated service, so it won't be running unless some applications is requesting it (NM). It has to be enabled otherwise it won't be usable by D-Bus applications. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c13
--- Comment #13 from Ruediger Meier
(In reply to comment #11)
Hi Frederic,
What's the reason to always enable wpa_supplicant.service in the post script?
It is a dbus activated service, so it won't be running unless some applications is requesting it (NM). It has to be enabled otherwise it won't be usable by D-Bus applications.
This is exactly what I want. That's why I had disabled it. zypper patch must not change my settings. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c14
--- Comment #14 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c15
--- Comment #15 from Ruediger Meier
use "systemctl mask wpa_supplicant"
That's a dirty hack. "mask" makes it impossible to start it manually. I don't want this. Any disabled service should be kept disabled on updates. What else is the purpose of "systemctl disable"? I guess most other services are behaving correctly on update. Why not wpa_supplicant? I don't want to be forced to read any rpm post script just to know whether I have to use "mask" or "disable". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c16
--- Comment #16 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c17
--- Comment #17 from Ruediger Meier
We can't "fix it" for a release distribution.
Don't understand this. The post script has an obvious and easy-to-fix bug. It simply must not call "systemctl enable" on update. Where is the problem? If this is "unfixable" then good night SUSE. Respecting admin's non-default setup is one of the most important things on any package update... "zypper patch" should improve things and not break... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c18
--- Comment #18 from Frederic Crozat
(In reply to comment #16)
We can't "fix it" for a release distribution.
Don't understand this. The post script has an obvious and easy-to-fix bug. It simply must not call "systemctl enable" on update. Where is the problem? If this is "unfixable" then good night SUSE.
It will affect new installs for people using update channels. I gave you a workaround until the fix can be released in the next distribution release. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c19
--- Comment #19 from Gary Ching-Pang Lin
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c20
--- Comment #20 from Frederic Crozat
How about the script like this?
%post %service_add_post wpa_supplicant.service if [ $1 -eq 1 ] ; then systemctl --quiet enable wpa_supplicant.service || : fi
So the systemctl command only runs for install, not for upgrade.
It won't work for upgrades from version where the service was not existing. For Factory, just drop the enable and do a sr on systemd-branding-openSUSE-presets adding wpa_supplicant.service. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c22
--- Comment #22 from Gary Ching-Pang Lin
(In reply to comment #19)
How about the script like this?
%post %service_add_post wpa_supplicant.service if [ $1 -eq 1 ] ; then systemctl --quiet enable wpa_supplicant.service || : fi
So the systemctl command only runs for install, not for upgrade.
It won't work for upgrades from version where the service was not existing.
Hmm I forgot the pre-systemd systems...
For Factory, just drop the enable and do a sr on systemd-branding-openSUSE-presets adding wpa_supplicant.service. Ok, I'll do it.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c23
Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c24
--- Comment #24 from Ruediger Meier
So the systemctl command only runs for install, not for upgrade.
It won't work for upgrades from version where the service was not existing.
This could be checked too. The current logic is broken since the beginning. BTW I don't see why wpa_supplicant is installed and enabled per default at all. I would have expected that upgrading openSUSE would not install/enable such service which I did not even had installed before. Isn't it very obvious that I don't need it on this system? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c25
Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c26
Frederic Crozat
Why should it be default enabled?
dbus activated systemd service, they need to be enabled at systemd level to be later actived by dbus.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c28
--- Comment #28 from Ruediger Meier
(In reply to comment #25)
Why should it be default enabled?
dbus activated systemd service, they need to be enabled at systemd level to be later actived by dbus..
The question was why it is enabled per default. Being a dbus activated service is no argument. Why would we want get it activated it by dbus? Even if NM is not installed and no wifi card. Also it's not only enabled but always running (comment #23). Please consider this a bug and fix it. It's a general problem, also for other services (like modem-manager). I'm really tired of cleaning this up all the time for any of my installations. Maintaining large package blacklists and masked services will shoot me in the foot in future. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c29
--- Comment #29 from Frederic Crozat
(In reply to comment #26)
(In reply to comment #25)
Why should it be default enabled?
dbus activated systemd service, they need to be enabled at systemd level to be later actived by dbus..
The question was why it is enabled per default. Being a dbus activated service is no argument. Why would we want get it activated it by dbus? Even if NM is not installed and no wifi card. Also it's not only enabled but always running (comment #23).
Then wait for future NM release which will allow to split wifi specific handling to a subpackage. In the mean time, we are enforcing installaing wpa_supplicant when NM is installed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c30
--- Comment #30 from Ludwig Nussel
(In reply to comment #25)
Why should it be default enabled?
dbus activated systemd service, they need to be enabled at systemd level to be later actived by dbus..
hmm... # pgrep -lf wpa_su # systemctl is-enabled wpa_supplicant.service disabled # dbus-send --system --dest=fi.w1.wpa_supplicant1 / foo.bar.baz # pgrep -lf wpa_su 7491 wpa_supplicant -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c31
--- Comment #31 from Episteme PROMENEUR
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c32
--- Comment #32 from Ruediger Meier
In the mean time, we are enforcing installaing wpa_supplicant when NM is installed.
This is also not true. It's installed allthough I've never had NM installed. NM is always blacklisted on any of my machines since I've noticed NM first time a few years ago. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c33
--- Comment #33 from Ludwig Nussel
(In reply to comment #25)
Why should it be default enabled?
dbus activated systemd service, they need to be enabled at systemd level to be later actived by dbus..
Now I got it. The service file is wrong. It must not hook itself into multiuser.target in Install but rather wpa_supplicant.target and it must have an alias for the bus activation there. That means enabling wpa_supplicant.service would only enable the dbus activation but not start the service on boot. To actually run wpa_supplicant on boot you'd need another file, e.g. a target that hooks itself to multi-user instead. See bluez for an example. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c34
--- Comment #34 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c35
--- Comment #35 from Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=860885
https://bugzilla.novell.com/show_bug.cgi?id=860885#c36
Frederic Crozat
I don't see how udev autodetection plays a role here. This is about dbus activation, right? For that one you need an alias in the Install section and don't need to hook into multiuser.wants.
That is the way the bluez target is enabled. I've not 100% convinced having an target as "install" which is not pulled at startup will cause systemd to allow the service to be dbus activable.. Any idea, systemd maintainers ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com