I can not connect to authenticated networks

MysteriesOfPsy · 2017-03-07 20:14:11

Help community, I need help

On my university there are two authenticated networks, WIFI-UFJF and WIFI-NRC, but when I try to login, they don't connect. Instead, it keeps requiring my login and password.

http://imgur.com/SuuzFY9

http://imgur.com/HCDCbKz

lspci -v
07:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7265
	Flags: bus master, fast devsel, latency 0, IRQ 46
	Memory at f7100000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

dmesg | grep iwlwifi
[    7.066204] iwlwifi 0000:07:00.0: enabling device (0000 -> 0002)
[    7.623713] iwlwifi 0000:07:00.0: Direct firmware load for iwlwifi-7265D-26.ucode failed with error -2
[    7.623724] iwlwifi 0000:07:00.0: Direct firmware load for iwlwifi-7265D-25.ucode failed with error -2
[    7.623730] iwlwifi 0000:07:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
[    7.623737] iwlwifi 0000:07:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
[    7.755244] iwlwifi 0000:07:00.0: loaded firmware version 22.391740.0 op_mode iwlmvm
[    8.739691] iwlwifi 0000:07:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
[    8.741090] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[    8.741264] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[    9.513625] iwlwifi 0000:07:00.0 wlp7s0: renamed from wlan0
[   13.166579] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[   13.166757] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[   13.231920] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[   13.232097] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[   13.251270] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[   13.251446] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[   13.316569] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[   13.316747] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled

jasonwryan · 2017-03-07 20:19:09

You want the log of your network manager, to see why it is failing...

Moving to NC.

MysteriesOfPsy · 2017-03-07 23:44:08

journalctl -u NetworkManager

Mar 07 14:34:05 universe NetworkManager[326]: <warn>  [1488908045.7695] sup-iface[0x1f3c980,wlp7s0]: connection disconnected (reason 23)
Mar 07 14:34:05 universe NetworkManager[326]: <info>  [1488908045.7740] device (wlp7s0): supplicant interface state: associated -> disconnected
Mar 07 14:34:05 universe NetworkManager[326]: <info>  [1488908045.8742] device (wlp7s0): supplicant interface state: disconnected -> scanning
Mar 07 14:34:17 universe NetworkManager[326]: <info>  [1488908057.0201] device (wlp7s0): supplicant interface state: scanning -> authenticating
Mar 07 14:34:17 universe NetworkManager[326]: <info>  [1488908057.0369] device (wlp7s0): supplicant interface state: authenticating -> associating
Mar 07 14:34:17 universe NetworkManager[326]: <info>  [1488908057.0436] device (wlp7s0): supplicant interface state: associating -> associated
Mar 07 14:34:18 universe NetworkManager[326]: <warn>  [1488908058.2289] sup-iface[0x1f3c980,wlp7s0]: connection disconnected (reason 23)
Mar 07 14:34:18 universe NetworkManager[326]: <info>  [1488908058.2337] device (wlp7s0): supplicant interface state: associated -> disconnected
Mar 07 14:34:18 universe NetworkManager[326]: <info>  [1488908058.3339] device (wlp7s0): supplicant interface state: disconnected -> scanning
Mar 07 14:34:28 universe NetworkManager[326]: <warn>  [1488908068.7359] device (wlp7s0): Activation: (wifi) association took too long
Mar 07 14:34:28 universe NetworkManager[326]: <info>  [1488908068.7359] device (wlp7s0): state change: config -> need-auth (reason 'none') [50 60 0]
Mar 07 14:34:28 universe NetworkManager[326]: <warn>  [1488908068.7377] device (wlp7s0): Activation: (wifi) asking for new secrets
Mar 07 14:34:31 universe NetworkManager[326]: <warn>  [1488908071.2683] device (wlp7s0): User canceled the secrets request.
Mar 07 14:34:31 universe NetworkManager[326]: <info>  [1488908071.2683] device (wlp7s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Mar 07 14:34:31 universe NetworkManager[326]: <info>  [1488908071.2685] manager: NetworkManager state is now DISCONNECTED
Mar 07 14:34:31 universe NetworkManager[326]: <warn>  [1488908071.2692] device (wlp7s0): Activation: failed for connection 'UFJF-WIFI'
Mar 07 14:34:31 universe NetworkManager[326]: <info>  [1488908071.3541] device (wlp7s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 07 14:34:31 universe NetworkManager[326]: <info>  [1488908071.3564] device (wlp7s0): set-hw-addr: set MAC address to 8A:9B:08:BE:A7:F2 (scanning)
Mar 07 14:34:31 universe NetworkManager[326]: <info>  [1488908071.4088] device (wlp7s0): supplicant interface state: scanning -> disconnected
Mar 07 14:34:31 universe NetworkManager[326]: <info>  [1488908071.4140] device (wlp7s0): supplicant interface state: disconnected -> inactive
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.3805] keyfile: add connection in-memory (c55e7545-0186-49db-ab8e-fd78a51bc68c,"eduroam")
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.3819] device (wlp7s0): Activation: starting connection 'eduroam' (c55e7545-0186-49db-ab8e-fd78a51bc68c
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.3826] keyfile: update /etc/NetworkManager/system-connections/eduroam (c55e7545-0186-49db-ab8e-fd78a51b
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.3827] audit: op="connection-add-activate" uuid="c55e7545-0186-49db-ab8e-fd78a51bc68c" name="eduroam" p
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.3903] device (wlp7s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.3908] manager: NetworkManager state is now CONNECTING
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.3933] device (wlp7s0): set-hw-addr: reset MAC address to 60:57:18:F2:C0:E2 (preserve)
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4158] device (wlp7s0): state change: prepare -> config (reason 'none') [40 50 0]
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4160] device (wlp7s0): Activation: (wifi) access point 'eduroam' has security, but secrets are require
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4160] device (wlp7s0): state change: config -> need-auth (reason 'none') [50 60 0]
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4382] device (wlp7s0): supplicant interface state: inactive -> disconnected
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4383] device (wlp7s0): supplicant interface state: disconnected -> inactive
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4567] device (wlp7s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4574] device (wlp7s0): state change: prepare -> config (reason 'none') [40 50 0]
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4576] device (wlp7s0): Activation: (wifi) connection 'eduroam' has security, and secrets exist.  No ne
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4576] Config: added 'ssid' value 'eduroam'
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4576] Config: added 'scan_ssid' value '1'
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4577] Config: added 'key_mgmt' value 'WPA-EAP'
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4577] Config: added 'auth_alg' value 'OPEN'
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4577] Config: added 'password' value '<hidden>'
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4577] Config: added 'eap' value 'TTLS'
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4577] Config: added 'fragment_size' value '1266'

jasonwryan · 2017-03-07 23:57:39

MysteriesOfPsy wrote:

Mar 07 14:34:28 universe NetworkManager[326]: <warn>  [1488908068.7377] device (wlp7s0): Activation: (wifi) asking for new secrets
Mar 07 14:34:31 universe NetworkManager[326]: <warn>  [1488908071.2683] device (wlp7s0): User canceled the secrets request.
Mar 07 14:34:31 universe NetworkManager[326]: <info>  [1488908071.2683] device (wlp7s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
...
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4160] device (wlp7s0): Activation: (wifi) access point 'eduroam' has security, but secrets are require
...
Mar 07 14:34:59 universe NetworkManager[326]: <info>  [1488908099.4576] device (wlp7s0): Activation: (wifi) connection 'eduroam' has security, and secrets exist.  No ne

MysteriesOfPsy · 2017-03-08 01:39:06

I can't undersand.. this "secrets" would be login and pass?
I can send the correct login and pass several times but I cant conect.. I get a loop for enter the login and pass...

http://imgur.com/SuuzFY9

jasonwryan · 2017-03-08 01:49:45

If you are absolutely certain that your credentials are correct, then your configuration options are wrong.

MysteriesOfPsy · 2017-03-08 01:57:08

That's right, on windows I can access normally.

This settings is default, how I can know the correct configuration? Only with network admins?
http://imgur.com/HCDCbKz

jasonwryan · 2017-03-08 02:06:01

Presumably.

MysteriesOfPsy · 2017-03-08 13:44:24

I see the configs for linux and can connect now on UFJF WIFI, but NRC doesn't work

new logs:

Mar 08 10:38:29 universe NetworkManager[325]: <info>  [1488980309.9023] Config: added 'fragment_size' value '1266'
Mar 08 10:38:29 universe NetworkManager[325]: <info>  [1488980309.9023] Config: added 'phase2' value 'auth=MSCHAPV2'
Mar 08 10:38:29 universe NetworkManager[325]: <info>  [1488980309.9023] Config: added 'identity' value '12195088613'
Mar 08 10:38:29 universe NetworkManager[325]: <info>  [1488980309.9023] Config: added 'bgscan' value 'simple:30:-65:300'
Mar 08 10:38:29 universe NetworkManager[325]: <info>  [1488980309.9023] Config: added 'proactive_key_caching' value '1'
Mar 08 10:38:29 universe NetworkManager[325]: <info>  [1488980309.9068] sup-iface[0x25b30d0,wlp7s0]: config: set interface ap_scan to 1
Mar 08 10:38:29 universe NetworkManager[325]: <info>  [1488980309.9167] device (wlp7s0): supplicant interface state: disconnected -> scanning
Mar 08 10:38:30 universe NetworkManager[325]: <info>  [1488980310.9447] device (wlp7s0): supplicant interface state: scanning -> authenticating
Mar 08 10:38:30 universe NetworkManager[325]: <info>  [1488980310.9642] device (wlp7s0): supplicant interface state: authenticating -> associating
Mar 08 10:38:30 universe NetworkManager[325]: <info>  [1488980310.9703] device (wlp7s0): supplicant interface state: associating -> associated
Mar 08 10:38:31 universe NetworkManager[325]: <info>  [1488980311.0842] device (wlp7s0): supplicant interface state: associated -> 4-way handshake
Mar 08 10:38:31 universe NetworkManager[325]: <info>  [1488980311.0919] device (wlp7s0): supplicant interface state: 4-way handshake -> completed
Mar 08 10:38:31 universe NetworkManager[325]: <info>  [1488980311.0919] device (wlp7s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wi
Mar 08 10:38:31 universe NetworkManager[325]: <info>  [1488980311.0921] device (wlp7s0): state change: config -> ip-config (reason 'none') [50 70 0]
Mar 08 10:38:31 universe NetworkManager[325]: <info>  [1488980311.0931] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Mar 08 10:39:16 universe NetworkManager[325]: <warn>  [1488980356.7238] dhcp4 (wlp7s0): request timed out
Mar 08 10:39:16 universe NetworkManager[325]: <info>  [1488980356.7239] dhcp4 (wlp7s0): state changed unknown -> timeout
Mar 08 10:39:16 universe NetworkManager[325]: <info>  [1488980356.7415] dhcp4 (wlp7s0): canceled DHCP transaction
Mar 08 10:39:16 universe NetworkManager[325]: <info>  [1488980356.7415] dhcp4 (wlp7s0): state changed timeout -> done
Mar 08 10:39:16 universe NetworkManager[325]: <info>  [1488980356.7418] device (wlp7s0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Mar 08 10:39:16 universe NetworkManager[325]: <info>  [1488980356.7419] manager: NetworkManager state is now DISCONNECTED
Mar 08 10:39:16 universe NetworkManager[325]: <warn>  [1488980356.7426] device (wlp7s0): Activation: failed for connection 'WIFI-NRC'
Mar 08 10:39:16 universe NetworkManager[325]: <info>  [1488980356.7429] device (wlp7s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 08 10:39:16 universe NetworkManager[325]: <info>  [1488980356.7532] device (wlp7s0): set-hw-addr: set MAC address to AA:0C:23:C3:95:11 (scanning)
Mar 08 10:39:16 universe NetworkManager[325]: <warn>  [1488980356.7735] sup-iface[0x25b30d0,wlp7s0]: connection disconnected (reason -3)
Mar 08 10:39:16 universe NetworkManager[325]: <info>  [1488980356.7736] device (wlp7s0): supplicant interface state: completed -> disconnected
Mar 08 10:39:16 universe NetworkManager[325]: <warn>  [1488980356.7737] sup-iface[0x25b30d0,wlp7s0]: connection disconnected (reason -3)

R00KIE · 2017-03-08 15:50:51

Connect manually with wpa_supplicant and a dhcp client, using network manager to debug connection problems is not a good idea as it hides many things.

If you have trouble also with wpa_supplicant but you are sure you are using the correct configuration then post the configuration you are using and we can go from there.

Also your network manager logs have truncated lines, please try to make sure your next posts don't have truncated lines as that makes it harder to see what's going on.

promarbler14 · 2017-03-09 12:33:05

Do the problems persist after a system upgrade and restart? There was a Linux firmware update recently.

Last edited by promarbler14 (2017-03-09 12:33:28)

smithw · 2017-04-25 18:42:23

It looks like something related to this bug.

Specifically, WPA2-Enterprise based connections with no cert file and username/password authentication tend to have this issue where they struggle with most recent TLS versions (Eduroam is a notorious offender here, btw). By default, wpa_supplicant (and hence NetworkManager) will require TLS v. 1.2 to be used for negotiating this type of authentication, and, if it fails, it will refuse to connect. Thing is, most networks set up to use this kind of configuration cannot do TLS > 1.0 because of some hardware issue or something (old routers and stuff; I can't find right now where I've read this, since I've been fighting this issue for almost 10 years now on my work network). Basically, for NetworkManager or wpa_supplicant to connect, you'd have to ask your network admin to upgrade their routers and this is not usually feasible. You can however connect on Windows, macOS, iOS and Android normally, because, unlike NM/wpa_supplicant, they will gracefully downgrade the TLS version they require until they're able to negotiate the authentication - the less secure, though most compatible, option.

As seen on the bug report, wpa_supplicant added some configuration options that will allow you to manually specify lower versions of TLS as a requirement for connection. This means you can connect using netctl and a configuration file like this:

Security=wpa-configsection
WPAConfigSection={
    (...)
    'phase1="tls_disable_tlsv1_2=1 tls_disable_tlsv1_1=1"'
}

However, up until 1.8 (which hit stable a few days ago), you couldn't specify this option on NetworkManager at all - by design, NetworkManager doesn't have any method to directly pass options to the underlying wpa_supplicant it uses. This bug report shows that since 1.8 NetworkManager have the option phase1-auth-flags, which will allow you to forward TLS disabling options to wpa_supplicant. You'd have to manually update you NetworkManager config file (usually located on "/etc/NetworkManager/system-connections") to include this:

[802-1x]
(...)
phase1-auth-flags=6

Here, "6" means the bitwise sum of flags "2" (meaning "disable TLS v. 1.1") and "4" (meaning "disable TLS v. 1.2"). It also allows you to disable TLS v. 1.0 with the flag "1", but usually this is not necessary.

Well, these are the good news. The bad news is that even updating these options it may fail to connect (as it does for me), and I can't for the life of me figure out the reason. Back to netctl for now. I hope this helps you with your issue, though.

Arch Linux

#1 2017-03-07 20:14:11

I can not connect to authenticated networks

#2 2017-03-07 20:19:09

Re: I can not connect to authenticated networks

#3 2017-03-07 23:44:08

Re: I can not connect to authenticated networks

#4 2017-03-07 23:57:39

Re: I can not connect to authenticated networks

#5 2017-03-08 01:39:06

Re: I can not connect to authenticated networks

#6 2017-03-08 01:49:45

Re: I can not connect to authenticated networks

#7 2017-03-08 01:57:08

Re: I can not connect to authenticated networks

#8 2017-03-08 02:06:01

Re: I can not connect to authenticated networks

#9 2017-03-08 13:44:24

Re: I can not connect to authenticated networks

#10 2017-03-08 15:50:51

Re: I can not connect to authenticated networks

#11 2017-03-09 12:33:05

Re: I can not connect to authenticated networks

#12 2017-04-25 18:42:23

Re: I can not connect to authenticated networks

Board footer