Ubuntu 20.04 can't access Deco M4 wifi

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Ubuntu 20.04 can't access Deco M4 wifi
Ubuntu 20.04 can't access Deco M4 wifi
2020-09-25 11:10:20 - last edited 2020-09-25 12:57:49
Model: Deco M4
Hardware Version:
Firmware Version:

Since yesterday, my laptop with Ubuntu 20.04 can't access the regular wifi created by the deco. It tries to connect, asks for the password, drops the connection and starts all over again. This happens every 5 seconds, it's ubelievable.

If I connect to the guest network (without a password) or another wifi by a Netgear router, everything works fine. It seems it's the authentication that suddenly stopped working. Both the laptop and Deco are up to date.

 

The wifi is configured on linux for WPA & WPA2 Personal and automatic IPV6

 

Any help would be greatly appreciated!

0
0
#1
Options
8 Reply
Re:Ubuntu 20.04 can't access Deco M4 wifi
2020-09-25 17:28:36

@FRR149 

 

Is the Deco is getting an IPv4 address, have you tried utilizing IPv4 for the Linux machine?

0
0
#2
Options
Re:Ubuntu 20.04 can't access Deco M4 wifi
2020-09-25 20:40:15
I'm not sure if the Deco is using IPv4 or IPv6. Right now, IPv6 is marked as automatic on Ubuntu. I'll try to deactivate that and force IPv4 only and see what happens.
0
0
#3
Options
Re:Ubuntu 20.04 can't access Deco M4 wifi
2020-09-25 20:51:48

@Tony 

Confirmed. IPV6 was disabled on the deco. I also disabled it on the Linux laptop. Still no luck... :-(

0
0
#4
Options
Re:Ubuntu 20.04 can't access Deco M4 wifi
2020-09-25 20:58:54

@Tony 

BTW, this is the log from sudo journalctl -b 0 /usr/sbin/NetworkManager 
 

sep 25 11:49:52 winston-wolfe NetworkManager[1289]: <info>  [1601027392.4189] device (wlo1): supplicant interface state: associating -> associated
sep 25 11:49:52 winston-wolfe NetworkManager[1289]: <info>  [1601027392.4189] device (p2p-dev-wlo1): supplicant management interface state: associating -> associated
sep 25 11:49:52 winston-wolfe NetworkManager[1289]: <info>  [1601027392.4318] device (wlo1): supplicant interface state: associated -> 4-way handshake
sep 25 11:49:52 winston-wolfe NetworkManager[1289]: <info>  [1601027392.4318] device (p2p-dev-wlo1): supplicant management interface state: associated -> 4-way handshake
sep 25 11:49:56 winston-wolfe NetworkManager[1289]: <warn>  [1601027396.5121] sup-iface[0x563245dc7210,wlo1]: connection disconnected (reason 2)
sep 25 11:49:56 winston-wolfe NetworkManager[1289]: <info>  [1601027396.5172] device (wlo1): supplicant interface state: 4-way handshake -> disconnected
sep 25 11:49:56 winston-wolfe NetworkManager[1289]: <info>  [1601027396.5176] device (wlo1): Activation: (wifi) disconnected during association, asking for new key
sep 25 11:49:56 winston-wolfe NetworkManager[1289]: <info>  [1601027396.5177] device (wlo1): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
sep 25 11:49:56 winston-wolfe NetworkManager[1289]: <info>  [1601027396.5181] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected
sep 25 11:49:56 winston-wolfe NetworkManager[1289]: <info>  [1601027396.6173] device (wlo1): supplicant interface state: disconnected -> scanning
sep 25 11:49:56 winston-wolfe NetworkManager[1289]: <info>  [1601027396.6173] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning
sep 25 11:49:56 winston-wolfe NetworkManager[1289]: <info>  [1601027396.7215] device (wlo1): supplicant interface state: scanning -> inactive
sep 25 11:49:56 winston-wolfe NetworkManager[1289]: <info>  [1601027396.7215] device (p2p-dev-wlo1): supplicant management interface state: scanning -> inactive
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.7926] device (wlo1): state change: need-auth -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.7931] manager: NetworkManager state is now CONNECTED_LOCAL
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.7943] device (wlo1): disconnecting for new activation request.
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.7944] audit: op="connection-activate" uuid="6df5bc60-2d2b-49d8-824b-79712bcf2c44" name="codenet" pid=2468 uid=1000 result="success"
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <warn>  [1601027397.7996] device (wlo1): Deactivation failed: GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.7996] device (wlo1): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8005] device (wlo1): Activation: starting connection 'codenet' (6df5bc60-2d2b-49d8-824b-79712bcf2c44)
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8013] device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8016] manager: NetworkManager state is now CONNECTING
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8019] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8039] device (wlo1): Activation: (wifi) access point 'codenet' has security, but secrets are required.
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8039] device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8041] sup-iface[0x563245dc7210,wlo1]: wps: type pbc start...
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8063] device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8066] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8069] device (wlo1): Activation: (wifi) connection 'codenet' has security, and secrets exist.  No new secrets needed.
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8069] Config: added 'ssid' value 'codenet'
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8069] Config: added 'scan_ssid' value '1'
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8069] Config: added 'bgscan' value 'simple:30:-65:300'
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8069] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.8070] Config: added 'psk' value '<hidden>'
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.9236] device (wlo1): supplicant interface state: inactive -> authenticating
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.9236] device (p2p-dev-wlo1): supplicant management interface state: inactive -> authenticating
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.9679] device (wlo1): supplicant interface state: authenticating -> associating
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.9679] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.9837] device (wlo1): supplicant interface state: associating -> associated
sep 25 11:49:57 winston-wolfe NetworkManager[1289]: <info>  [1601027397.9838] device (p2p-dev-wlo1): supplicant management interface state: associating -> associated
sep 25 11:49:58 winston-wolfe NetworkManager[1289]: <info>  [1601027398.0208] device (wlo1): supplicant interface state: associated -> 4-way handshake
sep 25 11:49:58 winston-wolfe NetworkManager[1289]: <info>  [1601027398.0209] device (p2p-dev-wlo1): supplicant management interface state: associated -> 4-way handshake
sep 25 11:50:02 winston-wolfe NetworkManager[1289]: <warn>  [1601027402.1023] sup-iface[0x563245dc7210,wlo1]: connection disconnected (reason 2)
sep 25 11:50:02 winston-wolfe NetworkManager[1289]: <info>  [1601027402.1074] device (wlo1): supplicant interface state: 4-way handshake -> disconnected
sep 25 11:50:02 winston-wolfe NetworkManager[1289]: <info>  [1601027402.1079] device (wlo1): Activation: (wifi) disconnected during association, asking for new key
sep 25 11:50:02 winston-wolfe NetworkManager[1289]: <info>  [1601027402.1079] device (wlo1): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
0
0
#5
Options
Re:Ubuntu 20.04 can't access Deco M4 wifi
2020-09-29 08:13:40

@Tony Hi any news on this? Is the deco defective and should I return it to amazon?

FRR149 wrote

Since yesterday, my laptop with Ubuntu 20.04 can't access the regular wifi created by the deco. It tries to connect, asks for the password, drops the connection and starts all over again. This happens every 5 seconds, it's ubelievable.

If I connect to the guest network (without a password) or another wifi by a Netgear router, everything works fine. It seems it's the authentication that suddenly stopped working. Both the laptop and Deco are up to date.

 

The wifi is configured on linux for WPA & WPA2 Personal and automatic IPV6

 

Any help would be greatly appreciated!

 

0
0
#6
Options
Re:Ubuntu 20.04 can't access Deco M4 wifi
2020-09-30 20:53:35 - last edited 2020-09-30 20:53:50

@FRR149 

 

What you could try is to download the M4 beta firmware that will allow you to change the wireless security to WPA2 AES (link), and test that connection. If the connection issue still persists, I would reach out to your local TP-Link support team at that point.

0
0
#7
Options
Re:Ubuntu 20.04 can't access Deco M4 wifi
2021-04-26 01:32:02
Hi guys. Ubuntu in different versions - latest 20.04 - with the same problem. Connection is intermittent with Deco M5 on wired ethernet backhaul. It seems that the mesh confuses my Ubuntu WIFI, which would be a shame for Ubuntu. All devices at home work fine. I have a 4 Deco M5 setup. Even if I connect manually, it disconnects.
0
0
#8
Options
Re:Ubuntu 20.04 can't access Deco M4 wifi
2021-04-26 01:49:18 - last edited 2021-04-26 02:08:29

Found the solution for Ubuntu 20.04 with DECO M5 Mesh on Ethernet Backhaul (Deco with up to date firmware)

 

I found the trail to the problem on this post:
https://www.raspberrypi.org/forums/viewtopic.php?t=251640

 

Without looking for the network foundations, I changed the timeout parameter in my Ubuntu 20.04 /etc/dhcp/dhclient.conf

Changed parameter timeout from 300 (5 minutes) to 30000 (500 minutes, 8.33 hours).

Now WIFI changes signal strength, is connected to a weaker AP, but stays connected.

 

 

 

0
0
#9
Options