You are not logged in.

Pages: 1 2

#1 2016-09-22 07:20:37

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Can't connect to specific wi-fi network

I have a Acer E5-523 laptop with a QCA9377 network adapter.

I manage to connect to my school network and to my cellphone wi-fi network so apparently my hardware does work correctly. Unfortunately I can't connect to my home network as I keep getting prompted to insert my wi-fi password (which I for sure know it's the correct password). I have also tried disabling security on my router and apparently I get a connection but it won't even let me access my router and I won't get an internet connection.

I have other devices which can connect to this network with no problem (cellphones and other Linux PCs). I actually get an internet connection if I connect my laptop via ethernet to my home router. If it helps I got an Arris WTM552 router. Hopefully I can provide more information if needed. Thanks in advance.

Offline

#2 2016-09-22 07:23:46

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: Can't connect to specific wi-fi network

What prompts for your password? What network management tool are you using? Have you tried connecting manually? What is the output of that process?


Moving to NC...

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2016-09-22 07:35:46

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

Sorry for posting on wrong section. Using NetworkManager.

This is how I have tried connecting manually

nmcli dev wifi connect [SSID]
Error: Connection activation failed: (7) Secrets were required, but not provided.

It keeps asking for password and when I cancel I get that message.

Offline

#4 2016-09-22 08:32:45

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: Can't connect to specific wi-fi network

That's not connecting manually, this is: https://wiki.archlinux.org/index.php/Wi … nual_setup

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#5 2016-09-22 08:56:23

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

This is what I got. It gets looped. 100% sure password is correct.

Successfully initialized wpa_supplicant
Could not read interface p2p-dev-wlp3s0 flags: No such device
nl80211: Could not set interface 'p2p-dev-wlp3s0' UP
nl80211: deinit ifname=p2p-dev-wlp3s0 disabled_11b_rates=0
p2p-dev-wlp3s0: Failed to initialize driver interface
P2P: Failed to enable P2P Device interface
wlp3s0: SME: Trying to authenticate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
wlp3s0: Trying to associate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
wlp3s0: Associated with 00:15:a2:75:ff:72
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=00:15:a2:75:ff:72 reason=3 locally_generated=1
wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=1 duration=10 reason=WRONG_KEY
wlp3s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="MySSID"
wlp3s0: SME: Trying to authenticate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
wlp3s0: Trying to associate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
wlp3s0: Associated with 00:15:a2:75:ff:72
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=00:15:a2:75:ff:72 reason=3 locally_generated=1
wlp3s0: SME: Trying to authenticate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
wlp3s0: Trying to associate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
wlp3s0: Associated with 00:15:a2:75:ff:72
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=00:15:a2:75:ff:72 reason=2 locally_generated=1
wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=2 duration=20 reason=WRONG_KEY
nl80211: send_and_recv->nl_recvmsgs failed: -33
wlp3s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="MySSID"
wlp3s0: SME: Trying to authenticate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
wlp3s0: Trying to associate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
wlp3s0: Associated with 00:15:a2:75:ff:72
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=00:15:a2:75:ff:72 reason=3 locally_generated=1
wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=3 duration=30 reason=CONN_FAILED
wlp3s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="MySSID"
wlp3s0: SME: Trying to authenticate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
wlp3s0: Trying to associate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
wlp3s0: Associated with 00:15:a2:75:ff:72
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=00:15:a2:75:ff:72 reason=3 locally_generated=1
wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=4 duration=60 reason=WRONG_KEY

Last edited by ArchEdu (2016-09-22 09:36:05)

Offline

#6 2016-09-22 09:44:04

Starfish
Member
From: Germany
Registered: 2015-10-21
Posts: 134

Re: Can't connect to specific wi-fi network

ArchEdu wrote:

This is what I got
...

I assume this is what you got from running wpa_supplicant. Posting the shell prompt with the executed command as well would be nice.

ioctl ... Operation not permitted

sounds like you where doing something as an ordinary user that needed root permissions. If you were about connect to your router, you should try again as root.

EDIT: OP changed his last output after I posted this.

Last edited by Starfish (2016-09-22 09:47:55)

"Yesterday is history, tomorrow is a mystery, but today is a gift. That is why it is called the present." - Master Oogway

Offline

#7 2016-09-22 20:02:54

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

Starfish wrote:
ArchEdu wrote:

This is what I got
...

I assume this is what you got from running wpa_supplicant. Posting the shell prompt with the executed command as well would be nice.

ioctl ... Operation not permitted

sounds like you where doing something as an ordinary user that needed root permissions. If you were about connect to your router, you should try again as root.

EDIT: OP changed his last output after I posted this.

Yes, I used wpa_supplicant to connect to the network. I did changed the output after succesfully running the command.

Offline

#8 2016-09-22 20:46:34

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: Can't connect to specific wi-fi network

ArchEdu wrote:

This is what I got. It gets looped. 100% sure password is correct.

wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=1 duration=10 reason=WRONG_KEY

Then something else is going on because the error message is pretty obvious. Do you have a config file somewhere with the passphrase in it?

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#9 2016-09-22 21:14:29

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

This is quite strange indeed.

This is the command I'm executing

sudo wpa_supplicant -iath10k -iwlp3s0 -c/etc/wpa_supplicant/wpa_supplicant.conf

This is the part of my wpa_supplicant.conf file where I stored the password

network={
        ssid="MySSID"
        psk="passphrase"
        key_mgmt=WPA-PSK
}

I know wpa_supplicant.conf is basically documentation but I have deleted all example networks, so my network is the only network in the configuration file.

My router is really old and my network adapter is fairly new, could this be some kind of compatibility issue?

Offline

#10 2016-09-22 21:31:13

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: Can't connect to specific wi-fi network

Assuming the passphrase is correct and there are no trailing spaces, or malformed characters etc., have you tried commenting out the key_mgmt value?

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#11 2016-09-22 22:00:00

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

Just tried with key_mgmt commented and I keed getting the same wrong key error.

Offline

#12 2016-09-22 22:08:26

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: Can't connect to specific wi-fi network

Change the key, temporarily, to something else; see if that works. Otherwise, I have nothing more to suggest.

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#13 2016-09-22 22:10:58

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

I'm going to try disabling security again and connecting manually, see if I get any errors. When I tried this before with NetworkManager it appeared as if I was connected but couldn't even access the router.

EDIT: Same as before. Disabling security gets me connected with no internet access and no access to the router. How can I be connected without being able to access my router?

Last edited by ArchEdu (2016-09-22 22:23:58)

Offline

#14 2016-09-22 22:32:47

onslow77
Member
Registered: 2014-09-21
Posts: 279

Re: Can't connect to specific wi-fi network

ArchEdu wrote:

I know wpa_supplicant.conf is basically documentation but I have deleted all example networks, so my network is the only network in the configuration file.

Hello!

My guess is that you have not followed the wpa_supplicant wiki properly, or you only missed that the wiki under the Troubleshooting section wrote:

"Warning: Make sure that you are not using the default configuration file at /etc/wpa_supplicant/wpa_supplicant.conf, which is filled with uncommented examples that will lead to lots of random errors in practice. This is a known packaging bug of the wpa_supplicant package: FS#40661."

Regards
Martin

Last edited by onslow77 (2016-09-22 22:37:59)

It is advised to follow the How to post guide when posting on the Arch forum. If one consciously jumps over these elementary steps like reading the wiki and providing necessary information about the problem, one can be regarded as a Help Vampire.

Offline

#15 2016-09-22 22:39:57

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,532
Website

Re: Can't connect to specific wi-fi network

onslow, that is an overly cautious (and a bit silly if you ask me) warning.  I use the same file myself - I just deleted all the crap that comes in it.  The OP has indicated that he has also removed all other network blocks.  Assuming this is true, that file is perfectly fine to use (though that assumption is worth double checking).

Often manually created wpa_supplicant.conf network blocks will work just fine, but in some cases additional parameters are needed, and it can be real hell trying to figure out what they are.  Remove your network block, or even everything in the file, and replace it with just the following:

ctrl_interface=/run/wpa_supplicant
update_config=1

The fire up a background wpa_supplicant process, and use wpa_cli to create a network (i.e. connect) and let it write the network info to the config file for you.

I normally hand edit my conf file - but for a few pesky networks, wpa_cli has saved me a lot of hassle.

I'm not an expert at reading wpa_supplicant output, but the errors seem suggestive (to me) that another key_mgmt method might be needed (WPA-EAP maybe?) and some of those need several additional parameters.

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#16 2016-09-22 22:43:03

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

Thanks for your reply Martín. I already posted the command I used to connect and as I said before I did erase all the example networks in wpa_supplicant.config

ArchEdu wrote:

I know wpa_supplicant.conf is basically documentation but I have deleted all example networks, so my network is the only network in the configuration file.

Offline

#17 2016-09-22 23:01:30

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

Trilby wrote:

onslow, that is an overly cautious (and a bit silly if you ask me) warning.  I use the same file myself - I just deleted all the crap that comes in it.  The OP has indicated that he has also removed all other network blocks.  Assuming this is true, that file is perfectly fine to use (though that assumption is worth double checking).

Often manually created wpa_supplicant.conf network blocks will work just fine, but in some cases additional parameters are needed, and it can be real hell trying to figure out what they are.  Remove your network block, or even everything in the file, and replace it with just the following:

ctrl_interface=/run/wpa_supplicant
update_config=1

The fire up a background wpa_supplicant process, and use wpa_cli to create a network (i.e. connect) and let it write the network info to the config file for you.

I normally hand edit my conf file - but for a few pesky networks, wpa_cli has saved me a lot of hassle.

I'm not an expert at reading wpa_supplicant output, but the errors seem suggestive (to me) that another key_mgmt method might be needed (WPA-EAP maybe?) and some of those need several additional parameters.

Erased everything in the configuration file and added what you suggested. Then executed wpa_supplicant and it froze:

$ sudo wpa_supplicant -i wlp3s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
[sudo] password for root: 
Successfully initialized wpa_supplicant
Could not read interface p2p-dev-wlp3s0 flags: No such device
nl80211: Could not set interface 'p2p-dev-wlp3s0' UP
nl80211: deinit ifname=p2p-dev-wlp3s0 disabled_11b_rates=0
p2p-dev-wlp3s0: Failed to initialize driver interface
P2P: Failed to enable P2P Device interface

Last edited by ArchEdu (2016-09-22 23:02:25)

Offline

#18 2016-09-22 23:03:31

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,532
Website

Re: Can't connect to specific wi-fi network

Good, the above is to be expected.  Continue ...

Trilby wrote:

The fire up a background wpa_supplicant process, and use wpa_cli

https://wiki.archlinux.org/index.php/WP … th_wpa_cli

Posting the line for your network from the scan results might be helpful too.

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#19 2016-09-22 23:22:36

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

Followed the instructions. Here is my network from scan_results:

> scan_results
bssid / frequency / signal level / flags / ssid
00:15:a2:75:ff:72	2462	-52	[WPA-PSK-TKIP][ESS]	MySSID

Then attempting to connect(it loops again)

> add_network
0
> set_network 0 ssid "MySSID"
OK
> set_network 0 psk "passphrase"
OK
> enable_network 0
OK
<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>SME: Trying to authenticate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
<3>Trying to associate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
<3>Associated with 00:15:a2:75:ff:72
<3>CTRL-EVENT-DISCONNECTED bssid=00:15:a2:75:ff:72 reason=3 locally_generated=1
<3>WPA: 4-Way Handshake failed - pre-shared key may be incorrect
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=1 duration=10 reason=WRONG_KEY
<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="MySSID"
<3>SME: Trying to authenticate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
<3>Trying to associate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
<3>Associated with 00:15:a2:75:ff:72
<3>CTRL-EVENT-DISCONNECTED bssid=00:15:a2:75:ff:72 reason=3 locally_generated=1
<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>SME: Trying to authenticate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
<3>CTRL-EVENT-SCAN-STARTED 
<3>Trying to associate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>Associated with 00:15:a2:75:ff:72
<3>CTRL-EVENT-DISCONNECTED bssid=00:15:a2:75:ff:72 reason=3 locally_generated=1
<3>WPA: 4-Way Handshake failed - pre-shared key may be incorrect
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=2 duration=23 reason=WRONG_KEY
<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="MySSID"
<3>SME: Trying to authenticate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
<3>Trying to associate with 00:15:a2:75:ff:72 (SSID='MySSID' freq=2462 MHz)
<3>Associated with 00:15:a2:75:ff:72
<3>CTRL-EVENT-DISCONNECTED bssid=00:15:a2:75:ff:72 reason=3 locally_generated=1
<3>WPA: 4-Way Handshake failed - pre-shared key may be incorrect
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=3 duration=46 reason=WRONG_KEY
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=4 duration=77 reason=CONN_FAILED
<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE

Offline

#20 2016-09-22 23:28:30

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,532
Website

Re: Can't connect to specific wi-fi network

Hmm, can you post a pstree output from when it fails?

EDIT: actuall, I think TKIP is the issue.  You need more lines in your config for that, standby. (but do check that no other networking process is running.)  Hmm, I can't find any good examples other than what's in the wpa_supplicant.conf man page and I've never used a TKIP network.

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#21 2016-09-22 23:47:04

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

Here is the pstree output

$ pstree -ap
systemd,1
  ├─NetworkManager,443 --no-daemon
  │   ├─{gdbus},459
  │   ├─{gmain},457
  │   └─{pool},1087
  ├─accounts-daemon,501
  │   ├─{gdbus},504
  │   └─{gmain},502
  ├─bluetoothd,438
  ├─colord,623
  │   ├─{gdbus},626
  │   └─{gmain},624
  ├─dbus-daemon,441 --system --address=systemd: --nofork --nopidfile--systemd-
  ├─gdm,464
  │   ├─gdm-session-wor,514
  │   │   ├─gdm-wayland-ses,525gnome-session --autostart /usr/share/gdm/greete
  │   │   │   ├─gnome-session-b,527 --autostart/usr/share/gdm/greeter/a
  │   │   │   │   ├─gnome-settings-,603
  │   │   │   │   │   ├─{dconf worker},621
  │   │   │   │   │   ├─{gdbus},620
  │   │   │   │   │   ├─{gmain},618
  │   │   │   │   │   ├─{gnome-settings-},617
  │   │   │   │   │   └─{pool},619
  │   │   │   │   ├─gnome-shell,539
  │   │   │   │   │   ├─Xwayland,568 :1024 -rootless -noreset -listen 4 ...
  │   │   │   │   │   │   ├─{Xwayland},569
  │   │   │   │   │   │   ├─{llvmpipe-0},570
  │   │   │   │   │   │   └─{llvmpipe-1},571
  │   │   │   │   │   ├─{JS GC Helper},591
  │   │   │   │   │   ├─{JS Sour~ Thread},592
  │   │   │   │   │   ├─{dconf worker},567
  │   │   │   │   │   ├─{gdbus},541
  │   │   │   │   │   ├─{gmain},540
  │   │   │   │   │   ├─{gnome-shell},565
  │   │   │   │   │   └─{threaded-ml},583
  │   │   │   │   ├─{dconf worker},537
  │   │   │   │   ├─{gdbus},535
  │   │   │   │   └─{gmain},534
  │   │   │   ├─{gdbus},528
  │   │   │   └─{gmain},526
  │   │   ├─{gdbus},516
  │   │   └─{gmain},515
  │   ├─gdm-session-wor,636
  │   │   ├─gdm-x-session,654 --run-script gnome-session
  │   │   │   ├─Xorg,656 vt2 -displayfd 3 -auth ...
  │   │   │   │   └─{Xorg},657
  │   │   │   ├─gnome-session-b,661
  │   │   │   │   ├─gnome-settings-,808
  │   │   │   │   │   ├─{dconf worker},818
  │   │   │   │   │   ├─{gdbus},817
  │   │   │   │   │   ├─{gmain},815
  │   │   │   │   │   ├─{pool},820
  │   │   │   │   │   └─{pool},1089
  │   │   │   │   ├─gnome-shell,704
  │   │   │   │   │   ├─{JS GC Helper},734
  │   │   │   │   │   ├─{JS Sour~ Thread},735
  │   │   │   │   │   ├─{dconf worker},715
  │   │   │   │   │   ├─{gdbus},707
  │   │   │   │   │   ├─{gmain},705
  │   │   │   │   │   ├─{gnome-shell},706
  │   │   │   │   │   └─{threaded-ml},729
  │   │   │   │   ├─gnome-tweak-too,825 ...
  │   │   │   │   │   ├─{gdbus},886
  │   │   │   │   │   └─{gmain},885
  │   │   │   │   ├─tracker-extract,823
  │   │   │   │   │   ├─{dconf worker},850
  │   │   │   │   │   ├─{gdbus},852
  │   │   │   │   │   ├─{gmain},851
  │   │   │   │   │   ├─{pool},958
  │   │   │   │   │   ├─{pool},959
  │   │   │   │   │   ├─{pool},960
  │   │   │   │   │   ├─{pool},961
  │   │   │   │   │   ├─{pool},962
  │   │   │   │   │   ├─{pool},963
  │   │   │   │   │   ├─{pool},964
  │   │   │   │   │   ├─{pool},965
  │   │   │   │   │   ├─{pool},966
  │   │   │   │   │   └─{pool},967
  │   │   │   │   ├─tracker-miner-a,832
  │   │   │   │   │   ├─{dconf worker},985
  │   │   │   │   │   ├─{gdbus},844
  │   │   │   │   │   └─{gmain},843
  │   │   │   │   ├─tracker-miner-f,837
  │   │   │   │   │   ├─{dconf worker},847
  │   │   │   │   │   ├─{gdbus},849
  │   │   │   │   │   └─{gmain},848
  │   │   │   │   ├─tracker-miner-u,838
  │   │   │   │   │   ├─{dconf worker},987
  │   │   │   │   │   ├─{gdbus},846
  │   │   │   │   │   └─{gmain},845
  │   │   │   │   ├─zeitgeist-datah,840
  │   │   │   │   │   ├─{gdbus},870
  │   │   │   │   │   ├─{gmain},866
  │   │   │   │   │   ├─{pool},867
  │   │   │   │   │   └─{pool},891
  │   │   │   │   ├─{dconf worker},693
  │   │   │   │   ├─{gdbus},691
  │   │   │   │   └─{gmain},690
  │   │   │   ├─{gdbus},660
  │   │   │   └─{gmain},655
  │   │   ├─{gdbus},638
  │   │   └─{gmain},637
  │   ├─{gdbus},500
  │   └─{gmain},499
  ├─gnome-keyring-d,651 --daemonize --login
  │   ├─{gdbus},703
  │   ├─{gmain},652
  │   └─{timer},702
  ├─gsd-printer,827
  │   ├─{gdbus},829
  │   └─{gmain},828
  ├─packagekitd,602
  │   ├─{gdbus},608
  │   └─{gmain},607
  ├─polkitd,507 --no-debug
  │   ├─{JS GC Helper},510
  │   ├─{JS Sour~ Thread},511
  │   ├─{gdbus},509
  │   ├─{gmain},508
  │   └─{polkitd},512
  ├─rtkit-daemon,585
  │   ├─{rtkit-daemon},586
  │   └─{rtkit-daemon},587
  ├─systemd,518 --user
  │   ├─(sd-pam),519  
  │   ├─at-spi-bus-laun,573
  │   │   ├─dbus-daemon,578...
  │   │   ├─{dconf worker},574
  │   │   ├─{gdbus},577
  │   │   └─{gmain},575
  │   ├─at-spi2-registr,580 --use-gnome-session
  │   │   ├─{gdbus},582
  │   │   └─{gmain},581
  │   ├─dbus-daemon,532 --session --address=systemd: --nofork --nopidfile...
  │   └─pulseaudio,584 --daemonize=no
  │       ├─{alsa-sink-ALC25},589
  │       ├─{alsa-sink-HDMI },588
  │       └─{alsa-source-ALC},590
  ├─systemd,642 --user
  │   ├─(sd-pam),643  
  │   ├─at-spi-bus-laun,678
  │   │   ├─dbus-daemon,683...
  │   │   ├─{dconf worker},679
  │   │   ├─{gdbus},682
  │   │   └─{gmain},680
  │   ├─at-spi2-registr,686 --use-gnome-session
  │   │   ├─{gdbus},688
  │   │   └─{gmain},687
  │   ├─dbus-daemon,672 --session --address=systemd: --nofork --nopidfile...
  │   ├─evolution-addre,949
  │   │   ├─evolution-addre,970--factor
  │   │   │   ├─{dconf worker},974
  │   │   │   ├─{evolution-addre},975
  │   │   │   ├─{gdbus},973
  │   │   │   └─{gmain},971
  │   │   ├─{dconf worker},956
  │   │   ├─{evolution-addre},957
  │   │   ├─{gdbus},953
  │   │   └─{gmain},952
  │   ├─evolution-calen,907
  │   │   ├─evolution-calen,932 --factoryc
  │   │   │   ├─{dconf worker},933
  │   │   │   ├─{evolution-calen},934
  │   │   │   ├─{evolution-calen},940
  │   │   │   ├─{gdbus},936
  │   │   │   ├─{gmain},935
  │   │   │   └─{pool},939
  │   │   ├─evolution-calen,942 --factoryl
  │   │   │   ├─{dconf worker},943
  │   │   │   ├─{evolution-calen},944
  │   │   │   ├─{gdbus},946
  │   │   │   └─{gmain},945
  │   │   ├─{dconf worker},928
  │   │   ├─{evolution-calen},929
  │   │   ├─{gdbus},927
  │   │   └─{gmain},926
  │   ├─evolution-sourc,762
  │   │   ├─{dconf worker},764
  │   │   ├─{gdbus},766
  │   │   └─{gmain},765
  │   ├─gnome-shell-cal,738
  │   │   ├─{dconf worker},792
  │   │   ├─{gdbus},755
  │   │   ├─{gmain},753
  │   │   ├─{gnome-shell-cal},793
  │   │   └─{gnome-shell-cal},906
  │   ├─gnome-terminal-,996
  │   │   ├─bash,1003
  │   │   │   └─sudo,1060 wpa_cli
  │   │   │       └─wpa_cli,1061
  │   │   ├─bash,1086
  │   │   │   └─pstree,1090 -ap
  │   │   ├─{dconf worker},999
  │   │   ├─{gdbus},998
  │   │   └─{gmain},997
  │   ├─goa-daemon,761
  │   │   ├─{dconf worker},800
  │   │   ├─{gdbus},797
  │   │   ├─{gmain},795
  │   │   └─{goa-daemon},794
  │   ├─goa-identity-se,803
  │   │   ├─{gdbus},807
  │   │   ├─{gmain},805
  │   │   └─{pool},806
  │   ├─gvfs-afc-volume,777
  │   │   ├─{gdbus},781
  │   │   ├─{gmain},779
  │   │   └─{gvfs-afc-volume},778
  │   ├─gvfs-goa-volume,791
  │   │   ├─{gdbus},799
  │   │   └─{gmain},798
  │   ├─gvfs-gphoto2-vo,782
  │   │   ├─{gdbus},785
  │   │   └─{gmain},783
  │   ├─gvfs-mtp-volume,786
  │   │   ├─{gdbus},790
  │   │   └─{gmain},788
  │   ├─gvfs-udisks2-vo,756
  │   │   ├─{gdbus},768
  │   │   └─{gmain},767
  │   ├─gvfsd,708
  │   │   ├─{gdbus},710
  │   │   └─{gmain},709
  │   ├─gvfsd-fuse,713 /run/user/1000/gvfs -f -o big_writes
  │   │   ├─{gdbus},727
  │   │   ├─{gmain},726
  │   │   ├─{gvfs-fuse-sub},728
  │   │   ├─{gvfsd-fuse},724
  │   │   └─{gvfsd-fuse},725
  │   ├─mission-control,746
  │   │   ├─{dconf worker},763
  │   │   ├─{gdbus},759
  │   │   ├─{gmain},757
  │   │   └─{pool},1088
  │   ├─pulseaudio,730 --daemonize=no
  │   │   ├─{alsa-sink-ALC25},732
  │   │   ├─{alsa-sink-HDMI },731
  │   │   └─{alsa-source-ALC},733
  │   ├─tracker-store,836
  │   │   ├─{dconf worker},839
  │   │   ├─{gdbus},842
  │   │   ├─{gmain},841
  │   │   ├─{pool},909
  │   │   ├─{pool},910
  │   │   ├─{pool},911
  │   │   └─{pool},912
  │   ├─wpa_supplicant,1058 -B -i wlp3s0 -c ...
  │   ├─zeitgeist-daemo,872
  │   │   ├─{gdbus},874
  │   │   └─{gmain},873
  │   └─zeitgeist-fts,884
  │       ├─{gdbus},888
  │       └─{gmain},887
  ├─systemd-journal,136
  ├─systemd-logind,439
  ├─systemd-udevd,169
  ├─udisksd,769 --no-debug
  │   ├─{cleanup},775
  │   ├─{gdbus},772
  │   ├─{gmain},770
  │   └─{probing-thread},773
  ├─upowerd,542
  │   ├─{gdbus},544
  │   └─{gmain},543
  └─wpa_supplicant,440 -u

And about the TKIP issue, would it help if I changed it to AES? But even if the router uses no security I can't get internet or router access, although 

iw dev wlp3s0 link

returns that I'm connected. The only way I have succesfully connected my laptop with my home network is by using the preinstalled version of Windows, which I don't wanna return to.

Offline

#22 2016-09-22 23:59:12

onslow77
Member
Registered: 2014-09-21
Posts: 279

Re: Can't connect to specific wi-fi network

Hello!

I have never used TKIP myself, but found an example for the "wpa_supplicant" configuration here!

It looks like this:

# WPA-PSK/TKIP

ctrl_interface=/var/run/wpa_supplicant

network={
	ssid="example wpa-psk network"
	key_mgmt=WPA-PSK
	proto=WPA
	pairwise=TKIP
	group=TKIP
	psk="secret passphrase"
}

Regards
Martin

Last edited by onslow77 (2016-09-23 00:02:53)

It is advised to follow the How to post guide when posting on the Arch forum. If one consciously jumps over these elementary steps like reading the wiki and providing necessary information about the problem, one can be regarded as a Help Vampire.

Offline

#23 2016-09-23 00:15:46

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,532
Website

Re: Can't connect to specific wi-fi network

Huh, my first suspicion was right.  You have multiple wpa_supplicant processes running (plus other network manager processes).  This *will* cause an error like the one you are seeing.

Martin's config from above may be useful, but first lets get rid of the problem that will definitely prevent you from connecting.

Disable *all* other networking processes, kill all wpa_supplicant process, and do the above wpa_cli steps again.  I can't even read through all that pstree to figure out what is what but there are definitely conflicting processes there.

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#24 2016-09-23 00:16:33

ArchEdu
Member
Registered: 2016-09-22
Posts: 19

Re: Can't connect to specific wi-fi network

Thanks again for your effort Martin, unfortunately even after using your suggestion as my config file I proceed to get the same password error loop.

EDIT: About to kill other wpa_supplicant processes and attempt to reconnect using Martin's suggestion.
I attempted to kill NetworkManager and wpa_supplicsnt processes but they get restarted.

Last edited by ArchEdu (2016-09-23 00:24:36)

Offline

#25 2016-09-23 00:26:03

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,532
Website

Re: Can't connect to specific wi-fi network

Then stop the services that are spawning them.

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

Pages: 1 2

Board footer

Powered by FluxBB