Page 1 of 1

Re: Wireless disconnected, group key exchange timeout

Posted: Sat Jun 23, 2018 1:43 am
by microtek
Very nice information. Thank you for sharing this.

Re: Wireless disconnected, group key exchange timeout

Posted: Mon Jun 25, 2018 9:03 pm
by Resnais
Regarding the group key interval 1min- it will cost you some mobile device battery power if youre into u-apsd wmm + no_keep_alive_frames thing.
No more last activities on wireless clients like (80+sec):
last_activity.png
Ill try it with 2minutes group key interval and respond back.

Re: Wireless disconnected, group key exchange timeout

Posted: Tue Jun 26, 2018 1:20 am
by samsung172
this is a old issue. its 99% sure due to bad signal.

Re: Wireless disconnected, group key exchange timeout

Posted: Tue Jun 26, 2018 3:34 am
by Kerbia
Do you have the 6.42.4 running by now?

Re: Wireless disconnected, group key exchange timeout

Posted: Tue Jun 26, 2018 12:38 pm
by nkourtzis
I am also seeing this problem since a few days ago, with a MT map which connects as a WDS repeater to an RB951G, which is a repeater (non-WDS) of an ISP router. It works perfectly for maybe an hour at a time and then the map disconnects and starts logging these "key exchange timeout" messages..

Re: Wireless disconnected, group key exchange timeout

Posted: Tue Dec 25, 2018 6:39 pm
by gaborka
From changelog:

Channel
Installed Version 6.43.8
Latest Version 6.43.8
What's new in 6.43.8 (2018-Dec-21 07:10):

MAJOR CHANGES IN v6.43.8:
----------------------
!) telnet - do not allow to set "tracefile" parameter;
----------------------

Changes in this release:

*) bridge - fixed IPv6 link-local address generation when auto-mac=yes;
*) capsman - fixed "group-key-update" parameter not using correct units;
*) crs3xx - improved data transmission between 10G and 1G ports;
*) console - properly remove system note after configuration reset;

I set the group key update interval back to 1 hour. All connections seems to be stable (20+ minutes now).

Re: Wireless disconnected, group key exchange timeout

Posted: Sun Mar 31, 2019 3:57 pm
by gutekpl
this is a old issue. its 99% sure due to bad signal.
I don;t think so. It's currently affecting my MiBOX which lies around 50cm from cAP AC and has full signal strength.

Earlier had this for random devices on random times. Changed 05min to 1h now, will see. using CAPsMAN on 6.44.0