[Solved] Network Manager - Looping Wifi Authentication

Stevefx · 2017-05-16 01:34:37

I've been struggling to get my arch wireless configuration going. Using the Arch Wiki as much as possible - my main issue is the loop of Wireless Authentication using the Network Manager. I have installed NetowrkManager, wpa_supplicant, and gnome keyring. This is the output of journalctl":

crunch@Banshee ~]$ journalctl -f
-- Logs begin at Wed 2017-05-10 00:17:43 UTC. --
May 16 01:25:44 Banshee wpa_supplicant[342]: wlp2s0: Associated with XX:XX:XX:XX
May 16 01:25:44 Banshee wpa_supplicant[342]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
May 16 01:25:44 Banshee NetworkManager[4945]: <info>  [1494897944.3672] device (wlp2s0): supplicant interface state: authenticating -> associating
May 16 01:25:44 Banshee NetworkManager[4945]: <info>  [1494897944.3714] device (wlp2s0): supplicant interface state: associating -> associated
May 16 01:25:44 Banshee wpa_supplicant[342]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=XX:XX:XX:XXreason=3 locally_generated=1
May 16 01:25:44 Banshee wpa_supplicant[342]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssidZZZZZ-5G" auth_failures=1 duration=10 reason=CONN_FAILED
May 16 01:25:44 Banshee NetworkManager[4945]: <warn>  [1494897944.3877] sup-iface[0x2652c80,wlp2s0]: connection disconnected (reason -3)
May 16 01:25:44 Banshee NetworkManager[4945]: <info>  [1494897944.3880] device (wlp2s0): supplicant interface state: associated -> disconnected
May 16 01:25:44 Banshee wpa_supplicant[342]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
May 16 01:25:45 Banshee NetworkManager[4945]: <info>  [1494897945.4825] device (wlp2s0): supplicant interface state: disconnected -> scanning
May 16 01:25:55 Banshee wpa_supplicant[342]: wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="ZZZZZ"
May 16 01:25:55 Banshee wpa_supplicant[342]: wlp2s0: SME: Trying to authenticate with XX:XX:XX:XX(SSID='xxxxxxcxcxc-5G' freq=5180 MHz)
May 16 01:25:55 Banshee kernel: wlp2s0: authenticate with::XX:XX:XX
May 16 01:25:55 Banshee NetworkManager[4945]: <info>  [1494897955.1377] device (wlp2s0): supplicant interface state: scanning -> authenticating
May 16 01:25:55 Banshee kernel: wlp2s0: send auth to XX:XX:XX:XX (try 1/3)
May 16 01:25:55 Banshee wpa_supplicant[342]: wlp2s0: Trying to associate with XX:XX:XX:XX (SSID OS-HOCT8xccxc-5G' freq=5180 MHz)
May 16 01:25:55 Banshee kernel: wlp2s0: authenticated
May 16 01:25:55 Banshee kernel: wlp2s0: associate with XX:XX:XX:X(try 1/3)
May 16 01:25:55 Banshee wpa_supplicant[342]: wlp2s0: Associated with XX:XX:XX:XX
May 16 01:25:55 Banshee wpa_supplicant[342]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
May 16 01:25:55 Banshee kernel: wlp2s0: RX AssocResp from XX:XX:XX:XX (capab=0x11 status=0 aid=5)
May 16 01:25:55 Banshee kernel: wlp2s0: associated
May 16 01:25:55 Banshee kernel: wlp2s0: deauthenticating from XX:XX:XX:XX:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING)
May 16 01:25:55 Banshee wpa_supplicant[342]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=XX:XX:XX:XX reason=3 locally_generated=1
May 16 01:25:55 Banshee wpa_supplicant[342]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="XZZXADad-5G" auth_failures=2 duration=20 reason=CONN_FAILED
May 16 01:25:55 Banshee NetworkManager[4945]: <info>  [1494897955.1787] device (wlp2s0): supplicant interface state: authenticating -> associating
May 16 01:25:55 Banshee NetworkManager[4945]: <info>  [1494897955.1788] device (wlp2s0): supplicant interface state: associating -> associated
May 16 01:25:55 Banshee NetworkManager[4945]: <warn>  [1494897955.1790] sup-iface[0x2652c80,wlp2s0]: connection disconnected (reason -3)
May 16 01:25:55 Banshee NetworkManager[4945]: <info>  [1494897955.1790] device (wlp2s0): supplicant interface state: associated -> disconnected
May 16 01:25:55 Banshee wpa_supplicant[342]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
May 16 01:25:56 Banshee NetworkManager[4945]: <info>  [1494897956.2627] device (wlp2s0): supplicant interface state: disconnected -> scanning
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[766]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:00 Banshee gnome-shell[538]: interval_offset: assertion 'tz->t_info != NULL' failed
May 16 01:26:04 Banshee gnome-terminal-[11317]: Allocating size to GtkScrollbar 0x19ca8e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
May 16 01:26:04 Banshee gnome-terminal-[11317]: Allocating size to GtkScrollbar 0x19ca8e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
May 16 01:26:04 Banshee gnome-terminal-[11317]: Allocating size to GtkScrollbar 0x19ca8e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
May 16 01:26:04 Banshee gnome-terminal-[11317]: Allocating size to GtkScrollbar 0x19ca8e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
May 16 01:26:04 Banshee gnome-terminal-[11317]: Allocating size to GtkScrollbar 0x19ca8e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
May 16 01:26:04 Banshee gnome-terminal-[11317]: Allocating size to GtkScrollbar 0x19ca8e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
May 16 01:26:04 Banshee gnome-terminal-[11317]: Allocating size to GtkScrollbar 0x19ca8e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
May 16 01:26:04 Banshee gnome-terminal-[11317]: Allocating size to GtkScrollbar 0x19ca8e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
May 16 01:26:04 Banshee gnome-terminal-[11317]: Allocating size to GtkScrollbar 0x19ca8e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
May 16 01:26:04 Banshee gnome-terminal-[11317]: Allocating size to GtkScrollbar 0x19ca8e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
May 16 01:26:05 Banshee NetworkManager[4945]: <warn>  [1494897965.2542] device (wlp2s0): Activation: (wifi) association took too long
May 16 01:26:05 Banshee NetworkManager[4945]: <info>  [1494897965.2542] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0]
May 16 01:26:05 Banshee NetworkManager[4945]: <warn>  [1494897965.2580] device (wlp2s0): Activation: (wifi) asking for new secrets
May 16 01:26:05 Banshee NetworkManager[4945]: <info>  [1494897965.2992] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
May 16 01:26:05 Banshee NetworkManager[4945]: <info>  [1494897965.2997] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0]
May 16 01:26:05 Banshee NetworkManager[4945]: <info>  [1494897965.2999] device (wlp2s0): Activation: (wifi) connection 'ZZZZZ-5G' has security, and secrets exist.  No new secrets needed.
May 16 01:26:05 Banshee NetworkManager[4945]: <info>  [1494897965.3000] Config: added 'ssid' value '-XXXXXX-5G'
May 16 01:26:05 Banshee NetworkManager[4945]: <info>  [1494897965.3000] Config: added 'scan_ssid' value '1'
May 16 01:26:05 Banshee NetworkManager[4945]: <info>  [1494897965.3000] Config: added 'key_mgmt' value 'WPA-PSK'
May 16 01:26:05 Banshee NetworkManager[4945]: <info>  [1494897965.3000] Config: added 'psk' value '<hidden>'
May 16 01:26:06 Banshee wpa_supplicant[342]: wlp2s0: SME: Trying to authenticate with XX:XX:XX:XX (SSID='FZZZZZZZZ-5G' freq=5180 MHz)

Any Help is appreciated :'(

Last edited by Stevefx (2017-05-16 02:10:15)

jasonwryan · 2017-05-16 01:38:34

Can you connect manually? Removing layers of abstraction is always the first step. Follow the wiki and see where it fails.

Stevefx · 2017-05-16 01:50:35

Thanks for the quick response jason ! I found that trying to connect manually fails as well. I have the output below:

May 16 01:47:16 Banshee systemd[1]: Starting Networking for netctl profile wlp2s0-XXXXXX-5G...
May 16 01:47:16 Banshee network[13750]: Starting network profile 'wlp2s0-XXXXXXX-5G'...
May 16 01:47:16 Banshee network[13750]: The interface of network profile 'wlp2s0-XXXXXXX-5G' is already up
May 16 01:47:16 Banshee systemd[1]: netctl@wlp2s0\x2dFiOS\x2dHOCT8\x2d5G.service: Main process exited, code=exited, status=1/FAILURE
May 16 01:47:16 Banshee systemd[1]: Failed to start Networking for netctl profile wlp2s0-FiOS-HOCT8-5G.
May 16 01:47:16 Banshee systemd[1]: netctl@wlp2s0\x2dFiOS\x2dHOCT8\x2d5G.service: Unit entered failed state.
May 16 01:47:16 Banshee systemd[1]: netctl@wlp2s0\x2dFiOS\x2dHOCT8\x2d5G.service: Failed with result 'exit-code'.

jasonwryan · 2017-05-16 01:53:14

Please paste the output of:

systemctl list-unit-files --state enabled

Stevefx · 2017-05-16 01:58:07

Sure!

[root@Banshee crunch]# systemctl list-unit-files --state enabled
UNIT FILE                                   STATE  
autovt@.service                             enabled
dbus-fi.w1.wpa_supplicant1.service          enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
gdm.service                                 enabled
getty@.service                              enabled
netctl-auto@.service                        enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
wpa_supplicant.service                      enabled
remote-fs.target                            enabled

12 unit files listed.

jasonwryan · 2017-05-16 01:59:17

You have more than one service managing your network. The wiki warns against this.

Stevefx · 2017-05-16 02:05:29

aww - that makes sense - would I need to go back and edit .xinitrc or disable one of the services via the terminal? I'm not sure which.

jasonwryan · 2017-05-16 02:09:02

It shouldn't have anything to do with .xinitrc; disable the service that you don't want (presumably netctl).

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

Arch Linux

#1 2017-05-16 01:34:37

[Solved] Network Manager - Looping Wifi Authentication

#2 2017-05-16 01:38:34

Re: [Solved] Network Manager - Looping Wifi Authentication

#3 2017-05-16 01:50:35

Re: [Solved] Network Manager - Looping Wifi Authentication

#4 2017-05-16 01:53:14

Re: [Solved] Network Manager - Looping Wifi Authentication

#5 2017-05-16 01:58:07

Re: [Solved] Network Manager - Looping Wifi Authentication

#6 2017-05-16 01:59:17

Re: [Solved] Network Manager - Looping Wifi Authentication

#7 2017-05-16 02:05:29

Re: [Solved] Network Manager - Looping Wifi Authentication

#8 2017-05-16 02:09:02

Re: [Solved] Network Manager - Looping Wifi Authentication

Board footer