Hide Forgot
Description of problem: [root@qe-dell-ovs5-vm-60 NetworkManager-ci]# nmcli device wifi connect wpa2-eap password secret123 Error: Connection activation failed: (0) No reason given. [root@qe-dell-ovs5-vm-60 NetworkManager-ci]# echo $? 0 exit code is incorrect and password wasn't stored at all. [root@qe-dell-ovs5-vm-60 NetworkManager-ci]# nmcli connection show wpa2-eap --show-secrets connection.id: wpa2-eap connection.uuid: df66a7d0-1172-493e-9774-07074e26f802 connection.stable-id: -- connection.interface-name: -- connection.type: 802-11-wireless connection.autoconnect: yes connection.autoconnect-priority: 0 connection.autoconnect-retries: -1 (default) connection.timestamp: 0 connection.read-only: no connection.permissions: -- connection.zone: -- connection.master: -- connection.slave-type: -- connection.autoconnect-slaves: -1 (default) connection.secondaries: -- connection.gateway-ping-timeout: 0 connection.metered: unknown connection.lldp: -1 (default) 802-11-wireless.ssid: wpa2-eap 802-11-wireless.mode: infrastructure 802-11-wireless.band: -- 802-11-wireless.channel: 0 802-11-wireless.bssid: -- 802-11-wireless.rate: 0 802-11-wireless.tx-power: 0 802-11-wireless.mac-address: -- 802-11-wireless.cloned-mac-address: -- 802-11-wireless.generate-mac-address-mask:-- 802-11-wireless.mac-address-blacklist: -- 802-11-wireless.mac-address-randomization:default 802-11-wireless.mtu: auto 802-11-wireless.seen-bssids: -- 802-11-wireless.hidden: no 802-11-wireless.powersave: default (0) 802-11-wireless-security.key-mgmt: wpa-psk 802-11-wireless-security.wep-tx-keyidx: 0 802-11-wireless-security.auth-alg: open 802-11-wireless-security.proto: -- 802-11-wireless-security.pairwise: -- 802-11-wireless-security.group: -- 802-11-wireless-security.leap-username: -- 802-11-wireless-security.wep-key0: -- 802-11-wireless-security.wep-key1: -- 802-11-wireless-security.wep-key2: -- 802-11-wireless-security.wep-key3: -- 802-11-wireless-security.wep-key-flags: 0 (none) 802-11-wireless-security.wep-key-type: 0 (unknown) 802-11-wireless-security.psk: -- 802-11-wireless-security.psk-flags: 0 (none) 802-11-wireless-security.leap-password: -- 802-11-wireless-security.leap-password-flags:0 (none) ipv4.method: auto ipv4.dns: -- ipv4.dns-search: -- ipv4.dns-options: (default) ipv4.dns-priority: 0 ipv4.addresses: -- ipv4.gateway: -- ipv4.routes: -- ipv4.route-metric: -1 ipv4.ignore-auto-routes: no ipv4.ignore-auto-dns: no ipv4.dhcp-client-id: -- ipv4.dhcp-timeout: 0 ipv4.dhcp-send-hostname: yes ipv4.dhcp-hostname: -- ipv4.dhcp-fqdn: -- ipv4.never-default: no ipv4.may-fail: yes ipv4.dad-timeout: -1 (default) ipv6.method: auto ipv6.dns: -- ipv6.dns-search: -- ipv6.dns-options: (default) ipv6.dns-priority: 0 ipv6.addresses: -- ipv6.gateway: -- ipv6.routes: -- ipv6.route-metric: -1 ipv6.ignore-auto-routes: no ipv6.ignore-auto-dns: no ipv6.never-default: no ipv6.may-fail: yes ipv6.ip6-privacy: -1 (unknown) ipv6.addr-gen-mode: stable-privacy ipv6.dhcp-send-hostname: yes ipv6.dhcp-hostname: -- ipv6.token: -- proxy.method: none proxy.browser-only: no proxy.pac-url: -- proxy.pac-script: -- Version-Release number of selected component (if applicable): 1.8.0-9 How reproducible: allways Steps to Reproduce: 1. simwifi_wpa2psk_no_profile test Additional info: actually it works on my real machine, but in VMs wih mac80211_hwsim based wifi it simply doesn't work. It's cli only installation.
Created attachment 1326424 [details] journal log from NM
Created attachment 1326995 [details] [PATCH] cli: wifi: connect with PSK when the AP supports WPA-PSK and WPA-EAP
(In reply to Beniamino Galvani from comment #2) > Created attachment 1326995 [details] > [PATCH] cli: wifi: connect with PSK when the AP supports WPA-PSK and WPA-EAP lgtm
Applied to master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=7af471919a25bd20b0f49024e6653da41ece20f0 and nm-1-8: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-8&id=dc3cbc60129e58112445721ebd15a629fdaf2da3
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0778