[SOLVED] Cannot connect to the special Wi-Fi router

ornichola · 2017-04-06 20:28:58

Hello!
I've got an interesting problem using Arch. I cannot connect to the special Wi-Fi router which succesfully connects other devices. My laptop is Lenovo v580c, previosly it had Ubuntu and recently I've installed Arch (want to go deeper into Linux world). So when laptop was with Ubuntu, I could connect to the same router without any problems but after installing Arch I cannot.

The detailed steps are following:

I installed plasma-nm and networkmanager on my laptop with Arch
In Network Manager applet I choose my Wi-Fi network and press connect
There 'Configuring interface' message appears with loading status near it
'Password dialog - KDE Daemon' popup window appears asking me to enter password
After entering password and pressing 'OK' it dissappeared but after a while (about 5-15 seconds) it is shown again

Few valuable notes:

Laptop succesfully connects to any other Wi-Fi network (tried mobile hotspot, some ZyXel router and college WLAN network)
Laptop succesfully connects to the same problem router by Ethernet connection
Other laptop with Arch and KDE Plasma also cannot connect to my router

So according to that, there can be two roots of the problem - Arch or router. Where should I start digging? Need your help, guys.

ip link output

3: wlp3s0b1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether 6e:da:8e:f2:c4:a9 brd ff:ff:ff:ff:ff:ff

lspci -k output

03:00.0 Network controller: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter (rev 01)
	Subsystem: Broadcom Limited Device 0608
	Kernel driver in use: bcma-pci-bridge
	Kernel modules: bcma

journalctl -f output during connection

Apr 06 22:13:04 v580c wpa_supplicant[340]: wlp3s0b1: SME: Trying to authenticate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
Apr 06 22:13:04 v580c kernel: wlp3s0b1: authenticate with 7c:26:64:02:77:e6
Apr 06 22:13:04 v580c kernel: wlp3s0b1: send auth to 7c:26:64:02:77:e6 (try 1/3)
Apr 06 22:13:04 v580c NetworkManager[316]: <info>  [1491505984.9458] device (wlp3s0b1): supplicant interface state: scanning -> authenticating
Apr 06 22:13:04 v580c wpa_supplicant[340]: wlp3s0b1: Trying to associate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
Apr 06 22:13:04 v580c kernel: wlp3s0b1: authenticated
Apr 06 22:13:04 v580c kernel: wlp3s0b1: associate with 7c:26:64:02:77:e6 (try 1/3)
Apr 06 22:13:04 v580c NetworkManager[316]: <info>  [1491505984.9535] device (wlp3s0b1): supplicant interface state: authenticating -> associating
Apr 06 22:13:04 v580c kernel: wlp3s0b1: associate with 7c:26:64:02:77:e6 (try 2/3)
Apr 06 22:13:05 v580c kernel: wlp3s0b1: associate with 7c:26:64:02:77:e6 (try 3/3)
Apr 06 22:13:05 v580c kernel: wlp3s0b1: association with 7c:26:64:02:77:e6 timed out
Apr 06 22:13:05 v580c NetworkManager[316]: <info>  [1491505985.2012] device (wlp3s0b1): supplicant interface state: associating -> disconnected
Apr 06 22:13:05 v580c NetworkManager[316]: <info>  [1491505985.3013] device (wlp3s0b1): supplicant interface state: disconnected -> scanning
Apr 06 22:13:06 v580c wpa_supplicant[340]: wlp3s0b1: SME: Trying to authenticate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
Apr 06 22:13:06 v580c kernel: wlp3s0b1: authenticate with 7c:26:64:02:77:e6
Apr 06 22:13:06 v580c kernel: wlp3s0b1: send auth to 7c:26:64:02:77:e6 (try 1/3)
Apr 06 22:13:06 v580c NetworkManager[316]: <info>  [1491505986.3086] device (wlp3s0b1): supplicant interface state: scanning -> authenticating
Apr 06 22:13:06 v580c wpa_supplicant[340]: wlp3s0b1: Trying to associate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
Apr 06 22:13:06 v580c kernel: wlp3s0b1: authenticated
Apr 06 22:13:06 v580c kernel: wlp3s0b1: associate with 7c:26:64:02:77:e6 (try 1/3)
Apr 06 22:13:06 v580c NetworkManager[316]: <info>  [1491505986.3168] device (wlp3s0b1): supplicant interface state: authenticating -> associating

Last edited by ornichola (2017-04-12 20:35:18)

jasonwryan · 2017-04-06 20:40:31

Don't use NM: connect manually to produce informative error messages.

ornichola · 2017-04-06 21:34:08

Executed command

wpa_supplicant -D nl80211,wext -i wlp3s0b1 -c <(wpa_passphrase "kwerty" "<REDACTED>")

and got following output:

[root@v580c ornichola]# wpa_supplicant -D nl80211,wext -i wlp3s0b1 -c <(wpa_passphrase "kwerty" "<REDACTED>")
Successfully initialized wpa_supplicant
wlp3s0b1: SME: Trying to authenticate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: Trying to associate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: SME: Trying to authenticate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: Trying to associate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: SME: Trying to authenticate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: Trying to associate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: SME: Trying to authenticate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: Trying to associate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="kwerty" auth_failures=1 duration=10 reason=CONN_FAILED
wlp3s0b1: CTRL-EVENT-SSID-REENABLED id=0 ssid="kwerty"
wlp3s0b1: SME: Trying to authenticate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: Trying to associate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="kwerty" auth_failures=2 duration=23 reason=CONN_FAILED
wlp3s0b1: CTRL-EVENT-SSID-REENABLED id=0 ssid="kwerty"
wlp3s0b1: SME: Trying to authenticate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="kwerty" auth_failures=3 duration=46 reason=CONN_FAILED
wlp3s0b1: CTRL-EVENT-SSID-REENABLED id=0 ssid="kwerty"
wlp3s0b1: SME: Trying to authenticate with 7c:26:64:02:77:e6 (SSID='kwerty' freq=2462 MHz)
wlp3s0b1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="kwerty" auth_failures=4 duration=77 reason=CONN_FAILED
^Cnl80211: deinit ifname=wlp3s0b1 disabled_11b_rates=0
wlp3s0b1: CTRL-EVENT-TERMINATING

The /etc/wpa_supplicant/example.conf file contains:

network={
	ssid="kwerty"
	#psk="<REDACTED>"
	psk=<LONG REDACTED HEX STRING>
}

Moderator edit: I went ahead and redacted your passphrase on this very public forum - ewaller

Last edited by ewaller (2017-04-06 22:42:18)

R00KIE · 2017-04-07 10:14:12

The lines like this "wlp3s0b1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="kwerty" auth_failures=4 duration=77 reason=CONN_FAILED" seem to indicate you are trying to use a wrong password. The only thing I can think of right now is that if your password has spaces or special characters (symbols or non-english characters) you have to pay special care when passing that to wpa_supplicant or wpa_passphrase.

You will have to provide more details about the network itself, the output of 'iwlist wlp3s0b1 scan' will help getting more details. Any other useful info you might have about the network, such as if there are any guides on how to setup the connection for other OSes or for Ubuntu will also help.

seth · 2017-04-07 14:43:33

There's no AUTH_FAILED or WRONG_KEY in that log.

systemctl list-unit-files| grep -iE '(net|conn|wicd|dhcp)' # the ordinary NM interference
iw scan # low signal strength?

What kind of router is that and which protocols (11bgn) is it supposed to support. Is there perhaps a MAC filter (whitelist)?

ornichola · 2017-04-07 19:57:29

R00KIE wrote:

seem to indicate you are trying to use a wrong password.

Password does not contain any special symbols or non-english letters, only capital and lower case letters and digits. I also rechecked correctness of input and deleted saved network on other devices and succesfully recconected again with same password.

R00KIE wrote:

the output of 'iwlist wlp3s0b1 scan' will help getting more details.

Here is output of the command:

Cell 01 - Address: 7C:26:64:02:77:E6
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=63/70  Signal level=-47 dBm  
                    Encryption key:on
                    ESSID:"kwerty"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000000d508f4f17e
                    Extra: Last beacon: 153ms ago
                    IE: Unknown: 00066B7765727479
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 03010B
                    IE: Unknown: 050400010002
                    IE: Unknown: 2A0104
                    IE: Unknown: 32043048606C
                    IE: Unknown: 2D1A6E181FFFFF000000000000000000000000000000000000000000
                    IE: Unknown: 3D160B070000000000000000000000000000000000000000
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: DD1E00904C336E181FFFFF000000000000000000000000000000000000000000
                    IE: Unknown: DD1A00904C340B070000000000000000000000000000000000000000
                    IE: Unknown: DD0600E04C020160
                    IE: Unknown: DD180050F204104A00011010440001021049000600372A000120

I didn't have any other guides to different OSes - my previous OS on this laptop was Ubuntu 16.04, it was just connected by default network applet. (By the way, it was connected with the same password).

ornichola · 2017-04-07 20:13:30

seth wrote:

systemctl list-unit-files| grep -iE '(net|conn|wicd|dhcp)' # the ordinary NM interference

Output:

org.freedesktop.network1.busname                                       static   
sys-fs-fuse-connections.mount                                          static   
dbus-org.freedesktop.network1.service                                  disabled 
dbus-org.freedesktop.NetworkManager.service                            enabled  
dhcpcd.service                                                         disabled 
dhcpcd@.service                                                        disabled 
netctl-auto@.service                                                   disabled 
netctl-ifplugd@.service                                                disabled 
netctl-sleep.service                                                   disabled 
netctl.service                                                         disabled 
netctl@.service                                                        static   
NetworkManager-dispatcher.service                                      enabled  
NetworkManager-wait-online.service                                     disabled 
NetworkManager.service                                                 enabled  
systemd-networkd-wait-online.service                                   disabled 
systemd-networkd.service                                               disabled 
telnet@.service                                                        static   
systemd-networkd.socket                                                disabled 
telnet.socket                                                          disabled 
network-online.target                                                  static   
network-pre.target                                                     static   
network.target                                                         static

seth wrote:

What kind of router is that and which protocols (11bgn) is it supposed to support. Is there perhaps a MAC filter (whitelist)?

My router is "Sagemcom 1744 v4" - it is promouting device from my provider 'Rostelekom' (for feature newbie searches: "Ростелеком"). Band: 2.4Ghz (B+G+N), Mode: AP. MAC filter is empty, no whitelisted or blacklisted devices are present.

Trilby · 2017-04-07 20:46:16

The most common cause of networking problems is having two services competing for the same device. In this case it looks like you have *every* networking service running.

Stop all of them, kill any backgrounded dhcpcd and wpa_supplicant processes, then try wpa_supplicant again (but drop the -D flag, it very rarely solves problems, but frequently causes them).

EDIT: oops, sorry. I missed that that list included disabled units.

seth · 2017-04-07 21:01:33

NetworkManager.service                                                 enabled

To be sure: you stopped that?

systemctl status NetworkManager

(Otherwise all wpa_supplicant tests are futile)

it is promouting device from my provider 'Rostelekom'

Can you connect unencrypted?

seth · 2017-04-07 21:03:00

@Trilby - he's got only NM enabled, the static setup looks fine.

equ · 2017-04-08 05:26:34

may be router itself has some logs?

Last edited by equ (2017-04-08 05:35:30)

R00KIE · 2017-04-08 14:01:45

I don't see anything that stands out as possibly causing the problem. Do as others have said, make sure nothing is trying to compete for access to the wireless card and see if it works trying to connect manually with wpa_supplicant.

If that doesn't work I would look into trying to use older firmware versions of your wireless card (if it uses any). If I recall correctly I've seen some people have trouble with more recent firmware for broadcom cards. I might be remembering incorrectly though, so search the forum for any similar problems before you spend too much time following that lead.

ornichola · 2017-04-08 20:05:49

seth wrote:

To be sure: you stopped that?

I tried with stopped and with enabled and got same results.

equ wrote:

may be router itself has some logs?

Yes, it is, but the log last record is Jan, 12.

Let me explain my steps trying to connect more detailed:

1. I disabled NetworkManager.service using

systemctl disable NetworkManager.service

Result: Network Manager disables with it's dependencies, applet in system tray becomes red, no wired internet.

2. Reboot, entered in 'su' mode. Executed:

wpa_supplicant -B -i wlp3s0b1 -c <(wpa_passphrase MYSSID MYPASSPHRASE)

Result, console return 'Successfully initialized wpa_supplicant', but no /etc/wpa_supplicant/example.conf file created. I don't know why, because previosly it creates succesfully.

3. Manually created /etc/wpa_supplicant/example.conf containing:

ctrl_interface=/run/wpa_supplicant
update_config=1

network={
    ssid="MYSSID"
    psk="MYPASSPHRASE"
}

4. Executed dhcpcd wlp3s0b1, got:

[root@v580c ornichola]# dhcpcd wlp3s0b1
wlp3s0b1: waiting for carrier
timed out
dhcpcd exited
[root@v580c ornichola]#

There is the point where I stucked.

But now I've got new info. I tried to connect with steps mentioned above to the different router, but samely promouted by Rostelekom provider (ZTE ZXHN H118N) and results were same. Moreover, now I cannot connect to the device that established connection succesfully - my smartphone hotspot. Here is two journal log files, created during connection to the ZTE router:

Log 1. Network Manager enabled as service, tried to connect using wpa_supplicant (steps described above).

Log 2. Network Manager disabled as service, tried to connect using wpa_supplicant (steps described above).

ornichola · 2017-04-08 20:10:20

seth wrote:

Can you connect unencrypted?

I disabled WPA2 encyption on my router and setted None, disabled Network Manager, created /etc/wpa_supplicant/example.conf containing

network={
    ssid="kwerty"
    key_mgmt=NONE
}

and still got same results

[root@v580c ornichola]# dhcpcd wlp3s0b1
wlp3s0b1: waiting for carrier
timed out
dhcpcd exited
[root@v580c ornichola]#

Tried this using Network Manager applet and also cannot establish connection, the difference is that no 'Password dialog - KDE Daemon' appears.

ornichola · 2017-04-08 20:45:22

Additionally installed b43-firmware from Broadcom wireless wiki page. Results are still the same, Network Manager reasking password each time, wpa supplicant stuck at dhcpcd wlp3s0b1 command.

Last edited by ornichola (2017-04-08 20:45:35)

ornichola · 2017-04-12 20:34:31

The problem was solved. Final result - laptop can connect to wireless networks using GUI of Network Manager (Plasma 5).

The root of it was hiding in the Broadcom BCM4313 wireless adapter's driver. Although device was recognized by the system, with following output of lspci -k:

03:00.0 Network controller: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter (rev 01)
    Subsystem: Broadcom Limited Device 0608
    Kernel driver in use: bcma-pci-bridge
    Kernel modules: bcma

and even could successfully establish connections with some networks, it failures on the certain devices (Rostelekom ISP promouting routers). I don't know what feature caused the problem exactly, I don't have a good knowledge of networking at this time.

My steps to solve the problem are following:
1. Arch was newly installed (no actions with wpa supplicant and wpa_cli were performed)
2. broadcom-wl package was installed
3. Blacklist few other Broadcom modules - create file sudo nano /etc/modprobe.d/blacklist.conf, containing:

blacklist bcma
blacklist b43
blacklist b43legacy
blacklist brcm80211
blacklist ssb

4. Install networkmanager and plasma-nm packages
5. Disable services:
sudo systemctl disable dhcpcd@enp4s0.service
sudo systemctl disable netctl-auto@wlp3s0b1.service
5. Enable Network Manager as service:
sudo systemctl enable NetworkManager.service
6. reboot

After those steps I can successfully establish connection with router. During test connection behaves stable, though I should always enter my password in 'Password dialog - KDE Daemon' before connecting, but I think this is another problem.

Some helpful links:
1. Broadcom Wireless
2. [SOLVED] Connection keeps dropping with Broadcom BCM4313
3. [SOLVED] How to get Broadcom wireless to work (Arch install)?
4. Total Newb: Unable to connect with Broadcom wifi card

Search keywords: Wi-Fi router drops connection, не подлючается к роутеру, Ростелеком, broadcom bcm4313

Arch Linux

#1 2017-04-06 20:28:58

[SOLVED] Cannot connect to the special Wi-Fi router

#2 2017-04-06 20:40:31

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#3 2017-04-06 21:34:08

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#4 2017-04-07 10:14:12

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#5 2017-04-07 14:43:33

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#6 2017-04-07 19:57:29

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#7 2017-04-07 20:13:30

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#8 2017-04-07 20:46:16

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#9 2017-04-07 21:01:33

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#10 2017-04-07 21:03:00

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#11 2017-04-08 05:26:34

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#12 2017-04-08 14:01:45

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#13 2017-04-08 20:05:49

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#14 2017-04-08 20:10:20

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#15 2017-04-08 20:45:22

Re: [SOLVED] Cannot connect to the special Wi-Fi router

#16 2017-04-12 20:34:31

Re: [SOLVED] Cannot connect to the special Wi-Fi router

Board footer