[SOLVED] Unable to connect to wifi in tty.

NarcoticNoble · 2019-02-17 17:15:57

Hello,

I've just installed Arch on my X60 laptop, during the install I connect to the internet wirelessly through netctl to my hidden network and all works fine, but as soon as I boot into the system and try to connect with netctl using the same configuration file it fails.

The output of

systemctl status netctl@NobleWireless

nessie systemd[1]: Starting Networking for netctl profile NobleWireless..
nessie network[897]: Starting network profile 'NobleWireless'...
nessie network[897]: WPA association/authentication failed for interface 'wls3'
nessie network[897]: Failed ot bring the network up for profile 'NobleWireless'
nessie systemd[1]: netctl@NobleWireless.service: Main process exited, code=exited, status=1/FAILURE
nessie systemd[1]: netctl@NobleWireless.service: Failed with result 'exit-code'.
nessie systemd[1]: Failed to start Networking for netctl profile NobleWireless.

I tried with network managers nmcli and nmtui and it works fine on the installation media but again it doesn't work on my system - doesn't seem to find NobleWireless as an SSID.

Is the issue that it's a hidden network? But then again why does it work in the installation media?

Using wired isn't really an option.

Thank you.

Last edited by NarcoticNoble (2019-02-17 22:37:22)

Trilby · 2019-02-17 17:22:58

The installation medium includes tools that are not part of a base install, including some wireless drivers. However, to actually get to the bottom of what is happening, please follow the manual connection steps in the wiki and post all output or any errors here in [ code ] tags.

The first would be the output of `lspci -vnn | grep -i net' and `ip a`.

NarcoticNoble · 2019-02-17 17:48:23

lspci -vnn | grep -i net

02:00.0 Ethernet controller [0200]: Intel Corporation 82573L Gigabit Ethernet Controller [8086:109a]
03:00.0 Network controller [0280]: Intel Corporation Pro/Wireless 3945ABG [Golan] Network Connection [8086:4227] (rev 02)

I then followed the Wireless network configuration page:
I ran

lspci -k | less

and manually searched for "Network" to see what drivers had been installed.

03:00.0 Network controller [0280]: Intel Corporation Pro/Wireless 3945ABG [Golan] Network Connection [8086:4227] (rev 02)
             Subsystem: Intel COrporation ThinkPad T60/R60e/X60s/R61
             Kernel driver in use: iwl3945
             Kernel modules: iwl3945

Then checked if it was loaded with

dmesg | grep firmware

iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9

So it seems to have loaded the correct driver but still fails to connect.
So ti seems to have loaded the correct drivers but when I try to connect I get the same error:

systemctl status netctl@NobleWireless

nessie systemd[1]: Starting Networking for netctl profile NobleWireless..
nessie network[897]: Starting network profile 'NobleWireless'...
nessie network[897]: WPA association/authentication failed for interface 'wls3'
nessie network[897]: Failed ot bring the network up for profile 'NobleWireless'
nessie systemd[1]: netctl@NobleWireless.service: Main process exited, code=exited, status=1/FAILURE
nessie systemd[1]: netctl@NobleWireless.service: Failed with result 'exit-code'.
nessie systemd[1]: Failed to start Networking for netctl profile NobleWireless.

Last edited by NarcoticNoble (2019-02-17 19:45:54)

jasonwryan · 2019-02-17 17:50:58

Yes, continue working methodically through that wiki page, "fails to connect" is not a meaningful error message: https://bbs.archlinux.org/viewtopic.php?id=57855

NarcoticNoble · 2019-02-17 19:46:20

After following the guide I found that my wireless card using the iwlegacy driver the kernel module for this is iwl3945 for my wireless card, which is enabled and installed as it the previous output shows and as I have linux-firmware installed.

My only other option is as stated in the page:
"If you have problems connecting to networks in general, random failures with your card on bootup or your link quality is very poor, try to disable 802.11n"
So I added this line in /etc/modprobe.d/iwl3945.conf:

options iwl4965 11n_disable=1

This made no difference either.

It also states and issue with the nouveau driver conflicting but this doesn't apply to me as the ThinkPad X60T doesn't have nvidia graphics.

I thought I was getting somewhere but I honestly don't understand what is wrong, journalctl and systemctl aren't giving very helpful error messages.

Any other pointers?

Last edited by NarcoticNoble (2019-02-17 19:48:00)

Trilby · 2019-02-17 19:54:57

NarcoticNoble wrote:

I honestly don't understand what is wrong, journalctl and systemctl aren't giving very helpful error messages.

Neither do we, as you are not giving helpful error messages or the output requested.

NarcoticNoble wrote:

Any other pointers?

Yes:

Trilby wrote:

... please follow the manual connection steps in the wiki and post all output or any errors here in [ code ] tags.
The first would be the output of `lspci -vnn | grep -i net' and `ip a`.

NarcoticNoble · 2019-02-17 20:06:07

Just tried to create a wifi hotspot with my phone as all the other available connections are either PEAP protected or hidden, using wifi-menu it appears, so my card can scan and pick up APs, so I enter it, enter the wifi password and it fails to connect and asks me to check "systemctl status" and "journalctl -xe".

systemctl status output:

nessie systemd[1]: Starting Networking for netctl profile wls3-Noble
nessie network[897]: Starting network profile 'wls3-Noble'...
nessie network[897]: WPA association/authentication failed for interface 'wls3'
nessie network[897]: Failed ot bring the network up for profile 'wls3-Noble'
nessie systemd[1]: netctl@wls3\\x2dNoble.service: Main process exited, code=exited, status=1/FAILURE
nessie systemd[1]: netctl@wls3\\x2dNoble.service: Failed with result 'exit-code'.
nessie systemd[1]: Failed to start Networking for netctl profile wls3-Noble.

So the exact same error for a different network.

And journalctl output:
https://pastebin.com/L2Ewv3rJ

loqs · 2019-02-17 20:17:22

You have NetworkManager and netctl competing for control of the interface. Disable all network management services.
Continue from Wireless_network_configuration#Get_the_status_of_the_interface until "Connect to an access point" then if you need WPA follow WPA_supplicant#Advanced_usage.

NarcoticNoble · 2019-02-17 20:29:21

Output of 'ip a':

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 00:16:d3:c0:09:4c brd ff:ff:ff:ff:ff:ff
3: wls3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 26:47:5b:db:ad:da brd ff:ff:ff:ff:ff:ff

So as I've tried many network drivers I installed the iwd utility as it supports WPA2, so I followed the iwd command of connecting to a wireless point.

I ran:

# systemctl start iwd.service
# iwctl

The from iwd command prompt:

[iwd]# device list
Name Address Powered Adapter Mode
wls3   ##### on          phy0      station

[iwd]# station wls3 scan
[iwd]# station wls3 get-networks
Network name  Security   Signal
eduroam           8021x       ****
PS4-#####     psk           ****
Noble                 psk           ****

[iwd]# station wls3 connect Noble
Type the network passphrase for Noble psk.
Passphrase: ************

After this I get no output but according to the iwd arch wiki page this should be connected now - but when I run:

ping archlinux.org

I get:

ping: archlinux.org: Temporary failure in name resolution

loqs · 2019-02-17 20:35:45

After you connected to the wireless network did you follow Network_configuration#IP_addresses?

NarcoticNoble · 2019-02-17 21:25:34

Following loqs advice:
I ran:

# systemctl disable netctl
# systemctl disable NetworkManager
# systemctl disable NobleWireless@netctl
# pacman -Rs networkmanager
# pacman -Syu iw wpa_supplicant

Then ran:

# iw dev wls3 link
Not connected.
# iw dev wls3
# ip link set wls3 up
# iw dev wls3 scan

iw dev wls3 scan output:
https://pastebin.com/G3eDbpc7
Then I did:

# wpa_passphrase NobleWireless mypassword > /etc/wpa_supplicant/example.conf

Then added scan_ssid=1 to the network block as it is a hidden network like so:

network={
	ssid="NobleWireless"
	#psk="mypassword"
	psk=a_long_string_of_chars
	scan_ssid=1
}

Then, finally some good errors, when I ran:

wpa_supplicant -i wls3 -c /etc/wpa_supplicant/example.conf

output:
https://pastebin.com/iQRrbypV

loqs · 2019-02-17 21:46:15

wls3: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="NobleWireless" auth_failures=1 duration=10 reason=WRONG_KEY

The SSID PSK pair is being rejected.

NarcoticNoble · 2019-02-17 21:47:54

I commented the psk with a long string of characters and uncommented the one with the plain text password.
This is the new following output of

 # wpa_supplicant -i wls3 -c /etc/wpa_supplicant/example.conf

:

wls3: SME: Trying to authenticate with b8:27:eb:ca:f6:7d (SSID='NobleWireless' freq=2412 MHz)
wls3: Trying to associate with b8:27:eb:ca:f6:7d (SSID='NobleWireless' freq=2412 MHz)
wls3: Associated with b8:27:eb:ca:f6:7d
wls3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wls3: WPA: Key negotiation completed with b8:27:eb:ca:f6:7d [PTK=TKIP GTK=TKIP]
wls3: CTRL-EVET-CONNECTED - Connection to b8:27:eb:ca:f6:7d completed [id=0 id_str=]

Then the command never finished and just hangs there, so I force exit with Ctrl+C and get:

wls3: CTRL-EVENT-DISCONNECTED bssid=b8:27:eb:ca:f6:7d reason=3 locally_generated=1
nl80211: deinit ifname=wls3 disabled_11b_rates=0
wls3: CTRL-EVENT_TERMINATING

NarcoticNoble · 2019-02-17 21:50:55

The password I am using is the right one, and it isn't written down incorrectly as I can see the password in plaintext is exactly what I have typed for all my other devices connected to the same network.

seth · 2019-02-17 21:55:16

Then the command never finished and just hangs there

wpa_supplicant won't fork w/o "-B"

jasonwryan · 2019-02-17 21:56:07

NarcoticNoble wrote:

Then the command never finished and just hangs there, so I force exit with Ctrl+C and get:

This means it is running; use another terminal to obtain an IP address.

NarcoticNoble · 2019-02-17 21:59:41

So I ran with the -B flag and get the output

Successfully initialized wpa_supplicant

Then while following the guide I ran:

# dhcpcd wls3

and I get

wls3: waiting for carrier
timed out
dhcpcd exited

NarcoticNoble · 2019-02-17 22:03:00

Also when I run

wpa_cli

I get

Could not connect to wpa_supplicant: (nil) - re-trying

And that just hangs and doesn't do anything.

seth · 2019-02-17 22:12:50

The carrier is provided by wpa_supplicant, the connection still takes a moment after the process forks.
Check "ip a" before running dhcpcd, ensure wls3 does no longer state "NO-CARRIER".

NarcoticNoble · 2019-02-17 22:31:34

Well that's embarrassing, so I left it for while, checking "ip a" for the "NO-CARRIER" to go, then did "dhcpd wls3" and now I am connected.

So I decided to reboot to see if now I could potentially use netctl, but netctl still fails and I still don't understand why this is. I am able to connect but I just have to run

# wpa_supplicant -i wls3 -c /etc/wpa_supplicant/example.conf
# dhcpcd wls3

every time I boot.

Still no idea why a network manager can't connect to it

jasonwryan · 2019-02-17 22:33:24

If you can connect manually, then the issue is with netctl. That's a separate issue.

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

Trilby · 2019-02-17 22:39:07

NarcoticNoble wrote:

I am able to connect but I just have to run ... every time I boot.

If you want, you can move that example.conf to wpa_supplicant.conf, enable the wpa_supplicant hook for dhcpcd, then `systemctl enable dhcpcd@wls1` and then from then on all of those commands will be run automatically for you at boot.

Other network management tools have always seemed bloated and confusing to me: wpa_supplicant and dhcpcd should be all you ever need, and they are just as easily automated as any other tool (more so if you ask me).

Arch Linux

#1 2019-02-17 17:15:57

[SOLVED] Unable to connect to wifi in tty.

#2 2019-02-17 17:22:58

Re: [SOLVED] Unable to connect to wifi in tty.

#3 2019-02-17 17:48:23

Re: [SOLVED] Unable to connect to wifi in tty.

#4 2019-02-17 17:50:58

Re: [SOLVED] Unable to connect to wifi in tty.

#5 2019-02-17 19:46:20

Re: [SOLVED] Unable to connect to wifi in tty.

#6 2019-02-17 19:54:57

Re: [SOLVED] Unable to connect to wifi in tty.

#7 2019-02-17 20:06:07

Re: [SOLVED] Unable to connect to wifi in tty.

#8 2019-02-17 20:17:22

Re: [SOLVED] Unable to connect to wifi in tty.

#9 2019-02-17 20:29:21

Re: [SOLVED] Unable to connect to wifi in tty.

#10 2019-02-17 20:35:45

Re: [SOLVED] Unable to connect to wifi in tty.

#11 2019-02-17 21:25:34

Re: [SOLVED] Unable to connect to wifi in tty.

#12 2019-02-17 21:46:15

Re: [SOLVED] Unable to connect to wifi in tty.

#13 2019-02-17 21:47:54

Re: [SOLVED] Unable to connect to wifi in tty.

#14 2019-02-17 21:50:55

Re: [SOLVED] Unable to connect to wifi in tty.

#15 2019-02-17 21:55:16

Re: [SOLVED] Unable to connect to wifi in tty.

#16 2019-02-17 21:56:07

Re: [SOLVED] Unable to connect to wifi in tty.

#17 2019-02-17 21:59:41

Re: [SOLVED] Unable to connect to wifi in tty.

#18 2019-02-17 22:03:00

Re: [SOLVED] Unable to connect to wifi in tty.

#19 2019-02-17 22:12:50

Re: [SOLVED] Unable to connect to wifi in tty.

#20 2019-02-17 22:31:34

Re: [SOLVED] Unable to connect to wifi in tty.

#21 2019-02-17 22:33:24

Re: [SOLVED] Unable to connect to wifi in tty.

#22 2019-02-17 22:39:07

Re: [SOLVED] Unable to connect to wifi in tty.

Board footer