Hide Forgot
Description of problem: Access to a WPA-HOME WLAN endpoint is not possible. The curious things is, WLAN-WEP (has Web-Authorisation) does not have that problem!! Version-Release number of selected component (if applicable): Fedora F23 (F24 seemed have it fixed) How reproducible: Simple open a WLAN-WPA, give the passkey wait and wait and wait and .... failure. When i look into the journal i see: Aug 31 01:34:18 chrissyboy.fritz.box systemd[1]: Stopping CUPS Scheduler. Aug 31 01:34:18 chrissyboy.fritz.box systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket. Aug 31 01:18:35 chrissyboy.fritz.box /firewalld[1183]: ERROR: UNKNOWN_INTERFACE: 'wlp13s0' is not in any zone Aug 31 01:18:35 chrissyboy.fritz.box /usr/libexec/gdm-x-session[3433]: "Method \"GetAll\" with signature \"s\" on interface \"org.freedesktop.DBus.Properties\" doesn't exist\n" Aug 31 01:18:38 chrissyboy.fritz.box NetworkManager[1287]: <info> (wlp13s0): supplicant interface state: disconnected -> inactive Aug 31 01:20:39 chrissyboy.fritz.box systemd[1]: Starting system activity accounting tool... Aug 31 01:20:39 chrissyboy.fritz.box systemd[1]: Started system activity accounting tool. Aug 31 01:20:39 chrissyboy.fritz.box audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? Aug 31 01:20:39 chrissyboy.fritz.box audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? Aug 31 01:20:59 chrissyboy.fritz.box NetworkManager[1287]: <info> (enp14s0): Activation: starting connection 'enp14s0' (efb803f0-f88f-4e4f-97e4-627c75d88706) Aug 31 01:20:59 chrissyboy.fritz.box NetworkManager[1287]: <info> (enp14s0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Aug 31 01:20:59 chrissyboy.fritz.box NetworkManager[1287]: <info> NetworkManager state is now CONNECTING Aug 31 01:20:59 chrissyboy.fritz.box NetworkManager[1287]: <info> (enp14s0): device state change: prepare -> config (reason 'none') [40 50 0] First time i ran into that problem i entered: $ firewall-cmd --list-interfaces and did not see my WLAN device. I added it later but, assigned a permanent public zone but it did not helped. Steps to Reproduce: 1.visit you Network-Manager 2.select a WLAN with WPA, give passkey 3.wait and see the error Actual results: WLAN with WPA is not working. WLAN with WEP is working ?!?! Expected results: Working WLAN ... man! Additional info: Ask me for some more infos iff you need 'em
the logfile doesn't contain relevant parts of why activating the connection would fail. Please attach full logfile with level=TRACE enabled. See https://cgit.freedesktop.org/NetworkManager/NetworkManager/plain/contrib/fedora/rpm/NetworkManager.conf?id=c90ec2d8c8a12b44c908bf7f80b23059c29f68fa and `man NetworkManager.conf` I don't think the firewall-cmd matters here? Are you saying the connection was successfully established, but connectivity restricted by the firewall? You say "see error"? What error did you see? Note that fedora 23 brings 1.0.12 release. The 1.0 branch is no longer supported upstream, so expect little help here for Fedora 23. Sorry.
Salut Thomas and sorry for my late response, i had to ship some other software and yeah went into problems. I'll gonna send you the output of the log this evening (in about 12 hours). No, the connection was not established, i simply noticed an error message in journalctl -u NetworkManager, saying that: <warn> [1473133773.4629] firewall: [0x55f53916fe40,remove:"wlp13s0"]: complete: request failed (UNKNOWN_INTERFACE: 'wlp13s0' is not in any zone) so i thought it could be a firewall issue. In the meantime i switched to F24, but the problem is still there. I have another notebook(with F24 it is ole i686), that has no problems with a similar configuration.
Ok, here we are: wlp13s0 is my wlan device and GroovieNet the WLAN ressoure to conect to: see the attached nm3.log.gz file.
Created attachment 1198406 [details] journalctl -u NetworkManager A log file from the NM.
Hi, from the logfile it is not visible why that would happen. Can you gather logfiles from wpa-supplicant? This is our howto for that: https://wiki.gnome.org/Projects/NetworkManager/Debugging#Debugging_WiFi_Connections (although, recently those instructions did not work for me, they actually should work).
Does it help, iff not i will create a debug log. Sorry actually the computer is serving some stuff for me. Successfully initialized wpa_supplicant wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN nl80211: deinit ifname=wlp13s0 disabled_11b_rates=0 wlp13s0: CTRL-EVENT-TERMINATING Successfully initialized wpa_supplicant wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN nl80211: deinit ifname=wlp13s0 disabled_11b_rates=0 wlp13s0: CTRL-EVENT-TERMINATING Successfully initialized wpa_supplicant wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN nl80211: deinit ifname=wlp13s0 disabled_11b_rates=0 wlp13s0: CTRL-EVENT-TERMINATING
Salut the above log is the only think i can offer your. Let me know iff you need further information. Maybe there is a side effect with a openvpn Configuration, that is running since F23. Please take into accout, that i was switching the desktop from cinnamon to plasma, after plasma was able to handle correct the openvpn stuff. Christian
the only thing
Did you fix it in the meantime. WLAN WPA Access is working again in private and professional mode.