Network: Unable to connect - No plugin supported this connection

theblackdog · 2015-04-25 21:50:50

As of recently I can't connect to any wireless Networks.
It must have happened with a update in the recent days, but as I mostly use the ethernet port of my Laptop I can't say for sure when it happened.
Wireless networks are still showing up but I'm unable to connect.

My Network card:

derped@K-LPC ~ $ lspci | grep Network
01:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)

The Package linux-firmware is installed and my system is using

derped@K-LPC ~ $ dmesg | grep firmware                                 
[    2.633820] iwlwifi 0000:01:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm

What I already tried:
I deactivated NetworkManager and used dhcpcd.
I tried to connect using wifi-menu and the NetworkManager apllet in Gnome.

Also I've received the message that there is "No plugin supported adding this connection".

derped@K-LPC ~ $ sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
   Active: active (running) since Sa 2015-04-25 22:40:15 CEST; 4min 25s ago
 Main PID: 248 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           ├─248 /usr/bin/NetworkManager --no-daemon
           └─820 /usr/bin/dhclient -d -q -sf /usr/lib/networkmanager/nm-dhcp-helper -pf /var/run/dhclient-enp2s0.pid -lf /var/lib/NetworkManager/dhclient-9ebe8050-842c-4de2-86a8-f9e11e7a07dd-enp2s0.lease -cf /var/lib/NetworkManager/dhclient-enp2s0.conf enp2s0

Apr 25 22:42:07 K-LPC NetworkManager[248]: <info>    nameserver '213.73.91.35'
Apr 25 22:42:07 K-LPC NetworkManager[248]: <info>    domain name 'hq.c3d2.de'
Apr 25 22:42:07 K-LPC NetworkManager[248]: <info>  (enp2s0): DHCPv4 state changed unknown -> bound
Apr 25 22:42:07 K-LPC NetworkManager[248]: <info>  (enp2s0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 25 22:42:07 K-LPC NetworkManager[248]: <info>  (enp2s0): Activation: Stage 5 of 5 (IPv4 Commit) started...
Apr 25 22:42:07 K-LPC NetworkManager[248]: <info>  Policy set 'Kabelgebundene Verbindung 1' (enp2s0) as default for IPv4 routing and DNS.
Apr 25 22:42:07 K-LPC NetworkManager[248]: <info>  Writing DNS information to /usr/bin/resolvconf
Apr 25 22:42:07 K-LPC dhclient[820]: bound to 172.22.99.175 -- renewal in 37918 seconds.
Apr 25 22:42:07 K-LPC NetworkManager[248]: <info>  (enp2s0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
Apr 25 22:42:10 K-LPC NetworkManager[248]: <warn>  Failed to activate 'C3D2': No plugin supported adding this connection

Thank's a lot in advance.

Last edited by theblackdog (2015-04-25 21:59:34)

jasonwryan · 2015-04-25 21:54:43

Please edit your post and add a meaningful title, this will help others find the thread: https://wiki.archlinux.org/index.php/Fo … ow_to_post

Moving to NC...

theblackdog · 2015-04-25 22:00:20

Sorry just forget to add it, I wasn't exactly sure what to use in the beginning. *added now*
As it actually is a network issue it would be nice it the thread would be kept in the Networking, Server, and Protection.

Last edited by theblackdog (2015-04-25 22:28:08)

jasonwryan · 2015-04-25 23:04:21

What errors do you get connecting manually?

theblackdog · 2015-04-26 01:48:29

When using wifi-menu:

derped@K-LPC ~ $ sudo wifi-menu
[sudo] Passwort für derped: 
Scanning for networks... done
/usr/bin/wifi-menu: Zeile 67: Successfully initialized wpa_supplicant
/tmp/essid.eBIw017b: Datei oder Verzeichnis nicht gefunden

Error: Expected at least 6 tokens for --menu, have 4.
Use --help to list options.


Aborted

nmtui:

Could not activate connection: No plugin supported adding this connection

using dhcpcd give's me a lot of errors, even though it uses a unmodified file (moved a .pacnew file in its place)

derped@K-LPC ~ $ sudo dhcpcd wlp1s0
wlp1s0: adding address fe80::a36e:3211:803a:531d
if_addaddress6: Permission denied
wlp1s0: starting wpa_supplicant
wlp1s0: failed to start wpa_supplicant
wlp1s0: Successfully initialized wpa_supplicant
Line 1264: unknown EAP method 'SIM'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1264: failed to parse eap 'SIM'.
Line 1267: failed to parse network block.
Line 1274: unknown EAP method 'PSK'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1274: failed to parse eap 'PSK'.
Line 1278: failed to parse network block.
Line 1310: unknown EAP method 'IKEV2'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1310: failed to parse eap 'IKEV2'.
Line 1313: failed to parse network block.
Line 1398: too large mode (value=5 max_value=4)
Line 1398: failed to parse mode '5'.
Line 1401: failed to parse network block.
Line 1406: too large mode (value=5 max_value=4)
Line 1406: failed to parse mode '5'.
Line 1408: invalid key_mgmt 'SAE'
Line 1408: no key_mgmt values configured.
Line 1408: failed to parse key_mgmt 'SAE'.
Line 1410: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant.conf'.
wlp1s0: waiting for carrier
timed out
dhcpcd exited

jasonwryan · 2015-04-26 03:14:45

What is this: /tmp/essid.eBIw017b: Datei oder Verzeichnis nicht gefunden

https://wiki.archlinux.org/index.php/Fo … s_and_code

Was wpa_supplicant one of the packages you upgraded?

theblackdog · 2015-04-26 03:46:48

It is a file not found message.
Yes it is, I already downgraded it and it gets me what seems like one step closer to solving the problem.

wifi-menu now lets me pick a wireless network but right after selecting one it quits with.

Job for netctl@wlp1s0\x2dC3D2.service failed.

Here is the systemctl status output for the service:

● netctl@wlp1s0\x2dC3D2.service - Networking for netctl profile wlp1s0-C3D2
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since So 2015-04-26 05:31:51 CEST; 19s ago
     Docs: man:netctl.profile(5)
  Process: 850 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 850 (code=exited, status=1/FAILURE)

and the relevant journal output:

-- Unit netctl@wlp1s0\x2dC3D2.service has begun starting up.
Apr 26 05:31:51 K-LPC network[850]: Starting network profile 'wlp1s0-C3D2'...
Apr 26 05:31:51 K-LPC network[850]: The interface of network profile 'wlp1s0-C3D2' is already up
Apr 26 05:31:51 K-LPC systemd[1]: netctl@wlp1s0\x2dC3D2.service: main process exited, code=exited, status=1/FAILURE
Apr 26 05:31:51 K-LPC systemd[1]: Failed to start Networking for netctl profile wlp1s0-C3D2.
-- Subject: Unit netctl@wlp1s0\x2dC3D2.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp1s0\x2dC3D2.service has failed.
-- 
-- The result is failed.
Apr 26 05:31:51 K-LPC sudo[772]: pam_unix(sudo:session): session closed for user root
Apr 26 05:31:51 K-LPC systemd[1]: Unit netctl@wlp1s0\x2dC3D2.service entered failed state.
Apr 26 05:31:51 K-LPC systemd[1]: netctl@wlp1s0\x2dC3D2.service failed.
Apr 26 05:31:51 K-LPC polkitd[283]: Unregistered Authentication Agent for unix-process:845:4175 (system bus name :1.46, object path /org/freedesktop/Po

jasonwryan · 2015-04-26 04:31:37

You really should disable all networking services and connect manually: it is the only way to narrow down exactly where and what is failing.

kkoceski · 2015-04-26 05:07:20

I just want to say that I'm having the same problem. theblackdog has dug much deeper into it though - I was only able to capture the "4 out of 6 token" error from wifi-menu.

The only help I can offer is that I did "clonezilla" back to an old image I had, and wifi-menu does work, and I can connect - not a hardware issue.

theblackdog · 2015-04-26 07:12:44

So I dug a little deeper and was (with a little help from a friend) able to connect to a wireless network.
Problem is my best guess why it isn't working is that the naming of my wireless device changed for no apparent reason.

How to reproduce:
Disable NetworkManager.service and reboot (or use the systemctl kill option as it respawns when using stop)

Here is the output of ifconfig & iwconfig

derped@K-LPC ~ $ ifconfig
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 100.70.136.51  netmask 255.255.192.0  broadcast 100.70.191.255
        inet6 fe80::762b:62ff:fe6e:7848  prefixlen 64  scopeid 0x20<link>
        ether 74:2b:62:6e:78:48  txqueuelen 1000  (Ethernet)
        RX packets 64239  bytes 94239532 (89.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 34567  bytes 3163690 (3.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 8  bytes 480 (480.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 480 (480.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

derped@K-LPC ~ $ iwconfig
enp2s0    no wireless extensions.

wlp1s0    IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=16 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          
lo        no wireless extensions.

The funny thing here is that my wireless device isn't showing up in my ifconfig output.
So I did:

sudo ifconfig wlp1s0 up

Now it shows up (no pun intended) in my ifconfig:

derped@K-LPC ~ $ ifconfig                                                       
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 100.70.136.51  netmask 255.255.192.0  broadcast 100.70.191.255
        inet6 fe80::762b:62ff:fe6e:7848  prefixlen 64  scopeid 0x20<link>
        ether 74:2b:62:6e:78:48  txqueuelen 1000  (Ethernet)
        RX packets 66650  bytes 94448852 (90.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 34703  bytes 3189914 (3.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 8  bytes 480 (480.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 480 (480.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp1s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:c2:c6:6b:d6:cc  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Now I used iwconfig to Choose the Network I want to connect to:

sudo iwconfig wlp1s0 essid C3D2

And finally I used dhclient to connect:

sudo dhclient wlp1s0

The steps may vary a bit since I did that a few hours ago and as I don't have any wireless networks where I'm right now I'm unable to test it.
Since it would be a huge pain to do that every time I boot and I'd rather prefer a actually working system this doesn't solve my Problem.

Last edited by theblackdog (2015-04-26 07:21:15)

jasonwryan · 2015-04-26 07:19:24

You can use a udev rule to rename the interface to something predictable: https://wiki.archlinux.org/index.php/Ne … evice_name

Arch Linux

#1 2015-04-25 21:50:50

Network: Unable to connect - No plugin supported this connection

#2 2015-04-25 21:54:43

Re: Network: Unable to connect - No plugin supported this connection

#3 2015-04-25 22:00:20

Re: Network: Unable to connect - No plugin supported this connection

#4 2015-04-25 23:04:21

Re: Network: Unable to connect - No plugin supported this connection

#5 2015-04-26 01:48:29

Re: Network: Unable to connect - No plugin supported this connection

#6 2015-04-26 03:14:45

Re: Network: Unable to connect - No plugin supported this connection

#7 2015-04-26 03:46:48

Re: Network: Unable to connect - No plugin supported this connection

#8 2015-04-26 04:31:37

Re: Network: Unable to connect - No plugin supported this connection

#9 2015-04-26 05:07:20

Re: Network: Unable to connect - No plugin supported this connection

#10 2015-04-26 07:12:44

Re: Network: Unable to connect - No plugin supported this connection

#11 2015-04-26 07:19:24

Re: Network: Unable to connect - No plugin supported this connection

Board footer