Community discussions

MikroTik App
 
lazerusrm
Member Candidate
Member Candidate
Topic Author
Posts: 162
Joined: Sat Jan 29, 2011 7:56 am

4 way handshake timeout

Fri Mar 11, 2016 6:52 am

I'm trying to figure out a problem im having

i seem to not be able to use any of the new RB firmwares as a station pseudobridge on a 802.11 wifi network

i get the problem 4 way handshake timeout.

Did i not get the memo? This used to work fine, but now i'm not sure which release to use.

any input on this?
 
lazerusrm
Member Candidate
Member Candidate
Topic Author
Posts: 162
Joined: Sat Jan 29, 2011 7:56 am

Re: 4 way handshake timeout

Mon Mar 14, 2016 1:19 pm

Does anyone really have info on this?

im going to test some older ROS versions and see which ones work with 802.11N routers.. it was like 6.15-6.20 that worked, and now i get handshake timeouts when using them as 802.11 pseudobridges.
 
jimmyz
Frequent Visitor
Frequent Visitor
Posts: 56
Joined: Wed Jul 02, 2014 10:10 pm

Re: 4 way handshake timeout

Thu Jun 09, 2016 8:58 am

Hi, I'm trying to investigate this, too.


Do your clients with this error connect at last to the AP?
 
jimmyz
Frequent Visitor
Frequent Visitor
Posts: 56
Joined: Wed Jul 02, 2014 10:10 pm

Re: 4 way handshake timeout

Thu Jun 09, 2016 9:59 am

Just now I noticed that it is a pseudobridge.
In my case it is an AP.

I will post portion of oa log:
jun/08 21:42:20 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, group key timeout 
jun/08 21:42:26 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 21:44:40 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 21:45:06 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 21:45:21 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 21:45:24 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 21:47:29 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 21:47:33 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 21:47:39 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, 4-way handshake timeout 
jun/08 21:59:02 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:00:10 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:00:11 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:01:54 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:03:21 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:04:24 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:06:49 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:07:20 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:07:37 dhcp,info defconf deassigned 10.160.0.242 from 20:55:31:xx:xx:xx 
jun/08 22:07:51 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, received disassoc: sending station leaving (8) 
jun/08 22:07:52 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:08:11 dhcp,info defconf assigned 10.160.0.242 to 20:55:31:xx:xx:xx 
jun/08 22:08:24 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:08:28 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:08:35 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:08:35 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:08:43 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:08:44 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:08:53 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:08:54 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:09:02 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:09:02 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:09:08 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:09:09 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:09:19 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:11:00 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:11:46 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
jun/08 22:30:59 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:31:05 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, 4-way handshake timeout 
jun/08 22:38:21 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:38:31 dhcp,info defconf deassigned 10.160.0.242 from 20:55:31:xx:xx:xx 
jun/08 22:38:57 caps,info 20:55:31:xx:xx:xx@dyo-Basebox2_B-1 connected 
jun/08 22:38:57 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, registered to other interface 
jun/08 22:38:59 dhcp,info defconf assigned 10.160.0.242 to 20:55:31:xx:xx:xx 
jun/08 22:39:14 caps,info 20:55:31:xx:xx:xx@dyo-Basebox2_B-1 disconnected, extensive data loss 
jun/08 22:39:46 caps,info 20:55:31:xx:xx:xx@dyo-Basebox2_B-1 connected 
jun/08 22:40:01 caps,info 20:55:31:xx:xx:xx@dyo-Basebox2_B-1 disconnected, extensive data loss 
jun/08 22:41:03 caps,info 20:55:31:xx:xx:xx@dyo-Basebox2_B-1 connected 
jun/08 22:43:44 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
jun/08 22:43:50 caps,info 20:55:31:xx:xx:xx@dyo-Basebox2_B-1 disconnected, extensive data loss 
jun/08 22:43:50 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, 4-way handshake timeout 
06:37:48 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
06:38:05 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
06:38:06 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
06:39:19 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
06:39:23 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
06:43:15 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
06:44:03 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
06:44:10 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
06:44:11 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
06:44:26 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
06:44:28 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
06:44:43 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
06:44:48 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
06:44:56 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
06:44:56 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
06:45:09 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
06:45:11 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
06:45:26 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
06:45:27 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
07:17:57 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
07:20:05 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
07:20:37 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, received disassoc: sending station leaving (8) 
07:20:39 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
07:20:45 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, 4-way handshake timeout 
07:25:26 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
07:25:36 dhcp,info defconf deassigned 10.160.0.242 from 20:55:31:xx:xx:xx 
07:25:36 dhcp,info defconf assigned 10.160.0.242 to 20:55:31:xx:xx:xx 
07:32:20 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, group key timeout 
07:32:22 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
07:32:27 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
07:32:28 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
07:32:33 dhcp,info defconf deassigned 10.160.0.242 from 20:55:31:xx:xx:xx 
07:32:36 dhcp,info defconf assigned 10.160.0.242 to 20:55:31:xx:xx:xx 
07:32:44 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
07:32:44 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
07:32:49 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
07:32:51 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
07:32:59 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
07:32:59 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
07:33:05 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, extensive data loss 
07:33:06 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 
07:33:10 dhcp,info defconf deassigned 10.160.0.242 from 20:55:31:xx:xx:xx 
07:33:22 dhcp,info defconf assigned 10.160.0.242 to 20:55:31:xx:xx:xx 
08:12:20 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 disconnected, group key timeout 
08:12:26 caps,info 20:55:31:xx:xx:xx@dyo-MikroTik-1 connected 

This is Capsman and the two CAPs taking place are in 2,4GHz
 
efaden
Forum Guru
Forum Guru
Posts: 1708
Joined: Sat Mar 30, 2013 1:55 am
Location: New York, USA

Re: 4 way handshake timeout

Mon Jul 25, 2016 11:07 pm

Ever figure this out?
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: 4 way handshake timeout

Tue May 09, 2017 1:24 pm

Have you once found a solution for this?
 
jimmyz
Frequent Visitor
Frequent Visitor
Posts: 56
Joined: Wed Jul 02, 2014 10:10 pm

Re: 4 way handshake timeout

Tue May 09, 2017 1:39 pm

I think it means, in some devices, the wifi password was not entered correctly. It has really been a long time I haven't red the log from this device. I will, at first chance, after updating.
 
valdemirrix
just joined
Posts: 2
Joined: Mon Jan 07, 2019 5:45 pm

Re: 4 way handshake timeout

Mon Jan 07, 2019 6:03 pm

Hi there,

Although the Mikrotik (HAP Lite) settings are correct, it disconnects continuously.
I had already read on another list that the message was a password error, but I was sure it was correct.

At the terminal checked the settings:

/ wireless interface security-profile print without-paging

The keys were as they should be: in capital letters (ABCD26218). I changed the letters to lowercase and magic: stopped disconnecting, got IP address and is working very well.

to make sure I did on the same command line:
/ wireless interface security-profiles> set name = "PROFILE_NAME" wpa-pre-shared-key = "abcd26218" wpa2-pre-shared-key = "abcd26218".

Do not ask me why it worked in lowercase when the key was uppercase in the AP, but soved my problem;
 
victornc
just joined
Posts: 3
Joined: Fri Dec 16, 2016 1:09 pm

Re: 4 way handshake timeout

Fri Oct 09, 2020 9:38 pm

El problema viene por las interferencias, este tipo de error (4 way handshake timeout) lo vamos a encontrar en cualquier marca, aunque es cierto que ruckus lo maneja algo mejor, pero prefiero Mikrotik ya que permite más parametrización.
Despues de muchas pruebas con este tipo de errores mi consejo es adquirir AP con alta sensibilidad en escucha y reducirles la potencia de salida en no más de 15 db, esto nos permite tener más dispositivos y evitar interferencias. Al tener más sensibilidad mejoramos la comunicación en dispositivos como móviles y tablets, no sirve de nada tener un AP potente si el cliente no es capaz de emitir con la misma potencia para escucharlo.
En cuanto a configuración yo recomiendo doble canal (20Mhz/40Mhz XX) tanto en 2.4 Ghz como en 5 Ghz, esto nos permitirá tener velocidades de hasta 150 Mb en 2.4 Ghz y 400 Mb en Ghz, con esta configuración el AP realizará la gestión de canales de forma automática permitiendo que se alternen, ya que en 2.4 tenemos 3 canales completos de 20 MHZ y 4 canales en 5 Ghz (Activando "evitar" canales DFS para mayor compatibilidad).
Recuerdo que este tipo de configuración que recomiendo es para CAPsMAN con varios AP y alta densidad de conectividad, de nada sirve conectar clientes con alto ancho de banda si la conexión de cable es a 1Gb, ya que hay dividirla entre clientes, por este motivo es mejor tener más AP con menos potencia y distribuirlos.
######################################
Translation by Google:
The problem comes from the interferences, this type of error (4 way handshake timeout) we will find in any brand, although it is true that ruckus handles it somewhat better, but I prefer Mikrotik since it allows more parameterization.
After many tests with these types of errors, my advice is to acquire APs with high listening sensitivity and reduce their output power by no more than 15 db, this allows us to have more devices and avoid interference. By having more sensitivity we improve communication on devices such as mobiles and tablets, it is useless to have a powerful AP if the client is not able to broadcast with the same power to listen to it.
Regarding configuration, I recommend dual channel (20Mhz / 40Mhz XX) in both 2.4 Ghz and 5 Ghz, this will allow us to have speeds of up to 150 Mb in 2.4 Ghz and 400 Mb in Ghz, with this configuration the AP will manage the channels automatically allowing them to alternate, since in 2.4 we have 3 complete channels of 20 MHZ and 4 channels in 5 Ghz (Activating "avoid" DFS channels for greater compatibility).
I remember that this type of configuration that I recommend is for CAPsMAN with several APs and high connectivity density, it is useless to connect clients with high bandwidth if the cable connection is 1Gb, since it must be divided between clients, for this reason it is better to have more APs with less power and distribute them.

Who is online

Users browsing this forum: bpwl, emunt6, morphema, synchro and 17 guests