LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page [SOLVED] NetworkManager fails to connect - authentication problem
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-24-2015, 07:12 PM   #1
edmundo_ba
Member
 
Registered: Jun 2004
Location: Buenos Aires
Distribution: kubuntu 20.04, Slackware64 14.2
Posts: 43

Rep: Reputation: 15
NetworkManager fails to connect - authentication problem

Hi,

When trying to connect to a wifi network using NetworkManager, it asks for the AP password, and even though I enter the correct password, it fails to connect, and keeps asking for the password.

First time I used NetworkManager, it worked perfect. Next day, I couldn't connect to the same AP. This AP uses WPA2.

When I boot a Kali live USB , I can connect without problems.

I found several threads all around the web about problems similar to this, but couldn't find the solution for me. Something similar with Wicd and the Bad Password Error, it happened to me too, and I removed wicd.

Could it be something about the keyring? Because I saw this in dmesg :
Code:
Feb 24 17:55:39 paneb gnome-keyring-daemon[1206]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
And NetworkManager.conf has this entry "plugins=keyfile":
Code:
[main]
plugins=keyfile
dhcp=dhcpcd

[keyfile]
hostname=paneb
Since I'm not using Gnome or Gnome Keyring, I'm thinking this message is due to NetworkManager querying it.

I'm using Slackware64 14.1 and Xfce.

Here are a few things that could help, thanks in advance to anyone who took the time to read all this:

Code:
02:00.0 Network controller [0280]: Intel Corporation WiFi Link 5100 [8086:4232]
	Subsystem: Intel Corporation WiFi Link 5100 AGN [8086:1201]
	Flags: bus master, fast devsel, latency 0, IRQ 46
	Memory at fdffe000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 00-22-fa-ff-ff-28-cf-b2
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
things in /var/log/messages:
Code:
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) starting connection 'Speedy-24A521'
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> NetworkManager state is now CONNECTING
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0/wireless): access point 'Speedy-24A521' has security, but secrets are required.
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0/wireless): connection 'Speedy-24A521' has security, and secrets exist.  No new secrets needed.
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Config: added 'ssid' value 'Speedy-24A521'
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Config: added 'scan_ssid' value '1'
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Config: added 'auth_alg' value 'OPEN'
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Config: added 'psk' value '<omitted>'
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> Config: set interface ap_scan to 1
Feb 24 17:30:37 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: inactive -> scanning
Feb 24 17:30:40 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 24 17:30:40 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: authenticating -> associating
Feb 24 17:30:40 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: associating -> associated
Feb 24 17:30:40 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: associated -> disconnected
Feb 24 17:30:41 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 24 17:30:52 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 24 17:30:52 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: authenticating -> associating
Feb 24 17:30:52 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: associating -> associated
Feb 24 17:30:52 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: associated -> disconnected
Feb 24 17:30:52 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 24 17:31:02 paneb NetworkManager[1094]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb 24 17:31:03 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: scanning -> inactive
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Activation (wlan0/wireless): connection 'Speedy-24A521' has security, and secrets exist.  No new secrets needed.
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Config: added 'ssid' value 'Speedy-24A521'
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Config: added 'scan_ssid' value '1'
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Config: added 'auth_alg' value 'OPEN'
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Config: added 'psk' value '<omitted>'
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> Config: set interface ap_scan to 1
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: inactive -> associating
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: associating -> associated
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: associated -> disconnected
Feb 24 17:31:05 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 24 17:31:16 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 24 17:31:16 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: authenticating -> associating
Feb 24 17:31:16 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: associating -> associated
Feb 24 17:31:16 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: associated -> disconnected
Feb 24 17:31:16 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 24 17:31:30 paneb NetworkManager[1094]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb 24 17:31:33 paneb NetworkManager[1094]: <info> (wlan0): supplicant interface state: scanning -> inactive
Feb 24 17:31:33 paneb NetworkManager[1094]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Feb 24 17:31:33 paneb NetworkManager[1094]: <info> NetworkManager state is now DISCONNECTED
Feb 24 17:31:33 paneb NetworkManager[1094]: <info> Marking connection 'Speedy-24A521' invalid.
Feb 24 17:31:33 paneb NetworkManager[1094]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Feb 24 17:31:33 paneb NetworkManager[1094]: <info> (wlan0): deactivating device (reason 'none') [0]
 
Old 02-25-2015, 08:35 AM   #2
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,558
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
gnome-keyring can be acquired from SlackBuilds.org if you need it. Otherwise, it should connect normally.

Unless there's a problem with the wireless router, using static IP or dhcp it should connect you.
 
Old 02-25-2015, 10:08 AM   #3
edmundo_ba
Member
 
Registered: Jun 2004
Location: Buenos Aires
Distribution: kubuntu 20.04, Slackware64 14.2
Posts: 43

Original Poster
Rep: Reputation: 15
I have gnome-keyring in my system (I'll find out later why it's needed since I don't have Gnome).

I finnally got connected after a lot of tries, I wrote the correct password and it kept asking for it. It was like this for 1 hour or so, meanwhile I was trying to find put what is wrong.

Next day, it failed to connect but it didn't ask for the password. NetworkManager just tried to reconnect during some time, maybe 20 minutes, and it finally succeded.

I wouldn't say it's the router, because other devices and OSes connect right away.
 
Old 02-25-2015, 03:32 PM   #4
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,558
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
What kernel are you using by chance 3.10.17?

Gnome-Keyring is basically, more or less, a security credentials daemon. It's similar to KDE's wallet.
Last edited by ReaperX7; 02-25-2015 at 03:34 PM.
 
Old 02-25-2015, 10:39 PM   #5
ryan858
Member
 
Registered: Feb 2009
Distribution: Slackware64-14.1
Posts: 43

Rep: Reputation: 17
In NetworkManager there should be a tab on the left called "Other". When you click that, what does it say for "Store connection secrets: "? Since the error states it is trying to prevent storage on disk, then setting it to "In secure storage (encrypted)" should stop the error (theoretically).

The other possibility is it could be the IEEE settings. Sometimes those have caused me problems either being on or off. They should be in the wifi connection's properties but I don't have a wireless connection to verify, and my ethernet doesn't show up in the 64-bit Slackware for me for whatever reason so I just use the dhcp option in netconfig to autostart my connection at boot-time.
Last edited by ryan858; 02-26-2015 at 12:08 AM.
 
Old 02-26-2015, 04:58 PM   #6
edmundo_ba
Member
 
Registered: Jun 2004
Location: Buenos Aires
Distribution: kubuntu 20.04, Slackware64 14.2
Posts: 43

Original Poster
Rep: Reputation: 15
Thank you ReaperX7 and ryan858 for your help.

Quote:
Originally Posted by ReaperX7 View Post
What kernel are you using by chance 3.10.17?
Yes, that's what I'm using.

Quote:
Originally Posted by ReaperX7 View Post
Gnome-Keyring is basically, more or less, a security credentials daemon. It's similar to KDE's wallet.
I understand what these daemons are. In fact, I was considering using a passwords vault, but it seems this is giving me more problems than its worth. Gnome-keyring was first launched by Chrome, and it was poping up every time I started Chrome. Now I followed this hint: erased the keyring files, leave password field blank, and proceed unsecurely. I just did this, I'm yet to test if this fixes my connection problems. Either way, after doing this, is gnome-keyring still loaded and available by networkmanager? Because I'm thinking the problem with NetworkManager is that gnome-keyring isn't loaded before I start Chrome. It seems NetworkManager succeds in connecting to WPA2 networks after I start Chrome, which launches gnome-keyring.


Quote:
Originally Posted by ryan858 View Post
In NetworkManager there should be a tab on the left called "Other". When you click that, what does it say for "Store connection secrets: "?
Please help me find that, because it looks promising but I'm not seeing it. I'm using XFCE, and when rc.networkmanager is started, it loads the NetworkManager Applet 0.9.8.4 . There are no tabs in that applet, is there any other way to access NetworkManager? Either using a gui or cli.

Quote:
Originally Posted by ryan858 View Post
The other possibility is it could be the IEEE settings. Sometimes those have caused me problems either being on or off. They should be in the wifi connection's properties but I don't have a wireless connection to verify, and my ethernet doesn't show up in the 64-bit Slackware for me for whatever reason so I just use the dhcp option in netconfig to autostart my connection at boot-time.
I have to look into this too, I've seen messages about disconnecting due to a change in the bandwidth that is not available for my country (AR, Argentina):

Code:
[  255.289453] wlan0: associated
[  255.289520] cfg80211: Calling CRDA for country: AR
[  255.292299] cfg80211: Regulatory domain changed to country: AR
[  255.292305] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  255.292310] cfg80211:   (2402000 KHz - 2482000 KHz @ 20000 KHz), (N/A, 2000 mBm)
[  255.292314] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[  255.292318] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  255.292322] cfg80211:   (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  255.292325] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[  255.375235] wlan0: AP 78:6a:89:24:a5:28 changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
[  255.375242] wlan0: AP 78:6a:89:24:a5:28 changed bandwidth in a way we can't support - disconnect
[  255.388091] cfg80211: Calling CRDA to update world regulatory domain
[  255.391181] cfg80211: World regulatory domain updated:
[  255.391188] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  255.391193] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  255.391197] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[  255.391200] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[  255.391204] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  255.391207] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  267.019040] wlan0: authenticate with 78:6a:89:24:a5:28
[  267.021098] wlan0: send auth to 78:6a:89:24:a5:28 (try 1/3)
[  267.039940] wlan0: send auth to 78:6a:89:24:a5:28 (try 2/3)
[  267.066764] wlan0: send auth to 78:6a:89:24:a5:28 (try 3/3)
[  267.091334] wlan0: authentication with 78:6a:89:24:a5:28 timed out
I think the router might be wrongly configured, and it could be picking a configuration not allowed for Argentina, thus my wifi just can keep connected legally. But I could try changing this settings at least to verify if this is true. Do you know how to do that? I mean, changing my country settings for the wifi card.
 
Old 02-26-2015, 05:30 PM   #7
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,558
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
Is your router using DNSMasque by chance?
 
Old 02-27-2015, 06:11 PM   #8
edmundo_ba
Member
 
Registered: Jun 2004
Location: Buenos Aires
Distribution: kubuntu 20.04, Slackware64 14.2
Posts: 43

Original Poster
Rep: Reputation: 15
It seems I finally hit the nail.

I turned the 802.11n mode off, as suggested in this site:

http://nerdia.net/2014/04/24/disable...965-in-ubuntu/

Since my card is Intel Wifi 5100 , I did :

Code:
echo "options iwlwifi 11n_disable=1" >> /etc/modprobe.d/iwlwifi.conf
It's working ok so far.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Can't connect to wifi through NetworkManager Didier Spaier Slackware 16 10-27-2013 03:49 PM
Trying to compile Robby's networkmanager-openconnect from SBO fails. vdemuth Slackware 10 06-02-2013 05:52 AM
[SOLVED] Networkmanager-vpnc-0.9.4 fails to compile under -current fl0 Slackware 7 04-05-2013 03:38 PM
[SOLVED] NetworkManager fails while installing Fedora 12 guest os Ashkan_s Linux - Virtualization and Cloud 1 11-18-2011 12:59 PM
Configure NetworkManager OpenVPN - Import Configuration Fails morbo77 Linux - Networking 3 09-18-2009 07:08 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:13 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration