[SOLVED] Can't connect to wifi using a dongle

Getting your soundcard to work, using Debian on non-i386 hardware, etc

[SOLVED] Can't connect to wifi using a dongle

Postby ohad » 2020-04-13 19:25

I have debian installed on a fit-pc:
Code: Select all
ohad@fit-pc:~$ uname -a
Linux fit-pc 4.19.0-8-686 #1 SMP Debian 4.19.98-1 (2020-01-26) i586 GNU/Linux

and I'm trying to connect to my home wifi network using an external USB adapter:
Code: Select all
ohad@fit-pc:~$ lsusb
Bus 001 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter


I googled for the necessary drivers, and ended up installing the packages firmware-misc-nonfree, firmware-realtek and firmware-iwlwifi. I'm not sure they are all necessary, but now the adapter is successfully identified as a network interface:
Code: Select all
ohad@fit-pc:~$ ip a
[...]
4: wlx48022a322063: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 48:02:2a:32:20:63 brd ff:ff:ff:ff:ff:ff

and as a wifi device:
Code: Select all
ohad@fit-pc:~$ sudo iw dev
phy#0
   Interface wlx48022a322063
      ifindex 4
      wdev 0x1
      addr 48:02:2a:32:20:63
      type managed
      txpower 20.00 dBm


I then entered the network credentials:
Code: Select all
ohad@fit-pc:~$ sudo cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto enp0s13
iface enp0s13 inet dhcp

allow-hotplug wlx48022a322063
iface wlx48022a322063 inet dhcp
wpa-ssid "<NETWORK-NAME>"
wpa-psk "<PASSWORD>"

and tried to start the interface with
Code: Select all
sudo ifup wlx48022a322063

but didn't get an IP address.

After double-checking the credentials and rebooting (for a clean startup process, in case some of the commands I've used along the way messed up the system state) I still don't get an address. I verified that the dongle does see the network:
Code: Select all
ohad@fit-pc:~$ sudo iw dev wlx48022a322063 scan | grep SSID
   SSID: <NETWORK-NAME>

and it works properly on another computer (a Windows workstation), so there doesn't seem to be a hardware problem. I somehow got a systemctl unit that tries to bring the interface up at startup, and its status shows the failed attempts at DHCP discovery:
Code: Select all
ohad@fit-pc:~$ sudo systemctl status ifup@wlx48022a322063.service
* ifup@wlx48022a322063.service - ifup for wlx48022a322063
   Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: enabled)
   Active: active (exited) since Mon 2020-04-13 22:37:50 IDT; 26min ago
  Process: 399 ExecStart=/bin/sh -ec ifup --allow=hotplug wlx48022a322063; ifquery --state wlx48022a322063 (code=exited, status=0/SUCCESS)
 Main PID: 399 (code=exited, status=0/SUCCESS)
    Tasks: 1 (limit: 455)
   Memory: 3.0M
   CGroup: /system.slice/ifup@wlx48022a322063.service
           `-416 /sbin/dhclient -4 -v -i -pf /run/dhclient.wlx48022a322063.pid -lf /var/lib/dhcp/dhclient.wlx48022a322063.leases -I -df /var/lib/dhcp/dhclient6.wlx48022a322063.leases wlx4802

Apr 13 22:55:24 fit-pc dhclient[416]: No DHCPOFFERS received.
Apr 13 22:55:24 fit-pc dhclient[416]: No working leases in persistent database - sleeping.
Apr 13 23:01:23 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 3
Apr 13 23:01:26 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 8
Apr 13 23:01:34 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 15
Apr 13 23:01:49 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 14
Apr 13 23:02:03 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 19
Apr 13 23:02:22 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 2
Apr 13 23:02:24 fit-pc dhclient[416]: No DHCPOFFERS received.
Apr 13 23:02:24 fit-pc dhclient[416]: No working leases in persistent database - sleeping.

and the system journal only gives a little more information:
Code: Select all
ohad@fit-pc:~$ sudo journalctl -b 0 | grep wlx
Apr 13 22:37:47 fit-pc kernel: rt2800usb 1-1:1.0 wlx48022a322063: renamed from wlan0
Apr 13 22:37:50 fit-pc systemd[1]: Started ifup for wlx48022a322063.
Apr 13 22:37:52 fit-pc kernel: IPv6: ADDRCONF(NETDEV_UP): wlx48022a322063: link is not ready
Apr 13 22:37:52 fit-pc dhclient[416]: Listening on LPF/wlx48022a322063/48:02:2a:32:20:63
Apr 13 22:37:52 fit-pc sh[399]: Listening on LPF/wlx48022a322063/48:02:2a:32:20:63
Apr 13 22:37:52 fit-pc dhclient[416]: Sending on   LPF/wlx48022a322063/48:02:2a:32:20:63
Apr 13 22:37:52 fit-pc sh[399]: Sending on   LPF/wlx48022a322063/48:02:2a:32:20:63
Apr 13 22:37:52 fit-pc sh[399]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 5
Apr 13 22:37:52 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 5
Apr 13 22:37:57 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 14
Apr 13 22:37:57 fit-pc sh[399]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 14
Apr 13 22:38:11 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 8
Apr 13 22:38:11 fit-pc sh[399]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 8
Apr 13 22:38:19 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 11
Apr 13 22:38:19 fit-pc sh[399]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 11
Apr 13 22:38:30 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 15
Apr 13 22:38:30 fit-pc sh[399]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 15
Apr 13 22:38:46 fit-pc dhclient[416]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 7
Apr 13 22:38:46 fit-pc sh[399]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 7
Apr 13 22:38:53 fit-pc sh[399]: wlx48022a322063=wlx48022a322063

but that third line
Code: Select all
Apr 13 22:37:52 fit-pc kernel: IPv6: ADDRCONF(NETDEV_UP): wlx48022a322063: link is not ready

seems to be out of place. It also reappears every time I try to ifup the interface again.

At this point I'm stuck. Any help would be appreciated.
Last edited by ohad on 2020-04-14 17:16, edited 1 time in total.
ohad
 
Posts: 13
Joined: 2020-04-12 18:03

Re: Can't connect to wifi using a dongle

Postby shep » 2020-04-13 20:12

Maybe try disabling IPV6? It is kinda overkill for an LAN anyway.
shep
 
Posts: 399
Joined: 2011-03-15 15:22

Re: Can't connect to wifi using a dongle

Postby ohad » 2020-04-14 05:48

Disabling IPv6 does eliminate the "link is not ready" message, but has no effect on DHCP discovery at all...
ohad
 
Posts: 13
Joined: 2020-04-12 18:03

Re: Can't connect to wifi using a dongle

Postby Head_on_a_Stick » 2020-04-14 11:49

ohad wrote:
Code: Select all
allow-hotplug wlx48022a322063
iface wlx48022a322063 inet dhcp
wpa-ssid "<NETWORK-NAME>"
wpa-psk "<PASSWORD>"

Remove the quotation marks.

If it still doesn't work search the journal for entries from networking.service, that is responsible for handling ifupdown.
Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 12622
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Can't connect to wifi using a dongle

Postby ohad » 2020-04-14 14:43

I removed the quotations. Still no change. Here is the journal for networking.service:
Code: Select all
ohad@fit-pc:~$ sudo journalctl -b -u networking.service
Apr 14 18:18:26 fit-pc systemd[1]: Starting Raise network interfaces...
Apr 14 18:18:29 fit-pc dhclient[411]: Internet Systems Consortium DHCP Client 4.4.1
Apr 14 18:18:29 fit-pc dhclient[411]: Copyright 2004-2018 Internet Systems Consortium.
Apr 14 18:18:29 fit-pc ifup[379]: Internet Systems Consortium DHCP Client 4.4.1
Apr 14 18:18:29 fit-pc ifup[379]: Copyright 2004-2018 Internet Systems Consortium.
Apr 14 18:18:29 fit-pc ifup[379]: All rights reserved.
Apr 14 18:18:29 fit-pc ifup[379]: For info, please visit https://www.isc.org/software/dhcp/
Apr 14 18:18:29 fit-pc dhclient[411]: All rights reserved.
Apr 14 18:18:29 fit-pc dhclient[411]: For info, please visit https://www.isc.org/software/dhcp/
Apr 14 18:18:29 fit-pc dhclient[411]:
Apr 14 18:18:30 fit-pc dhclient[411]: Listening on LPF/enp0s13/00:01:c0:04:05:19
Apr 14 18:18:30 fit-pc ifup[379]: Listening on LPF/enp0s13/00:01:c0:04:05:19
Apr 14 18:18:30 fit-pc ifup[379]: Sending on   LPF/enp0s13/00:01:c0:04:05:19
Apr 14 18:18:30 fit-pc ifup[379]: Sending on   Socket/fallback
Apr 14 18:18:30 fit-pc ifup[379]: DHCPDISCOVER on enp0s13 to 255.255.255.255 port 67 interval 5
Apr 14 18:18:30 fit-pc dhclient[411]: Sending on   LPF/enp0s13/00:01:c0:04:05:19
Apr 14 18:18:30 fit-pc dhclient[411]: Sending on   Socket/fallback
Apr 14 18:18:30 fit-pc dhclient[411]: DHCPDISCOVER on enp0s13 to 255.255.255.255 port 67 interval 5
Apr 14 18:18:31 fit-pc dhclient[411]: DHCPOFFER of 10.100.102.29 from 10.100.102.1
Apr 14 18:18:31 fit-pc ifup[379]: DHCPOFFER of 10.100.102.29 from 10.100.102.1
Apr 14 18:18:31 fit-pc ifup[379]: DHCPREQUEST for 10.100.102.29 on enp0s13 to 255.255.255.255 port 67
Apr 14 18:18:31 fit-pc dhclient[411]: DHCPREQUEST for 10.100.102.29 on enp0s13 to 255.255.255.255 port 67
Apr 14 18:18:31 fit-pc ifup[379]: DHCPACK of 10.100.102.29 from 10.100.102.1
Apr 14 18:18:31 fit-pc dhclient[411]: DHCPACK of 10.100.102.29 from 10.100.102.1
Apr 14 18:18:32 fit-pc dhclient[411]: bound to 10.100.102.29 -- renewal in 1761 seconds.
Apr 14 18:18:32 fit-pc ifup[379]: bound to 10.100.102.29 -- renewal in 1761 seconds.
Apr 14 18:18:34 fit-pc dhclient[471]: Internet Systems Consortium DHCP Client 4.4.1
Apr 14 18:18:34 fit-pc ifup[379]: Internet Systems Consortium DHCP Client 4.4.1
Apr 14 18:18:34 fit-pc ifup[379]: Copyright 2004-2018 Internet Systems Consortium.
Apr 14 18:18:34 fit-pc ifup[379]: All rights reserved.
Apr 14 18:18:34 fit-pc ifup[379]: For info, please visit https://www.isc.org/software/dhcp/
Apr 14 18:18:34 fit-pc dhclient[471]: Copyright 2004-2018 Internet Systems Consortium.
Apr 14 18:18:34 fit-pc dhclient[471]: All rights reserved.
Apr 14 18:18:34 fit-pc dhclient[471]: For info, please visit https://www.isc.org/software/dhcp/
Apr 14 18:18:34 fit-pc dhclient[471]:
Apr 14 18:18:34 fit-pc dhclient[471]: Listening on LPF/wlx48022a322063/48:02:2a:32:20:63
Apr 14 18:18:34 fit-pc ifup[379]: Listening on LPF/wlx48022a322063/48:02:2a:32:20:63
Apr 14 18:18:34 fit-pc dhclient[471]: Sending on   LPF/wlx48022a322063/48:02:2a:32:20:63
Apr 14 18:18:34 fit-pc ifup[379]: Sending on   LPF/wlx48022a322063/48:02:2a:32:20:63
Apr 14 18:18:34 fit-pc ifup[379]: Sending on   Socket/fallback
Apr 14 18:18:34 fit-pc ifup[379]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 3
Apr 14 18:18:34 fit-pc dhclient[471]: Sending on   Socket/fallback
Apr 14 18:18:34 fit-pc dhclient[471]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 3
Apr 14 18:18:37 fit-pc dhclient[471]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 6
Apr 14 18:18:37 fit-pc ifup[379]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 6
Apr 14 18:18:43 fit-pc dhclient[471]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 7
Apr 14 18:18:43 fit-pc ifup[379]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 7
Apr 14 18:18:50 fit-pc dhclient[471]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 11
Apr 14 18:18:50 fit-pc ifup[379]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 11
Apr 14 18:19:01 fit-pc dhclient[471]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 11
Apr 14 18:19:01 fit-pc ifup[379]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 11
Apr 14 18:19:12 fit-pc dhclient[471]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 12
Apr 14 18:19:12 fit-pc ifup[379]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 12
Apr 14 18:19:24 fit-pc dhclient[471]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 8
Apr 14 18:19:24 fit-pc ifup[379]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 8
Apr 14 18:19:32 fit-pc dhclient[471]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 3
Apr 14 18:19:32 fit-pc ifup[379]: DHCPDISCOVER on wlx48022a322063 to 255.255.255.255 port 67 interval 3
Apr 14 18:19:35 fit-pc dhclient[471]: No DHCPOFFERS received.
Apr 14 18:19:35 fit-pc ifup[379]: No DHCPOFFERS received.
Apr 14 18:19:35 fit-pc ifup[379]: No working leases in persistent database - sleeping.
Apr 14 18:19:35 fit-pc dhclient[471]: No working leases in persistent database - sleeping.
Apr 14 18:19:35 fit-pc systemd[1]: Started Raise network interfaces.
ohad
 
Posts: 13
Joined: 2020-04-12 18:03

Re: Can't connect to wifi using a dongle

Postby Head_on_a_Stick » 2020-04-14 14:48

Do you have the wpasupplicant package installed?
Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 12622
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Can't connect to wifi using a dongle

Postby ohad » 2020-04-14 16:02

I didn't. I've now installed it and reconfigured
Code: Select all
ohad@fit-pc:~$ sudo cat /etc/network/interfaces
[...]
auto wlx48022a322063
iface wlx48022a322063 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf

and
Code: Select all
ohad@fit-pc:~$ sudo sh -c "wpa_passphrase <NETWORK-NAME> <PASSWORD> > /etc/wpa_supplicant/wpa_supplicant.conf"
ohad@fit-pc:~$ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf
network={
   ssid="<NETWORK-NAME>"
   #psk="<PASSWORD>"
   psk=<LONG_HEX_KEY>
}


The journal entry:
Code: Select all
ohad@fit-pc:~$ sudo journalctl -b -u networking.service
Apr 14 19:32:54 fit-pc systemd[1]: Starting Raise network interfaces...
Apr 14 19:32:57 fit-pc dhclient[427]: Internet Systems Consortium DHCP Client 4.4.1
Apr 14 19:32:57 fit-pc dhclient[427]: Copyright 2004-2018 Internet Systems Consortium.
Apr 14 19:32:57 fit-pc ifup[394]: Internet Systems Consortium DHCP Client 4.4.1
Apr 14 19:32:57 fit-pc ifup[394]: Copyright 2004-2018 Internet Systems Consortium.
Apr 14 19:32:57 fit-pc ifup[394]: All rights reserved.
Apr 14 19:32:57 fit-pc ifup[394]: For info, please visit https://www.isc.org/software/dhcp/
Apr 14 19:32:57 fit-pc dhclient[427]: All rights reserved.
Apr 14 19:32:57 fit-pc dhclient[427]: For info, please visit https://www.isc.org/software/dhcp/
Apr 14 19:32:57 fit-pc dhclient[427]:
Apr 14 19:32:58 fit-pc dhclient[427]: Listening on LPF/enp0s13/00:01:c0:04:05:19
Apr 14 19:32:58 fit-pc ifup[394]: Listening on LPF/enp0s13/00:01:c0:04:05:19
Apr 14 19:32:58 fit-pc ifup[394]: Sending on   LPF/enp0s13/00:01:c0:04:05:19
Apr 14 19:32:58 fit-pc ifup[394]: Sending on   Socket/fallback
Apr 14 19:32:58 fit-pc ifup[394]: DHCPDISCOVER on enp0s13 to 255.255.255.255 port 67 interval 4
Apr 14 19:32:58 fit-pc dhclient[427]: Sending on   LPF/enp0s13/00:01:c0:04:05:19
Apr 14 19:32:58 fit-pc dhclient[427]: Sending on   Socket/fallback
Apr 14 19:32:58 fit-pc dhclient[427]: DHCPDISCOVER on enp0s13 to 255.255.255.255 port 67 interval 4
Apr 14 19:32:59 fit-pc dhclient[427]: DHCPOFFER of 10.100.102.29 from 10.100.102.1
Apr 14 19:32:59 fit-pc ifup[394]: DHCPOFFER of 10.100.102.29 from 10.100.102.1
Apr 14 19:32:59 fit-pc ifup[394]: DHCPREQUEST for 10.100.102.29 on enp0s13 to 255.255.255.255 port 67
Apr 14 19:32:59 fit-pc dhclient[427]: DHCPREQUEST for 10.100.102.29 on enp0s13 to 255.255.255.255 port 67
Apr 14 19:32:59 fit-pc ifup[394]: DHCPACK of 10.100.102.29 from 10.100.102.1
Apr 14 19:32:59 fit-pc dhclient[427]: DHCPACK of 10.100.102.29 from 10.100.102.1
Apr 14 19:32:59 fit-pc dhclient[427]: bound to 10.100.102.29 -- renewal in 1632 seconds.
Apr 14 19:32:59 fit-pc ifup[394]: bound to 10.100.102.29 -- renewal in 1632 seconds.
Apr 14 19:33:01 fit-pc wpa_supplicant[486]: Successfully initialized wpa_supplicant
Apr 14 19:33:03 fit-pc systemd[1]: Started Raise network interfaces.
Apr 14 19:33:05 fit-pc wpa_supplicant[487]: wlx48022a322063: SME: Trying to authenticate with 8c:59:c3:b4:f5:18 (SSID='<NETWORK-NAME>' freq=2412 MHz)
Apr 14 19:33:05 fit-pc wpa_supplicant[487]: wlx48022a322063: Trying to associate with 8c:59:c3:b4:f5:18 (SSID='<NETWORK-NAME>' freq=2412 MHz)
Apr 14 19:33:05 fit-pc wpa_supplicant[487]: wlx48022a322063: Associated with 8c:59:c3:b4:f5:18
Apr 14 19:33:05 fit-pc wpa_supplicant[487]: wlx48022a322063: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 14 19:33:06 fit-pc wpa_supplicant[487]: wlx48022a322063: WPA: Key negotiation completed with 8c:59:c3:b4:f5:18 [PTK=CCMP GTK=CCMP]
Apr 14 19:33:06 fit-pc wpa_supplicant[487]: wlx48022a322063: CTRL-EVENT-CONNECTED - Connection to 8c:59:c3:b4:f5:18 completed [id=0 id_str=]
Apr 14 19:33:06 fit-pc wpa_action[630]: WPA_IFACE=wlx48022a322063 WPA_ACTION=CONNECTED
Apr 14 19:33:06 fit-pc wpa_action[641]: WPA_ID=0 WPA_ID_STR= WPA_CTRL_DIR=/run/wpa_supplicant
Apr 14 19:33:06 fit-pc wpa_action[674]: network settings not defined for default in /etc/network/interfaces and included files.
Apr 14 19:33:06 fit-pc wpa_action[678]: ifup wlx48022a322063=default
Apr 14 19:33:06 fit-pc wpa_action[723]: creating sendsigs omission pidfile: /run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlx48022a322063.pid
Apr 14 19:33:07 fit-pc wpa_action[732]: bssid=8c:59:c3:b4:f5:18
Apr 14 19:33:07 fit-pc wpa_action[732]: freq=2412
Apr 14 19:33:07 fit-pc wpa_action[732]: ssid=<NETWORK-NAME>
Apr 14 19:33:07 fit-pc wpa_action[732]: id=0
Apr 14 19:33:07 fit-pc wpa_action[732]: mode=station
Apr 14 19:33:07 fit-pc wpa_action[732]: pairwise_cipher=CCMP
Apr 14 19:33:07 fit-pc wpa_action[732]: group_cipher=CCMP
Apr 14 19:33:07 fit-pc wpa_action[732]: key_mgmt=WPA2-PSK
Apr 14 19:33:07 fit-pc wpa_action[732]: wpa_state=COMPLETED
Apr 14 19:33:07 fit-pc wpa_action[732]: address=48:02:2a:32:20:63
Apr 14 19:33:07 fit-pc wpa_action[732]: uuid=cec6ce91-5e17-50e4-8d74-2e29b2ad5657
Apr 14 19:33:07 fit-pc wpa_supplicant[487]: wlx48022a322063: SME: Trying to authenticate with 8c:59:c3:b4:f5:18 (SSID='<NETWORK-NAME>' freq=2412 MHz)
Apr 14 19:33:07 fit-pc wpa_supplicant[487]: wlx48022a322063: Trying to associate with 8c:59:c3:b4:f5:18 (SSID='<NETWORK-NAME>' freq=2412 MHz)
Apr 14 19:33:07 fit-pc wpa_supplicant[487]: wlx48022a322063: Associated with 8c:59:c3:b4:f5:18
Apr 14 19:33:07 fit-pc wpa_supplicant[487]: wlx48022a322063: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 14 19:33:07 fit-pc wpa_supplicant[487]: wlx48022a322063: WPA: Key negotiation completed with 8c:59:c3:b4:f5:18 [PTK=CCMP GTK=CCMP]
Apr 14 19:33:07 fit-pc wpa_supplicant[487]: wlx48022a322063: CTRL-EVENT-CONNECTED - Connection to 8c:59:c3:b4:f5:18 completed [id=0 id_str=]
Apr 14 19:33:07 fit-pc wpa_supplicant[487]: wlx48022a322063: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

I'm not sure why there were two attempts to connect, but at least it seems like some sort of connection was established. Still no address though:
Code: Select all
ohad@fit-pc:~$ ip a
[...]
4: wlx48022a322063: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 48:02:2a:32:20:63 brd ff:ff:ff:ff:ff:ff

which makes sense, I guess, because I changed the definition in /etc/network/interfaces from dhcp to manual for wpa_supplicant, so I need to figure out how to set up DHCP under the new settings.
ohad
 
Posts: 13
Joined: 2020-04-12 18:03

Re: Can't connect to wifi using a dongle

Postby Head_on_a_Stick » 2020-04-14 16:10

ohad wrote:I didn't. I've now installed it and reconfigured
Code: Select all
ohad@fit-pc:~$ sudo cat /etc/network/interfaces
[...]
auto wlx48022a322063
iface wlx48022a322063 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf

Why have you done that? :?

Your previous configuration was fine, it should have worked once wpasupplicant was installed.
Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 12622
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Can't connect to wifi using a dongle

Postby arzgi » 2020-04-14 16:13

After link is up, as root or with sudo
Code: Select all
dhclient
arzgi
 
Posts: 654
Joined: 2008-02-21 17:03
Location: Finland

Re: Can't connect to wifi using a dongle

Postby ohad » 2020-04-14 16:13

Sorry, I was following the first documentation for wpa_supplicant I've found, which was Arch's. I'm now reverting and trying again.
ohad
 
Posts: 13
Joined: 2020-04-12 18:03

Re: Can't connect to wifi using a dongle

Postby ohad » 2020-04-14 16:34

The connection works now. Thanks
ohad
 
Posts: 13
Joined: 2020-04-12 18:03

Re: Can't connect to wifi using a dongle

Postby arzgi » 2020-04-14 16:49

Great! Could you please edit the header of your first post in the thread, and add [SOLVED] to the front of it.
arzgi
 
Posts: 654
Joined: 2008-02-21 17:03
Location: Finland


Return to Hardware

Who is online

Users browsing this forum: No registered users and 14 guests

fashionable