Am 16.07.2013 17:14, schrieb Gianluca Cecchi: > Possibly NetworkManager that keeps wpa_supplicant running could > interfere and prevent hostapd to set AP mode? > > [g.cecchi@ope46 ~]$ sudo systemctl status wpa_supplicant > wpa_supplicant.service - WPA Supplicant daemon > Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled) > Active: active (running) since Tue 2013-07-16 09:18:38 CEST; 7h ago > Main PID: 497 (wpa_supplicant) > CGroup: name=systemd:/system/wpa_supplicant.service > └─497 /usr/sbin/wpa_supplicant -u -f > /var/log/wpa_supplicant.log -c /etc/wpa_supplican...t > > But as soon as I stop wpa, NetworkManager starts it again... > > I didn't find any option to prevent NM to keep wpa running... is it > hardcoded? How to stop wpa and retry with hostapd?
* a) file a bug for NM * b) systemctl mask wpa_supplicant.service or switch to classic network.service for static configured machines and disable the complete NM crap - hence you can even use "BOOTPROTO=dhcp" in "ifcfg-XX"-files
signature.asc
Description: OpenPGP digital signature
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
