You are not logged in.

#1 2020-02-23 14:02:19

Sinn12
Member
Registered: 2020-02-22
Posts: 14

Network Manager sup-iface disconnected (reason -3) loop

Hello
i am new to arch...just finished my installation a couple of days ago and all seems to be working besides when i'm with eduroam connected.
Network Manager somtimes connects just fine and then it just stops and starts a loop connecting.....Disconnecting.
I am using Deepin

Feb 23 14:29:54 Thinkpad wpa_supplicant[14511]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <warn>  [1582464594.0799] sup-iface[0x5645c4d14930,wlp3s0]: connection disconnected (reason -3)
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.0801] device (wlp3s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Feb 23 14:29:54 Thinkpad wpa_supplicant[14511]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.0819] device (wlp3s0): set-hw-addr: set MAC address to 4E:AC:06:56:57:FB (scanning)
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.0851] manager: NetworkManager state is now DISCONNECTED
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.0854] device (wlp3s0): Activation: starting connection 'eduroam' (c8aa70c5-43ce-4110-9ef2-2b20a43d6f08)
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.0864] device (wlp3s0): supplicant interface state: associated -> disconnected
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.0865] device (p2p-dev-wlp3s0): supplicant management interface state: associated -> disconnected
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1082] device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1087] manager: NetworkManager state is now CONNECTING
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1105] device (wlp3s0): set-hw-addr: reset MAC address to 28:B2:BD:AE:9C:9B (preserve)
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1138] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1165] device (wlp3s0): Activation: (wifi) access point 'eduroam' has security, but secrets are required.
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1165] device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1204] device (wlp3s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1209] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1214] device (wlp3s0): Activation: (wifi) connection 'eduroam' has security, and secrets exist.  No new secrets needed.
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1214] Config: added 'ssid' value 'eduroam'
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1214] Config: added 'scan_ssid' value '1'
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1214] Config: added 'bgscan' value 'simple:30:-65:300'
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1214] Config: added 'key_mgmt' value 'WPA-EAP WPA-EAP-SHA256 FT-EAP FT-EAP-SHA384'
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1215] Config: added 'password' value '<hidden>'
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1215] Config: added 'eap' value 'PEAP'
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1215] Config: added 'fragment_size' value '1266'
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1215] Config: added 'phase2' value 'auth=MSCHAPV2'
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1215] Config: added 'identity' value '#myeduroamid'
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1215] Config: added 'anonymous_identity' value '#eduroam'
Feb 23 14:29:54 Thinkpad NetworkManager[14510]: <info>  [1582464594.1215] Config: added 'proactive_key_caching' value '1'
Feb 23 14:29:57 Thinkpad NetworkManager[14510]: <info>  [1582464597.1567] device (wlp3s0): supplicant interface state: disconnected -> scanning
Feb 23 14:29:57 Thinkpad NetworkManager[14510]: <info>  [1582464597.1568] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> scanning
Feb 23 14:29:59 Thinkpad wpa_supplicant[14511]: wlp3s0: SME: Trying to authenticate with 6c:8b:d3:03:2b:2e (SSID='eduroam' freq=5500 MHz)
Feb 23 14:29:59 Thinkpad NetworkManager[14510]: <info>  [1582464599.9821] device (wlp3s0): supplicant interface state: scanning -> authenticating
Feb 23 14:29:59 Thinkpad NetworkManager[14510]: <info>  [1582464599.9821] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> authenticating
Feb 23 14:29:59 Thinkpad wpa_supplicant[14511]: wlp3s0: Trying to associate with 6c:8b:d3:03:2b:2e (SSID='eduroam' freq=5500 MHz)
Feb 23 14:29:59 Thinkpad wpa_supplicant[14511]: wlp3s0: Associated with 6c:8b:d3:03:2b:2e
Feb 23 14:29:59 Thinkpad wpa_supplicant[14511]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Feb 23 14:29:59 Thinkpad wpa_supplicant[14511]: wlp3s0: CTRL-EVENT-EAP-STARTED EAP authentication started
Feb 23 14:30:00 Thinkpad NetworkManager[14510]: <info>  [1582464600.0035] device (wlp3s0): supplicant interface state: authenticating -> associating
Feb 23 14:30:00 Thinkpad NetworkManager[14510]: <info>  [1582464600.0036] device (p2p-dev-wlp3s0): supplicant management interface state: authenticating -> associating
Feb 23 14:30:00 Thinkpad NetworkManager[14510]: <info>  [1582464600.0037] device (wlp3s0): supplicant interface state: associating -> associated
Feb 23 14:30:00 Thinkpad NetworkManager[14510]: <info>  [1582464600.0037] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> associated

I tried restarting NetworkManager.service and wpa_supplicant but it didnt solve anything.

UNIT FILES

UNIT FILE                                  STATE  
autovt@.service                            enabled
bluetooth.service                          enabled
dbus-org.bluez.service                     enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
display-manager.service                    enabled
getty@.service                             enabled
lightdm.service                            enabled
NetworkManager-dispatcher.service          enabled
NetworkManager-wait-online.service         enabled
NetworkManager.service                     enabled
remote-fs.target                           enabled

Offline

#2 2020-02-24 06:16:28

atrotet
Member
From: Reunion island
Registered: 2010-12-28
Posts: 26

Re: Network Manager sup-iface disconnected (reason -3) loop

https://gitlab.freedesktop.org/NetworkM … issues/232

Seems like using systemd-networkd instead of NM might be a working solution for now

Last edited by atrotet (2020-02-24 06:40:51)

Offline

#3 2020-02-24 08:21:04

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,708
Website

Re: Network Manager sup-iface disconnected (reason -3) loop

According to the linked issue you also might want to try an alternative WiFi backend, such as iwd. As a last resort you can also try to downgrade NetworkManager to 1.8.

Last edited by schard (2020-02-24 08:21:52)


Inofficial first vice president of the Rust Evangelism Strike Force

Offline

#4 2020-02-24 18:55:10

Sinn12
Member
Registered: 2020-02-22
Posts: 14

Re: Network Manager sup-iface disconnected (reason -3) loop

just downgradet to networkmanager 1.18 after i read that 1.22 had problems with PEAP ....it connected after 1 min but i still get this :

Feb 24 19:51:49 Thinkpad NetworkManager[425]: <warn>  [1582570309.0723] sup-iface[0x56393daef0b0,wlan0]: connection disconnected (reason -3)

and then NetworkManger tries to connect again.Could it be the wpa_supplicant?

Offline

#5 2020-02-24 22:51:32

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,708
Website

Re: Network Manager sup-iface disconnected (reason -3) loop

Sinn12 wrote:

Could it be the wpa_supplicant?

Yes. This has been mentoined in one of the comments of the issue linked to by @atrotet and is also the reason why I suggested to try iwd.
Did you do that?


Inofficial first vice president of the Rust Evangelism Strike Force

Offline

#6 2020-02-25 08:00:21

Sinn12
Member
Registered: 2020-02-22
Posts: 14

Re: Network Manager sup-iface disconnected (reason -3) loop

Yes created a configurationsFile for eduroam but when i tried to connect it still said no configuration.
I changed the Configuration of the wpa_supplicant after i found a file in eduroams website.
I stopted NetworkManager and wpa_supplicant then i did the following command:

wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf

And it connected directly without problems but when i restarted Network Manager it still had problems .

Offline

#7 2020-02-25 08:09:57

Sinn12
Member
Registered: 2020-02-22
Posts: 14

Re: Network Manager sup-iface disconnected (reason -3) loop

device (wlan0): state change: config -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
device (wlan0): disconnecting for new activation request.

This is what breaks the connection and then restarts again

Offline

#8 2020-02-25 08:28:02

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,708
Website

Re: Network Manager sup-iface disconnected (reason -3) loop

If you actually safely identified this as the cause, NetworkManager might try to attempt to connect to another network nearby.
You might want to try to identify this network and lower its priority in its profile.
If you do not encounter this issue without NetworkManager, it might also be a good idea to change to another network management tool, such as netctl, for the time being.


Inofficial first vice president of the Rust Evangelism Strike Force

Offline

#9 2020-02-25 15:31:04

Sinn12
Member
Registered: 2020-02-22
Posts: 14

Re: Network Manager sup-iface disconnected (reason -3) loop

Removed Deepin and all Dependencies and installed Gnome. Apparently Deepin has a problem with WPA2 Enterprise Networks

Offline

#10 2020-02-25 16:13:07

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,708
Website

Re: Network Manager sup-iface disconnected (reason -3) loop

Well, this is a drastic measure.
If the Deepin NM plugin really was the culprit, it should have sufficed to uninstall it and use NetworkManager e.g. from a CLI.
But hey, whatever floats your boat.
Please remember to mark the topic as solved by prepending [SOLVED] to the title of your original post.


Inofficial first vice president of the Rust Evangelism Strike Force

Offline

Board footer

Powered by FluxBB