home | list info | list archive | date index | thread index

Wifi issue with TP-Link TL-WN881ND

Ubuntu 18.04 with latest updates
Linux HOSTNAME 5.3.0-45-generic #37~18.04.1-Ubuntu SMP Fri Mar 27
15:58:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Very strange issue here.  Ubuntu recognised the card no issue and
everything appeared to be functioning but I just couldn't connect to
my wifi.  After a fair bit of frustration I decided to try to connect
to the Bell WiFi directly on the Home Hub 3000 I have for Fibe - BAM
it works fine.  Well, other than the fact that that thing is in the
basement and I'm on the 2nd floor so I only get about 5Mbit up and
down through it.

I have the HH3000 in bridge mode and I have an Ubiquiti USG and a
couple of Unifi-AC-PRO access points, along with the Unifi controller.
This setup has been working great for years now and I've connected a
wide range of clients to it without issues.  rPis, various IoT devices
from multiple vendors like smart switches and so forth, Windows,
Linux. Mac you name it.  Never a single issue.  But dammit if I can
figure out why this card won't connect.  I've tried various SSIDs that
I have enabled including both 2.4/5G mixed SSIDs, and 2.4 and 5G
segregated.

Here are the log entries from when it works against the HH3000 and
below that logs from when it doesn't work against my Ubiquiti setup

I've been doing a fair bit of googling and running some nmcli debug
commands and have not been able to find anything yet as to what is up
here

From within my Ubiquiti GUI logs I cannot find an instance of the MAC
address of my TP-Link card.  Which seems to indicate a pretty low
level issue.

Working :

Apr  2 14:39:40 HOSTNAME NetworkManager[867]: <info>
[1585852780.9213] device (wlp6s0): state change: need-auth -> prepare
(reason 'none', sys-iface-state: 'managed')
Apr  2 14:39:40 HOSTNAME NetworkManager[867]: <info>
[1585852780.9261] device (wlp6s0): state change: prepare -> config
(reason 'none', sys-iface-state: 'managed')
Apr  2 14:39:40 HOSTNAME NetworkManager[867]: <info>
[1585852780.9263] device (wlp6s0): Activation: (wifi) connection
'BellHomeHub3000SSID' has security, and secrets exist.  No new secrets
needed.
Apr  2 14:39:40 HOSTNAME wpa_supplicant[865]: wlp6s0: SME: Trying to
authenticate with 40:c7:29:fb:96:e6 (SSID='BellHomeHub3000SSID'
freq=2437 MHz)
Apr  2 14:39:40 HOSTNAME kernel: [  749.827087] wlp6s0: authenticate
with 40:c7:29:fb:96:e6
Apr  2 14:39:40 HOSTNAME NetworkManager[867]: <info>
[1585852780.9649] device (wlp6s0): supplicant interface state:
scanning -> authenticating
Apr  2 14:39:40 HOSTNAME kernel: [  749.843354] wlp6s0: send auth to
40:c7:29:fb:96:e6 (try 1/3)
Apr  2 14:39:41 HOSTNAME wpa_supplicant[865]: wlp6s0: Trying to
associate with 40:c7:29:fb:96:e6 (SSID='BellHomeHub3000SSID' freq=2437
MHz)
Apr  2 14:39:41 HOSTNAME kernel: [  749.928002] wlp6s0: authenticated
Apr  2 14:39:41 HOSTNAME kernel: [  749.928736] wlp6s0: associate with
40:c7:29:fb:96:e6 (try 1/3)
Apr  2 14:39:41 HOSTNAME NetworkManager[867]: <info>
[1585852781.0543] device (wlp6s0): supplicant interface state:
authenticating -> associating
Apr  2 14:39:41 HOSTNAME kernel: [  749.997663] wlp6s0: RX AssocResp
from 40:c7:29:fb:96:e6 (capab=0x411 status=0 aid=2)
Apr  2 14:39:41 HOSTNAME wpa_supplicant[865]: wlp6s0: Associated with
40:c7:29:fb:96:e6
Apr  2 14:39:41 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr  2 14:39:41 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA
Apr  2 14:39:41 HOSTNAME kernel: [  750.003075] wlp6s0: associated
Apr  2 14:39:41 HOSTNAME NetworkManager[867]: <info>
[1585852781.1294] device (wlp6s0): supplicant interface state:
associating -> associated
Apr  2 14:39:42 HOSTNAME NetworkManager[867]: <info>
[1585852782.0961] device (wlp6s0): supplicant interface state:
associated -> 4-way handshake
Apr  2 14:39:42 HOSTNAME wpa_supplicant[865]: wlp6s0: WPA: Key
negotiation completed with 40:c7:29:fb:96:e6 [PTK=CCMP GTK=CCMP]
Apr  2 14:39:42 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-CONNECTED - Connection to 40:c7:29:fb:96:e6 completed [id=0
id_str=]
Apr  2 14:39:42 HOSTNAME kernel: [  751.150483] IPv6:
ADDRCONF(NETDEV_CHANGE): wlp6s0: link becomes ready
Apr  2 14:39:42 HOSTNAME NetworkManager[867]: <info>
[1585852782.2765] device (wlp6s0): supplicant interface state: 4-way
handshake -> completed
Apr  2 14:39:42 HOSTNAME NetworkManager[867]: <info>
[1585852782.2766] device (wlp6s0): Activation: (wifi) Stage 2 of 5
(Device Configure) successful.  Connected to wireless network
'BellHomeHub3000SSID'.
Apr  2 14:39:42 HOSTNAME NetworkManager[867]: <info>
[1585852782.2767] device (wlp6s0): state change: config -> ip-config
(reason 'none', sys-iface-state: 'managed')
Apr  2 14:39:42 HOSTNAME NetworkManager[867]: <info>
[1585852782.2770] dhcp4 (wlp6s0): activation: beginning transaction
(timeout in 45 seconds)
Apr  2 14:39:42 HOSTNAME NetworkManager[867]: <info>
[1585852782.2880] dhcp4 (wlp6s0): dhclient started with pid 2669
Apr  2 14:39:42 HOSTNAME avahi-daemon[860]: Joining mDNS multicast
group on interface wlp6s0.IPv6 with address fe80::a000:70a4:325e:8cc.
Apr  2 14:39:42 HOSTNAME avahi-daemon[860]: New relevant interface
wlp6s0.IPv6 for mDNS.
Apr  2 14:39:42 HOSTNAME avahi-daemon[860]: Registering new address
record for fe80::a000:70a4:325e:8cc on wlp6s0.*.
Apr  2 14:39:42 HOSTNAME dhclient[2669]: DHCPDISCOVER on wlp6s0 to
255.255.255.255 port 67 interval 3 (xid=0xa659ae7f)
Apr  2 14:39:45 HOSTNAME dhclient[2669]: DHCPDISCOVER on wlp6s0 to
255.255.255.255 port 67 interval 8 (xid=0xa659ae7f)
Apr  2 14:39:46 HOSTNAME dhclient[2669]: DHCPREQUEST of 192.168.2.14
on wlp6s0 to 255.255.255.255 port 67 (xid=0x7fae59a6)
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2484] dhcp4 (wlp6s0):   address 192.168.2.14
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2484] dhcp4 (wlp6s0):   plen 24 (255.255.255.0)
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2484] dhcp4 (wlp6s0):   gateway 192.168.2.1
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2484] dhcp4 (wlp6s0):   lease time 259200
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2485] dhcp4 (wlp6s0):   nameserver '192.168.2.1'
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2485] dhcp4 (wlp6s0):   nameserver '207.164.234.193'
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2485] dhcp4 (wlp6s0):   domain name 'home'
Apr  2 14:39:46 HOSTNAME avahi-daemon[860]: Joining mDNS multicast
group on interface wlp6s0.IPv4 with address 192.168.2.14.
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2485] dhcp4 (wlp6s0): state changed unknown -> bound
Apr  2 14:39:46 HOSTNAME avahi-daemon[860]: New relevant interface
wlp6s0.IPv4 for mDNS.
Apr  2 14:39:46 HOSTNAME avahi-daemon[860]: Registering new address
record for 192.168.2.14 on wlp6s0.IPv4.
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2496] device (wlp6s0): state change: ip-config -> ip-check
(reason 'none', sys-iface-state: 'managed')
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2501] device (wlp6s0): state change: ip-check ->
secondaries (reason 'none', sys-iface-state: 'managed')
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2503] device (wlp6s0): state change: secondaries ->
activated (reason 'none', sys-iface-state: 'managed')
Apr  2 14:39:46 HOSTNAME NetworkManager[867]: <info>
[1585852786.2546] device (wlp6s0): Activation: successful, device
activated.
Apr  2 14:39:46 HOSTNAME nm-dispatcher: req:1 'up' [wlp6s0]: new
request (1 scripts)
Apr  2 14:39:46 HOSTNAME nm-dispatcher: req:1 'up' [wlp6s0]: start
running ordered scripts...


and now not working

Apr  2 15:07:37 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-SSID-REENABLED id=0 ssid="SSIDBroken5G"
Apr  2 15:07:37 HOSTNAME wpa_supplicant[865]: wlp6s0: SME: Trying to
authenticate with f0:9f:c2:a7:b6:57 (SSID='SSIDBroken5G' freq=2462
MHz)
Apr  2 15:07:37 HOSTNAME kernel: [ 2426.262289] wlp6s0: authenticate
with f0:9f:c2:a7:b6:57
Apr  2 15:07:37 HOSTNAME NetworkManager[867]: <info>
[1585854457.4267] device (wlp6s0): supplicant interface state:
scanning -> authenticating
Apr  2 15:07:37 HOSTNAME kernel: [ 2426.293182] wlp6s0: send auth to
f0:9f:c2:a7:b6:57 (try 1/3)
Apr  2 15:07:37 HOSTNAME kernel: [ 2426.314709] wlp6s0:
f0:9f:c2:a7:b6:57 denied authentication (status 37)
Apr  2 15:07:37 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-AUTH-REJECT f0:9f:c2:a7:b6:57 auth_type=0
auth_transaction=2 status_code=37 ie=(null)
Apr  2 15:07:37 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDBroken5G" auth_failures=2
duration=20 reason=CONN_FAILED
Apr  2 15:07:37 HOSTNAME NetworkManager[867]: <info>
[1585854457.4954] device (wlp6s0): supplicant interface state:
authenticating -> disconnected
Apr  2 15:07:47 HOSTNAME NetworkManager[867]: <info>
[1585854467.4975] device (wlp6s0): supplicant interface state:
disconnected -> scanning
Apr  2 15:07:51 HOSTNAME NetworkManager[867]: <warn>
[1585854471.7900] device (wlp6s0): Activation: (wifi) association took
too long, failing activation
Apr  2 15:07:51 HOSTNAME NetworkManager[867]: <info>
[1585854471.7901] device (wlp6s0): state change: config -> failed
(reason 'ssid-not-found', sys-iface-state: 'managed')
Apr  2 15:07:51 HOSTNAME NetworkManager[867]: <warn>
[1585854471.7918] device (wlp6s0): Activation: failed for connection
'SSIDBroken5G 1'
Apr  2 15:07:51 HOSTNAME NetworkManager[867]: <info>
[1585854471.7982] device (wlp6s0): supplicant interface state:
scanning -> disconnected
Apr  2 15:07:51 HOSTNAME NetworkManager[867]: <info>
[1585854471.7985] device (wlp6s0): state change: failed ->
disconnected (reason 'none', sys-iface-state: 'managed')
Apr  2 15:08:52 HOSTNAME systemd[1]: Starting Message of the Day...
Apr  2 15:08:52 HOSTNAME systemd[1]: Started Message of the Day.
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3043] keyfile: add connection in-memory
(c14597de-2168-4523-a78f-d36759d12620,"SSIDBroken5G 3")
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3078] device (wlp6s0): Activation: starting connection
'SSIDBroken5G 3' (c14597de-2168-4523-a78f-d36759d12620)
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3185]
settings-connection[0x55a7dd42eee0,c14597de-2168-4523-a78f-d36759d12620]:
write: successfully commited (keyfile: update
/etc/NetworkManager/system-connections/SSIDBroken5G 3
(c14597de-2168-4523-a78f-d36759d12620,"SSIDBroken5G 3") and persist
connection)
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3187] audit: op="connection-add-activate"
uuid="c14597de-2168-4523-a78f-d36759d12620" name="SSIDBroken5G 3"
pid=6382 uid=0 result="success"
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3305] device (wlp6s0): state change: disconnected ->
prepare (reason 'none', sys-iface-state: 'managed')
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3313] device (wlp6s0): state change: prepare -> config
(reason 'none', sys-iface-state: 'managed')
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3316] device (wlp6s0): Activation: (wifi) access point
'SSIDBroken5G 3' has security, but secrets are required.
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3316] device (wlp6s0): state change: config -> need-auth
(reason 'none', sys-iface-state: 'managed')
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3350] device (wlp6s0): state change: need-auth -> prepare
(reason 'none', sys-iface-state: 'managed')
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3354] device (wlp6s0): state change: prepare -> config
(reason 'none', sys-iface-state: 'managed')
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3356] device (wlp6s0): Activation: (wifi) connection
'SSIDBroken5G 3' has security, and secrets exist.  No new secrets
needed.
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3356] Config: added 'ssid' value 'SSIDBroken5G'
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3356] Config: added 'scan_ssid' value '1'
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3356] Config: added 'bgscan' value 'simple:30:-80:86400'
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3357] Config: added 'key_mgmt' value 'WPA-PSK'
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3357] Config: added 'auth_alg' value 'OPEN'
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3357] Config: added 'psk' value '<hidden>'
Apr  2 15:09:26 HOSTNAME NetworkManager[867]: <info>
[1585854566.3485] device (wlp6s0): supplicant interface state:
disconnected -> scanning
Apr  2 15:09:27 HOSTNAME wpa_supplicant[865]: wlp6s0: SME: Trying to
authenticate with f0:9f:c2:a7:b6:57 (SSID='SSIDBroken5G' freq=2462
MHz)
Apr  2 15:09:27 HOSTNAME kernel: [ 2536.249614] wlp6s0: authenticate
with f0:9f:c2:a7:b6:57
Apr  2 15:09:27 HOSTNAME NetworkManager[867]: <info>
[1585854567.4145] device (wlp6s0): supplicant interface state:
scanning -> authenticating
Apr  2 15:09:27 HOSTNAME kernel: [ 2536.281482] wlp6s0: send auth to
f0:9f:c2:a7:b6:57 (try 1/3)
Apr  2 15:09:27 HOSTNAME kernel: [ 2536.286617] wlp6s0:
f0:9f:c2:a7:b6:57 denied authentication (status 37)
Apr  2 15:09:27 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-AUTH-REJECT f0:9f:c2:a7:b6:57 auth_type=0
auth_transaction=2 status_code=37 ie=(null)
Apr  2 15:09:27 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDBroken5G" auth_failures=1
duration=10 reason=CONN_FAILED
Apr  2 15:09:27 HOSTNAME NetworkManager[867]: <info>
[1585854567.4714] device (wlp6s0): supplicant interface state:
authenticating -> disconnected
Apr  2 15:09:37 HOSTNAME NetworkManager[867]: <info>
[1585854577.4732] device (wlp6s0): supplicant interface state:
disconnected -> scanning
Apr  2 15:09:38 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-SSID-REENABLED id=0 ssid="SSIDBroken5G"
Apr  2 15:09:38 HOSTNAME wpa_supplicant[865]: wlp6s0: SME: Trying to
authenticate with f0:9f:c2:a7:b6:57 (SSID='SSIDBroken5G' freq=2462
MHz)
Apr  2 15:09:38 HOSTNAME kernel: [ 2547.386382] wlp6s0: authenticate
with f0:9f:c2:a7:b6:57
Apr  2 15:09:38 HOSTNAME NetworkManager[867]: <info>
[1585854578.5508] device (wlp6s0): supplicant interface state:
scanning -> authenticating
Apr  2 15:09:38 HOSTNAME kernel: [ 2547.417682] wlp6s0: send auth to
f0:9f:c2:a7:b6:57 (try 1/3)
Apr  2 15:09:38 HOSTNAME kernel: [ 2547.426786] wlp6s0:
f0:9f:c2:a7:b6:57 denied authentication (status 37)
Apr  2 15:09:38 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-AUTH-REJECT f0:9f:c2:a7:b6:57 auth_type=0
auth_transaction=2 status_code=37 ie=(null)
Apr  2 15:09:38 HOSTNAME wpa_supplicant[865]: wlp6s0:
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDBroken5G" auth_failures=2
duration=20 reason=CONN_FAILED
Apr  2 15:09:38 HOSTNAME NetworkManager[867]: <info>
[1585854578.6114] device (wlp6s0): supplicant interface state:
authenticating -> disconnected
Apr  2 15:09:48 HOSTNAME NetworkManager[867]: <info>
[1585854588.6146] device (wlp6s0): supplicant interface state:
disconnected -> scanning
Apr  2 15:09:51 HOSTNAME NetworkManager[867]: <warn>
[1585854591.7899] device (wlp6s0): Activation: (wifi) association took
too long, failing activation
Apr  2 15:09:51 HOSTNAME NetworkManager[867]: <info>
[1585854591.7899] device (wlp6s0): state change: config -> failed
(reason 'ssid-not-found', sys-iface-state: 'managed')
Apr  2 15:09:51 HOSTNAME NetworkManager[867]: <warn>
[1585854591.7911] device (wlp6s0): Activation: failed for connection
'SSIDBroken5G 3'
Apr  2 15:09:51 HOSTNAME NetworkManager[867]: <info>
[1585854591.7976] device (wlp6s0): supplicant interface state:
scanning -> disconnected
Apr  2 15:09:51 HOSTNAME NetworkManager[867]: <info>
[1585854591.7981] device (wlp6s0): state change: failed ->
disconnected (reason 'none', sys-iface-state: 'managed')


-- 
"You should sit in nature for 20 minutes a day.
 Unless you are busy, then you should sit for an hour"
         - Zen Proverb

To unsubscribe send a blank message to linux+unsubscribe [ at ] linux-ottawa [ dot ] org
To get help send a blank message to linux+help [ at ] linux-ottawa [ dot ] org
To visit the archives: https://lists.linux-ottawa.org