I seem to be getting this message in my log at station end with more occurrence lately.

Setup is, RB133 with R52H card transmitting to identical @ 23km good LOS

Transmitter is 180° waveguide 13dBi, card at default power (25dBm), ap bridge, S/N 37, CCQ 68-55%, Signal -84 ave, 2412MHz freq, adaptive noise immunity ap client. AP log shows disconnected OK, reassociating, connected, whis is in unision with the station log of lost connection, no beacons received

Station hardware same, except 24dBi grid at horizontal polarity, S/N 15-16, CCQ 23-66.

We are in a very remote area, there shouldn't be any other signal anywhere except my own. I work all radios at channel 1, 6, 11 where crossover may occur.

The beacon loss is intermittent, every few seconds for periods of 20 mins or so, then the link will stay up for many hours. I am trying to pin it to some atmospheric regularity, but that doesn't seem to have any definity.

I have a similar link 2km shorter about 20° offset from the same transmitter, but is a WRT54GL with DD-WRT, on about the same signal stength, with a 19dBi pannel antenna set for horizontal polarity, that has a stable connection for weeks at a time!!!! There are no fancy settings on that unit either, except the radio set to 200mw.

I have tried many things on the RB unit, getting very frustrated.

The wiki is marvelous, but couldn't find much to help me resove this. I am going to try a different antenna, perhaps a similar pannel for a trial, but I would have thought the grid would have been the best.

Oh, ACk timeout set to dynamic on both.

Wondering if someone cold help please!

Did you enable Debug Logs to see more info about this disconnection?
http://wiki.mikrotik.com/wiki/Wireless_Debug_Logs

Thanks normis, will do, have done.

Will wait to see what gets logged. Will keep posted

Righto', have got some logs that indicate that connectionwas lost, no beacons, then the wireless goes through a list of other signals from other AP's, but vastly different frequencies. Two of these are mounted on the same tower, 180° waveguides, 2462, and 2437 MHz, 3m higher. Another is 54km distant, but would be at a non significant strength, the log doesn't say.

One log line says must connetct to strongest signal which is the one it has just disconnected from.

Is there a way to extract the log as a file to analyze? Even to post here for some enlightening help?

Thanks again

PS, maybe I didn't explain well enough in the original post, this RB133 has 3 radios, 2xAP's as above to transmit via the waveguides, one as station, from the master transmitter 23km distant.

Signal -84 ave

Your signal is too low, that's why the connection is dropping.

Your signal is too low, that's why the connection is dropping.

Well, yes, but why have I many others even worse, up to -90 that will stay connected for days on end, even weeks, without a dropout? I have a -92 on average, that regulalrly transmits 1-2mb reliably 24/7, possibly with 1-2 reconnections in that 7 day stretch.

I must admit, they aren't Mikrotik!

signal should be around -60 to be fine, but anyway, i'm not convinced that it's all of the problem. can you post some of the debug logs in their entirety ?

signal should be around -60 to be fine, but anyway, i'm not convinced that it's all of the problem. can you post some of the debug logs in their entirety ?

Thank you normis. I am finding a great deal like you said. Tx end said 'not in ACL', so I copied the Rx end into the Access List. Same at the Rx end, debug said 'not in connect list', so have copied it into Connect List.

Now, to achieve what you ask, do I set the action to disk rather than memory? Then where would the file be to copy and paste in the post?

open the terminal in winbox, and type "/log print without-paging" and use the mouse to copy some of the logs. paste them here in the forum.

11:54:12 wireless,info 00:0C:42:18:D9:B0@wlan3: lost connection, no beacons received
11:54:14 wireless,debug wlan3: must select network
11:54:14 wireless,debug 00:0C:42:1F:3A:DC: on 2437 AP: yes SSID tooligie_hill-ap2 caps 0x421 rates 0xff0f basic 0xf MT: yes
11:54:14 wireless,debug 00:0C:42:1F:3A:C0: on 2462 AP: yes SSID tooligie_hill-ap1 caps 0x421 rates 0xff0f basic 0xf MT: yes
11:54:14 wireless,debug 00:0C:42:18:D9:B0: on 2412 AP: yes SSID Lock-sw-ap1 caps 0x421 rates 0xff0f basic 0xf MT: yes
11:54:14 wireless,debug 00:0C:42:18:EC:E7: on 2437 AP: yes SSID eol-lock-ap1-2 caps 0x421 rates 0xf basic 0x1 MT: yes
11:54:14 wireless,debug 00:0C:42:1F:49:C8: on 2412 AP: yes SSID eol-lock-ap1-1 caps 0x421 rates 0x3 basic 0x1 MT: yes
11:54:14 wireless,debug 00:0C:42:1F:3A:DF: on 2462 AP: yes SSID Lock-sw-ap2 caps 0x421 rates 0xff0f basic 0xf MT: yes
11:54:14 wireless,debug 00:02:6F:45:12:92: on 2437 AP: yes SSID Gunnamatta caps 0x421 rates 0xff0f basic 0xf MT: yes
11:54:14 wireless,debug 00:0C:42:1F:3A:F5: on 2437 AP: yes SSID eol-myoung-ap1-2 caps 0x421 rates 0xff0f basic 0xf MT: yes
11:54:14 wireless,debug wlan3: no network that satisfies connect-list, by default choose with strongest signal
11:54:14 wireless,info 00:0C:42:18:D9:B0@wlan3 established connection on 2412, SSID Lock-sw-ap1
15:50:09 wireless,info 00:0C:42:18:D9:B0@wlan3: lost connection, received deauth: authentication not valid (2)
15:50:11 wireless,debug wlan3: must select network
15:50:11 wireless,debug 00:0C:42:1F:3A:DC: on 2437 AP: yes SSID tooligie_hill-ap2 caps 0x421 rates 0xff0f basic 0xf MT: yes
15:50:11 wireless,debug 00:0C:42:1F:3A:C0: on 2462 AP: yes SSID tooligie_hill-ap1 caps 0x421 rates 0xff0f basic 0xf MT: yes
15:50:11 wireless,debug 00:0C:42:18:D9:B0: on 2412 AP: yes SSID Lock-sw-ap1 caps 0x421 rates 0xff0f basic 0xf MT: yes
15:50:11 wireless,debug 00:0C:42:18:EC:E7: on 2437 AP: yes SSID eol-lock-ap1-2 caps 0x421 rates 0xf basic 0x1 MT: yes
15:50:11 wireless,debug 00:0C:42:1F:49:C8: on 2412 AP: yes SSID eol-lock-ap1-1 caps 0x421 rates 0x3 basic 0x1 MT: yes
15:50:11 wireless,debug 00:0C:42:1F:3A:DF: on 2462 AP: yes SSID Lock-sw-ap2 caps 0x421 rates 0xff0f basic 0xf MT: yes
15:50:11 wireless,debug 00:02:6F:45:12:92: on 2437 AP: yes SSID Gunnamatta caps 0x421 rates 0xff0f basic 0xf MT: yes
15:50:11 wireless,debug 00:0C:42:1F:3A:F5: on 2437 AP: yes SSID eol-myoung-ap1-2 caps 0x421 rates 0xff0f basic 0xf MT: yes
15:50:11 wireless,debug wlan3: no network that satisfies connect-list, by default choose with strongest signal
15:50:11 wireless,info 00:0C:42:18:D9:B0@wlan3 established connection on 2412, SSID Lock-sw-ap1
15:53:28 system,info,account user admin logged in from 203.34.11.10 via winbox
15:56:10 wireless,info 00:0C:42:18:D9:B0@wlan3: lost connection, connect-list changed
15:56:10 system,info wireless connect-list entry added by admin
15:56:11 wireless,debug wlan3: must select network
15:56:11 wireless,debug 00:0C:42:1F:3A:DC: on 2437 AP: yes SSID tooligie_hill-ap2 caps 0x421 rates 0xff0f basic 0xf MT: yes
15:56:11 wireless,debug 00:0C:42:1F:3A:C0: on 2462 AP: yes SSID tooligie_hill-ap1 caps 0x421 rates 0xff0f basic 0xf MT: yes
15:56:11 wireless,debug 00:0C:42:18:D9:B0: on 2412 AP: yes SSID Lock-sw-ap1 caps 0x421 rates 0xff0f basic 0xf MT: yes
15:56:11 wireless,debug 00:0C:42:18:EC:E7: on 2437 AP: yes SSID eol-lock-ap1-2 caps 0x421 rates 0xf basic 0x1 MT: yes
15:56:11 wireless,debug 00:0C:42:1F:49:C8: on 2412 AP: yes SSID eol-lock-ap1-1 caps 0x421 rates 0x3 basic 0x1 MT: yes
15:56:12 wireless,debug 00:0C:42:1F:3A:DF: on 2462 AP: yes SSID Lock-sw-ap2 caps 0x421 rates 0xff0f basic 0xf MT: yes
15:56:12 wireless,debug 00:02:6F:45:12:92: on 2437 AP: yes SSID Gunnamatta caps 0x421 rates 0xff0f basic 0xf MT: yes
15:56:12 wireless,debug 00:0C:42:1F:3A:F5: on 2437 AP: yes SSID eol-myoung-ap1-2 caps 0x421 rates 0xff0f basic 0xf MT: yes
15:56:12 wireless,info 00:0C:42:18:D9:B0@wlan3 established connection on 2412, SSID Lock-sw-ap1

Hope this helps noemis

Thanks again

which is the mac that is causing problems?

about the "no beacons" error you can read in the link I gave you:

"no beacons" - no beacons received from remote end of WDS link. Most likely weak signal, remote turned off, strong interference, some other RF related issue that makes communication impossible.

And this is from theTx end

11:54:10 wireless,info 00:0C:42:1F:3A:D1@wlan1: disconnected, ok
11:54:10 wireless,debug wlan1: 00:0C:42:1F:3A:D1 not in local ACL, by default accept
11:54:10 wireless,info 00:0C:42:1F:3A:D1@wlan1: connected
11:54:14 wireless,debug wlan1: 00:0C:42:1F:3A:D1 attempts to associate
11:54:14 wireless,info 00:0C:42:1F:3A:D1@wlan1: reassociating
11:54:14 wireless,info 00:0C:42:1F:3A:D1@wlan1: disconnected, ok
11:54:14 wireless,debug wlan1: 00:0C:42:1F:3A:D1 not in local ACL, by default accept
11:54:14 wireless,info 00:0C:42:1F:3A:D1@wlan1: connected
15:50:09 wireless,info 00:0C:42:1F:3A:D1@wlan1: disconnected, access-list changed
15:50:09 system,info wireless access-list entry added by admin
15:50:11 wireless,debug wlan1: 00:0C:42:1F:3A:D1 attempts to associate
15:50:11 wireless,debug wlan1: 00:0C:42:1F:3A:D1 in local ACL, accept
15:50:11 wireless,info 00:0C:42:1F:3A:D1@wlan1: connected
15:56:12 wireless,debug wlan1: 00:0C:42:1F:3A:D1 attempts to associate
15:56:12 wireless,info 00:0C:42:1F:3A:D1@wlan1: reassociating
15:56:12 wireless,info 00:0C:42:1F:3A:D1@wlan1: disconnected, ok
15:56:12 wireless,debug wlan1: 00:0C:42:1F:3A:D1 in local ACL, accept
15:56:12 wireless,info 00:0C:42:1F:3A:D1@wlan1: connected

which is the mac that is causing problems?

This one

00:0C:42:1F:3A:DF

which is the mac that is causing problems?

This one

00:0C:42:1F:3A:DF

I don't see this MAC disconnection in the logs you pasted

Bump.

I'd be interested to learn if and if so how this problem was resolved as I have the same problem.

Logged at station

09:52:58 wireless,info 00:02:6F:4B:27:49@Elie: lost connection, no beacons received
09:53:00 wireless,debug Elie: must select network
09:53:00 wireless,debug 00:02:6F:4B:27:49: on 2412 AP: yes SSID Crail caps 0x431 rates 0xf basic 0x1 MT: yes
09:53:00 wireless,debug 00:02:6F:52:DB:D3: on 2442 AP: yes SSID Bobbery caps 0x431 rates 0xf basic 0x1 MT: yes
09:53:00 wireless,info 00:02:6F:4B:27:49@Elie established connection on 2412, SSID Crail
09:59:34 wireless,info 00:02:6F:4B:27:49@Elie: lost connection, no beacons received
09:59:36 wireless,debug Elie: must select network
09:59:36 wireless,debug 00:02:6F:4B:27:49: on 2412 AP: yes SSID Crail caps 0x431 rates 0xf basic 0x1 MT: yes
09:59:36 wireless,debug 00:02:6F:52:DB:D3: on 2442 AP: yes SSID Bobbery caps 0x431 rates 0xf basic 0x1 MT: yes
09:59:36 wireless,info 00:02:6F:4B:27:49@Elie established connection on 2412, SSID Crail
09:59:38 wireless,info 00:02:6F:4B:27:49@Elie: lost connection, no beacons received
09:59:40 wireless,debug Elie: must select network
09:59:40 wireless,debug 00:02:6F:4B:27:49: on 2412 AP: yes SSID Crail caps 0x431 rates 0xf basic 0x1 MT: yes
09:59:40 wireless,debug 00:02:6F:52:DB:D3: on 2442 AP: yes SSID Bobbery caps 0x431 rates 0xf basic 0x1 MT: yes
09:59:40 wireless,info 00:02:6F:4B:27:49@Elie established connection on 2412, SSID Crail
10:06:14 wireless,info 00:02:6F:4B:27:49@Elie: lost connection, no beacons received
10:06:16 wireless,debug Elie: must select network
10:06:16 wireless,debug 00:02:6F:4B:27:49: on 2412 AP: yes SSID Crail caps 0x431 rates 0xf basic 0x1 MT: yes
10:06:16 wireless,debug 00:02:6F:52:DB:D3: on 2442 AP: yes SSID Bobbery caps 0x431 rates 0xf basic 0x1 MT: yes
10:06:16 wireless,info 00:02:6F:4B:27:49@Elie established connection on 2412, SSID Crail
10:06:18 wireless,info 00:02:6F:4B:27:49@Elie: lost connection, no beacons received
10:06:19 wireless,debug Elie: must select network
10:06:19 wireless,debug 00:02:6F:4B:27:49: on 2412 AP: yes SSID Crail caps 0x431 rates 0xf basic 0x1 MT: yes
10:06:19 wireless,debug 00:02:6F:52:DB:D3: on 2442 AP: yes SSID Bobbery caps 0x431 rates 0xf basic 0x1 MT: yes
10:06:19 wireless,info 00:02:6F:4B:27:49@Elie established connection on 2412, SSID Crail
10:12:54 wireless,info 00:02:6F:4B:27:49@Elie: lost connection, no beacons received
10:12:56 wireless,debug Elie: must select network
10:12:56 wireless,debug 00:02:6F:4B:27:49: on 2412 AP: yes SSID Crail caps 0x431 rates 0xf basic 0x1 MT: yes
10:12:56 wireless,debug 00:02:6F:52:DB:D3: on 2442 AP: yes SSID Bobbery caps 0x431 rates 0xf basic 0x1 MT: yes
10:12:56 wireless,info 00:02:6F:4B:27:49@Elie established connection on 2412, SSID Crail
10:12:58 wireless,info 00:02:6F:4B:27:49@Elie: lost connection, no beacons received
10:12:59 wireless,debug Elie: must select network
10:12:59 wireless,debug 00:02:6F:4B:27:49: on 2412 AP: yes SSID Crail caps 0x431 rates 0xf basic 0x1 MT: yes
10:12:59 wireless,debug 00:02:6F:52:DB:D3: on 2442 AP: yes SSID Bobbery caps 0x431 rates 0xf basic 0x1 MT: yes
10:12:59 wireless,info 00:02:6F:4B:27:49@Elie established connection on 2412, SSID Crail


Logged at AP:

09:52:56 wireless,debug Crail: 00:02:6F:4B:27:44 attempts to associate
09:52:56 wireless,info 00:02:6F:4B:27:44@Crail: reassociating
09:52:56 wireless,info 00:02:6F:4B:27:44@Crail: disconnected, ok
09:52:56 wireless,debug Crail: 00:02:6F:4B:27:44 in local ACL, accept
09:52:56 wireless,info 00:02:6F:4B:27:44@Crail: connected
09:53:00 wireless,debug Crail: 00:02:6F:4B:27:44 attempts to associate
09:53:00 wireless,info 00:02:6F:4B:27:44@Crail: reassociating
09:53:00 wireless,info 00:02:6F:4B:27:44@Crail: disconnected, ok
09:53:00 wireless,debug Crail: 00:02:6F:4B:27:44 in local ACL, accept
09:53:00 wireless,info 00:02:6F:4B:27:44@Crail: connected
09:59:36 wireless,debug Crail: 00:02:6F:4B:27:44 attempts to associate
09:59:36 wireless,info 00:02:6F:4B:27:44@Crail: reassociating
09:59:36 wireless,info 00:02:6F:4B:27:44@Crail: disconnected, ok
09:59:36 wireless,debug Crail: 00:02:6F:4B:27:44 in local ACL, accept
09:59:36 wireless,info 00:02:6F:4B:27:44@Crail: connected
09:59:39 wireless,debug Crail: 00:02:6F:4B:27:44 attempts to associate
09:59:39 wireless,info 00:02:6F:4B:27:44@Crail: reassociating
09:59:39 wireless,info 00:02:6F:4B:27:44@Crail: disconnected, ok
09:59:39 wireless,debug Crail: 00:02:6F:4B:27:44 in local ACL, accept
09:59:39 wireless,info 00:02:6F:4B:27:44@Crail: connected
10:06:16 wireless,debug Crail: 00:02:6F:4B:27:44 attempts to associate
10:06:16 wireless,info 00:02:6F:4B:27:44@Crail: reassociating
10:06:16 wireless,info 00:02:6F:4B:27:44@Crail: disconnected, ok
10:06:16 wireless,debug Crail: 00:02:6F:4B:27:44 in local ACL, accept
10:06:16 wireless,info 00:02:6F:4B:27:44@Crail: connected
10:06:19 wireless,debug Crail: 00:02:6F:4B:27:44 attempts to associate
10:06:19 wireless,info 00:02:6F:4B:27:44@Crail: reassociating
10:06:19 wireless,info 00:02:6F:4B:27:44@Crail: disconnected, ok
10:06:19 wireless,debug Crail: 00:02:6F:4B:27:44 in local ACL, accept
10:06:19 wireless,info 00:02:6F:4B:27:44@Crail: connected
10:12:56 wireless,debug Crail: 00:02:6F:4B:27:44 attempts to associate
10:12:56 wireless,info 00:02:6F:4B:27:44@Crail: reassociating
10:12:56 wireless,info 00:02:6F:4B:27:44@Crail: disconnected, ok
10:12:56 wireless,debug Crail: 00:02:6F:4B:27:44 in local ACL, accept
10:12:56 wireless,info 00:02:6F:4B:27:44@Crail: connected
10:12:59 wireless,debug Crail: 00:02:6F:4B:27:44 attempts to associate
10:12:59 wireless,info 00:02:6F:4B:27:44@Crail: reassociating
10:12:59 wireless,info 00:02:6F:4B:27:44@Crail: disconnected, ok
10:12:59 wireless,debug Crail: 00:02:6F:4B:27:44 in local ACL, accept

This is a P2P backbone link between two sites. The station end is also running a point-to-multipoint AP at 2442MHz and the AP is also running a second AP at 2472MHz.

When the station end loses the connection it scans and reports two APs, viz the one it should connect to - Crail - and the one running right next to it - Bobbery. It correctly reassociates with Crail but gets bumped off again almost immediately. Is it the case that the adjacent AP 'overwhelmes' the correct link despite the frequency difference? (2412GHz vs 2442)

If so is there any way to stop this happening without changing frequencies?

Also, it's very noticeable that the 'interrupts' are happening at quite regular intervals of around 6.5 minutes. Is this a clue?

Well, for what it's worth I turned on Adaptive Noise Immunity at both ends of the link, enabled nstream and polling and disabled CSMA (whatever that is) and the problem went away.

Quite which of the above (or combination thereof) did the trick I don't know, and whether the link quality/throughput will actually be worse as a result remains to be seen.

The disconnects will happen as a result of :
1) The AP not being able to make out what the client was transmitting even throughout all the retransmit attempts.
2) The Client not being able to make out what the AP was transmitting even throughout all the retransmit attempts.

This could be due to many things.
-90 can net OK results, if the frequency is 99% free (and by that; I mean the spectrum not 802.11).
Ultimately it is noise, or the perception of noise through your antenna, cabling, amplifiers, and radio cards which are filtered from the 802.11 signal by the radio card, and if the signal is integral the signal is accepted.

As everyone itterates over and over again, PLEASE check your antenna, connectors, cabling, and electronics.
If you do not have a spectral analyzer, do consider aquiring one, it is really the only truely good way to determine and measure noise.

Hi I have the same problem with no beacons received msg in CPE log

Situation:

RB411 as ap-bridge with clients connected to it and one RB433 (now as WDS station) as client(pseudobridge) and ap-bridge on second card.
Distance is cca 600m, signal cca -60 to -65 dbm on both ends.

At first I had:
[ap-bridge RB411 ROSv3.30 R52] --- [pseudobridge RB433 ROSv3.25 R52]

It worked not bad

I wanted to upgrade hardware and firmware so I turned off the MT AP RB411 and changed card to R52nM and updated to 4.16
After change RB433 started to have problems with beacons.
So I thought that upgrade would help, but I was wrong.

Now I have:
[ap-bridge RB411 ROSv4.16 R52nM] --- [station-wds RB433 ROSv4.16 R52nM]

After cca 6.50 minutes station-wds disconnects and it's log writes:
16:05:22 wireless,info [AP-MAC]@wlan1_CL: lost connection, no beacons received
16:05:24 wireless,info [AP-MAC]@wlan1_CL established connection on 2472, SSID [xxx]
16:05:28 wireless,info [AP-MAC]@wlan1_CL: lost connection, no beacons received
16:05:30 wireless,info [AP-MAC]@wlan1_CL established connection on 2472, SSID [xxx]

So I tried to
- change standard to B/G and then to B
- change signal strenghts
- frequency
- RTS/CTS
- HT Guard from any to long
- disable HT extension channel
- turn on and off ANI on atheros cards

but nothing helped

So finally I tried to set Nstreme on both ends and it helped, but the other CPEs didn't connect as expected.

So I don't know what do do now - I have two thoughts:

-I've read that reset of RBs and set everything again could help.
-I thought about creating Virtual AP with Nstreme, but I don't know if it's achievable.

I don't want to switch back to G standard. I also afraid of the same problem with older cards and ROSv4.16.
Thank for any help.

This thread should help (explains why):
http://forum.mikrotik.com/viewtopic.php?f=13&t=49321

These too (explains how to correct):
http://forum.mikrotik.com/viewtopic.php?f=13&t=48784
http://forum.mikrotik.com/viewtopic.php?f=7&t=49306
http://forum.mikrotik.com/viewtopic.php?f=7&t=49073

ADD: Since I have been posting it in other threads, it has been 5w2d1h20m37s since a disconnect.
And this does not only apply to a-mode. If you use n-mode, the log message would be

16:05:22 wireless,info [AP-MAC]@wlan1_CL: lost connection, not polled too long

Hedy Lamarr was not only beautiful and talented, but very intelligent. That is why I vote Hedy Lamarr the "Most Dangerous Woman" of the 20th century.

I've tried everything but nothing helped.

I thought about different thing:
I have two antennas on same holder both connected to different cards in RB433

Finally I've tried to disable AP on RB433 and connection drop went away.
After that I've thought about reasons - so I switched frequency from 6 to channel 1 on AP and enabled AP but problem came back.

The question is why problem rised after update to R52nM and ROSv4.16? And wasn't there before?

Is it possible that beacon from AP interferes beacon from AP-bridge on RB411 (main AP), although each broadcast on different frequencies (first and last channel)?

Now I can't fix cables nor antennas because of weather.
Is there any other way how to fix it?
I thought about temporary switch AP to WDS-slave and disable WDS-station interface. Or add AP (maybe from another manufacturer) as AP-bridge or WDS-station.

I have two antennas on same holder both connected to different cards in RB433

Me too.

After that I've thought about reasons - so I switched frequency from 6 to channel 1 on AP and enabled AP but problem came back.

Me too.

The question is why problem rised after update to R52nM and ROSv4.16? And wasn't there before?

I'm on V4.16
Please enable verbose logging on the station router. Then post the log entries after a disconnect.

debug log said (before change below):
03:07:02 wireless,info [AP-MAC]@wlan1_CL: lost connection, no beacons received
03:07:04 wireless,debug wlan1_CL: must select network
[some AP-MACs]
...

all 3x in log.

I tried to reduce AP signal strength on RB433 and enable this AP and disconnect problem went away.
But now CPEs of this AP are connected, but no ping or possibility to manage them
I don't think it's problem of signal strength. It's strange. Tried to change frequency of AP as was before - not helped.

03:07:04 wireless,debug wlan1_CL: must select network

means "frequency hopping". Please post "/interface wireless" from the station router.

The connection to CPEs established forgot to renew new interface (R52nM) in bridge (wondering how it could work before, without this change)

With default-authentication=no beacon loss happens more rare and 1x in one peace, but they are back when I rise signal strength on AP on RB433 .
I suppose that the worst is after me - it's not ideal, but I'll watch connection for stability. But I don't know what to do except change cables when weather permits.

Could help change default-authentication on wlan1_AP?

All seems ok there, as I expected. It is the station that is causing the challenge. If the station is set to "default-authentication=yes", then that will cause the interruption. It will occasionally search for a better (less busy) connection.

Now wds-station disconnects after 6-50 minutes. (often more frequently)
I noticed this (don't know if it's problem):

When I open details of connection in Winbox on RB411 (main AP) RX sometimes varies. For Ex. (1mb -> 54mb ->1mb -> 48mb -> ...)

Second notice i've made with my Android mobile:
Wifi analyzer of mobile displays The Main AP as 5GHz on unknow channel. It must be mobile error, but other stations are shown in 2.4GHz and with channel number.

Is wds necessary for your setup? I don't use it. How many "station-wds" units are on the AP?
What does "/interface wireless registration-table" show for the signal strengths and snr?

I use "mode=ap-bridge" on my APs and "mode=station" on my stations.

Are you still getting this message?

03:07:04 wireless,debug wlan1_CL: must select network

From what I see from experiments, this means "frequency hopping".

Tomorrow I'll try mode="station"
This is only one "station-wds" on this AP

Signal strenghts -65 to -60, SNR around 45dB.

Yes, still getting:
02:27:44 wireless,info [AP-MAC]@wlan1_CL: lost connection, no beacons received
02:27:46 wireless,debug wlan1_CL: must select network

Is there any other option how to stop "freq. hopping" ?

My signal/snr is real good also. And I was getting disconnects just like that before the "default-authentication=no" change.

I have contacted Mikrotik support about this. I will let you know what they say.

Tried mode="station-pseudobridge" but without "no beacons received" change.
Even though it seems reconnection is faster.

I am waiting for a response from Mikrotik support about this issue. When I hear from them, I will post the answer here.

ADD: I heard from support. They seem certain that "default-authentication" has nothing to do with the beacons and disconnects. Maybe they are correct. Could it be that all the noise or interference disappeared the exact time I set "default-authentication=no" almost 6 weeks ago?

They have asked me to set "default-authentication=yes" and see if the problem reappears, so I have. I do not expect anything in the log until this afternoon if the disconnects start again. The disconnects were only happening when that backhaul radio gets busy.

I will let you know what happens.

UPDATE: The result is here:
http://forum.mikrotik.com/viewtopic.php?f=13&t=49321

Is there any other way how to stabilize connection?
There isn't way how to set VirtualAP with Nstreme and normal AP without it, is there?

Maybe there is problem within Mirkotik device - disconnection after exactly 6:50 minutes should be a clue.
Try to disable CSMA/CA or completelly replace Mikrotik device to non-Mikrotik client?

DeIM, could you contact support about this issue? Include the support output files from AP and station which are made when you see those problems.

It must be some HW issue. Maybe connector on new pigtail (MMCX) between miniPCI card and cable to Antenna. Or miniPCI card itself.
The other (non-MT) devices aren't so sensitive to this regular 6:50 loss of signal.

I disassembled it and found the dielectric is a little closer to the end of central male pin than on pigtail before (u.fl).

Found this on CPE MT: Shouldn't it be issue with b/g/n standards together?

replaced pigtail, still getting:

Hi Guys

Have you found a solution to this problem?
It appears i am having the same issue. I have a RB411 Station connecting to an AP Bridge 600m away.
I also have another RB433 AP connected to the same pole.

The errors you were getting are the exact same.

So frustrating, please assist.

many ppl have this problem ...
its a well known thing... that need a fix....
mt just....... don't see it!!!

Mikrotik,

Is there really no fix for this? This has been going on for years now with the wireless package, I had hoped it would be fixed with 5.x but it is still there. Clients with solid connections, good signal strength, good CCQ and I still have logs full of lost connection, no beacons received. These are non WDS links just straight station mode.

Between this and the timing related disconnects of NV2 I am about ready to give up.

Hi ...

Some preliminary figures. First, second & third scenarios are the same test RB411AR, just swaping cards & functions (AP/client). Fourth and fifth scenarios are production links.

1st scenario: AP R52nM on 2.4GHz, G only & CPE 411AR fitted with R52Hn (AR9220) as client (built in card AR5215 as 2.4AP, G only) => Lost connection, no beacons received.

2nd scenario: AP R52nM on 2.4GHz, G only & CPE 411AR fitted with R52nM (AR9220) as client (built in card AR5215 as 2.4AP, G only) => Lost connection, no beacons received.

3rd scenario: AP R52nM on 2.4GHz, G only & CPE 411AR fitted with R52nM (AR9220) as AP (built in card AR5215 as client, G only) => Up and running for 5 hours now.

4th scenario: AP SR2 on 2.4GHz, G only & CPE WRAp X86 fitted with R52Hn (AR9220) as client => Up and running for 18 days!

5th scenario: AP R52nM on 2.4GHz, G only & CPE 411AR fitted with R52nM (AR9220) as AP (built in card AR5215 as client, G only) => Up and running for 5 days 8 hours and counting.

So ...

* AR9220 is not a good client to AR9220?

* AR9220 is a good client for SR2?

* AR5215 is a good client for AR9220/AR5215?

And an already disassembled config ... R52Hn (AR9220) as client of a AR5215 = lost connection, no beacons received ... but a SR2 as client of the same AP, no problem at all.

BTW, makes no difference at the test 411AR to disable the built in AP.

Signals from -68 to -72, connections speeds from 36 to 54MBps, CCQ > 90, SNR ~40dB.

Regards;

Yes, I fully agree, I posted the same scenarios over a year ago, with the same magical disconnect times.

Always around the 6 minute marker.

That should be a good enough clue for Mikrotik to sort it out, bla bla bla, All these posts to try this and that setting.

Makes no difference what so ever!.

There are hundreds of us out there with the same issue, and many of us that report the same period of time disconnects (approx 6 minutes).

How can it be anything related to a setting requirement, all of us users with same issues, have varying number of stations connected to an Ap, at varying signal levels, with varying background interference.

I have 1 station connected to an AP at -77 (signal) and they have had this problem for over a year, thank god they dont use the phone and by putting the AP frequency in the scan list the disconnect is a fraction of a second.

Now I see that the neighbour to where my tower is placed has started to get the same problem, and he lives 100 metres from the tower.. For years his connection was as solid as a rock, now he suffers the same as the other client.

OOO and BTW, port flapping still exists on 5.4.

Did it not occur to anyone that these issues developped after the introduction of the tdma option in the new ROS?
Maybe the new software also makes radio more sensitive and does pick up interference from other sources more easy then before?
Imho the issue is all to do with interference.

I had same problems in my all 5Ghz network (all 20mhz channels in use!) which does make a difference compared to 2,4Ghz due the better channel separation.

What did the trick for me?
- set ´connect-to´ list in CPE and make two rules. One to connect to AP mac, the second to AP SSID.
- set ´access-listñ in AP and mention only the CPE's allowed to connect.
- Both AP and CPE have ´default auth.´ disabled.
- set 10Mhz channel width. Although max. throughput might be halved, signal strenthgs are slightly better and thus radio links improves. As long as conn. rate is sufficiant to satisfy CPE traffic demand I have no problem. (24Mb conn. rate guarantees 10-12Mb data througput, which is plenty for 4Mb assigned clients, even for 8Mb assigned client!)
- set conn. rates on AP to only 2 or 3 rates. 6Mb for basic handshaking etc. and one or 2 that all connected CPE's can maintain without dropping signal for that rate below -73
- Any CPE with worse signal than -80 is to be considered ´bad´ anyway. Try to get better than -70. If not possible, use better antenna.
- Set the AP frequency in the wireless ´Scan List´. This way CPE only works on this frequency.
- Set Adaptive Noise Immunty in both AP and CPE accordingly.
- Use NV2 with encryption.
- Upgrade to ros 5.4. Running on my 220+ CPE network it came without any hickups or issues. Very stable version!

All these settings helped me getting rid of the issue.
I also set a new policy on my network; No more two radio's in same band on one board. And if a CPE radio has to work in a plastic housing, spraypaint the housing (NOT in front of the antenna!) with a metal paint. It helps keeping foreing signals away from the antenna connector. I did a test and saw 1-2dB diffence! This is rougly 25% less singal!
All little bits help!

After some months struggling my whole network is free of any of the dissconnects I was suffering from. Even close adjacent channels are not giving problems any more.

I don't think it can be pointed to what setting is actually making the difference. Imho it is the combination of all settings.
I call it ´hardening´ my network agains interferences.
After all, reciever in CPE has to make several decisions on what to do with all kind of packages arriving with different frequencies. So tell him to focus as much as possible to only pick these it shoudl use....

One reason why I think the new ROS versions are more sensible for other signals:
I had two CPE running 4.xx version and associated to AP. Signals where strong due the short distance to AP. (signals at CPE recieved fm AP in the -40 range, distance 150 to 200mtrs).
Now I started to upgrade my network to NV2 able wireless packages. I found that these two (retrospective conclusions) units performed very poor. Also many disconnects etc. I replaced these CPE with other units but the problem persisted. Very low signal strengths, -80 to -90! While I could almost throw a stone to the AP!!!
Than I set the ´Scan List´ parameter in the CPE to make it to listen to the AP frequency. BANG, straight away my good signals were back and the dissconnects stopped!
After switching this setting a couple of times on and off and watching in the wireless status field I found that the CPE with Scan List disabled, was connecting to one of the adjacent frequencies (next down or up 20Mhz channel of AP). Off course this frequency was much weaker than the main one.
If I ran a wireless ´scan´ while the Scan List was disabled, in fact I see three frequencies coming from AP's mac address all carrying same SSID.
Why now rb decides to pick one of the weak channels and not the strong centre one is not clear to me.
But anyway, setting ´Scan List´ to the right (´centre´) frequency solved the issue.
This problem did never exist on units running post NV2 packages.

Hence my remark in the first sentence of this topic.
One of my conclusion is also that due the freq. range in the 2.4Ghz band it will be much harder to stay out of interference issues than in the 5Ghz band. Before this might not have been such an issue. But when software is now ´better´, it picks up more ´problems´.
It is like your new cabriolet car gives you the problem with your ´toupet´ blowing off your head. On your bicycle you never had that issue. But that is not because the car is now worse. It is only that the new car make it possible to sense experiances you could never before sense at all!

[and btw, all units that had the port flapping issue on ros 5.1 and 5.1 have no more ´flapping ports´ after the upgrade to 5.4.
I can't find a single unit on my network where the log shows any more port ´flaps´...]

Well ...

What mades me post here, despite being observing this message (no beacons received) from months and believing that this belongs to an old setup which has a OEM only B AR5211 based AP on 2.4 + R52Hn on 2.4 too as client was ... I suspected of 5211 spurs, etc.

This setup is 300m from an AP with a 17dBi sector antenna, Only G on channel 13. The AP was on channel 1 + vertical 12dBi sector and the R52Hn client on a 20dBi grid, horizontal.

Ok, pigtails, bla bla bla, the Belden cables I use as jumpers are dual-braid anyway.

Then last week the old WRAP1C was retired after 3 years, on its place there is now a RB411AR (old fashion, UFL).

I swapped the cards, a R52n as AP and the built in as client. Same antennas plus a vertical omni and R52n using both chains as I've been trying to solve some multi-beam needs.

Since I boot it up there was not a single message ... more than a week stable.

In this meantime, I am preparing another 411AR to another place, another WRAP needs to be retired, mainly after V5.XX where X86 versions on such weak CPU boards was causing some 100% peaks on CPU (mostly management related).

This 411AR was deployed at my back yard, 25dBi grid, to the same AP were the 1st 411AR is connected.

As the new place is a challenge ... lots of trees close to AP & client, a lake in the middle, a bunch of propagation tricks, I decided to use the R52Hn with 2 antennas (2 x 25dBi grids), sort of spatial diversity, to improve this PTP link.

What a surprize! Durying the tests (ongoing yet), this 411AR started exibiting no beacons received 6 ... 10 times a day. How? There's not any other 802.11 device around, I'm isolated at countryside, trees all around, and 200m between R52Hn client and R52n AP!

Ok, multipath, group delay because the leaves in between etc. But why the first AP does not have the same problem and is working for more than a week without a single drop?

I suspected of the R52Hn client, replaced it by a R52nM. Both have the same chipsets btw.

Same thing, no beacons received.

Then I swapped cards functions: R52XX as AP, built in as client. Bingo! No more disconnections.

Short (too late) story: I think there's some issue with 9220 code/driver. With 40dB SNR, CCQ above 85 (95 ... 100 most of the time) and no more than 2Mbps loading there is no reason to not receive 100ms cycle beacons.

I described other setups (e.g. SR2 AP x R52Hn client than keeps connected for days without a single drop etc).

I'll build a matrix ... card types x error messages.

And - btw - UBNT clients (nano2, nano2 M, bullet2) that are more exposed to interference than R52XX clients keep connected for days.

Regards;

Rudy, Mramos, thanks both for input,, but dont want to drift too far off thread.

I want to stay on thread regarding the period of disconnect, and besides I would like to know WHY.

The common disconnect time is around 6mins 52 seconds, or a multiple thereof. And if you look at the posts of others, you will see that the disconnect period is more or less the same.

In the following data, you can see clearly the periods, and bear in mind that these are during the middle of the night, finally finishing off with a single "port flap" on version 5.4!!

I have taken a lot of time to edit the log of my mac and its channel and to colourise some fields to make it clearer to understand, I spend a few minutes editing the text, I have not edited all the relevant data, I just havent got the time.. But its clear from the first page that I edited, that the pattern of disconnects remains the same..

So what is it in the firmware that is relevant to 412 seconds! or there abouts!!




MMM MMM KKK TTTTTTTTTTT KKK
MMMM MMMM KKK TTTTTTTTTTT KKK
MMM MMMM MMM III KKK KKK RRRRRR OOOOOO TTT III KKK KKK
MMM MM MMM III KKKKK RRR RRR OOO OOO TTT III KKKKK
MMM MMM III KKK KKK RRRRRR OOO OOO TTT III KKK KKK
MMM MMM III KKK KKK RRR RRR OOOOOO TTT III KKK KKK

MikroTik RouterOS 5.4 (c) 1999-2011 http://www.mikrotik.com/




(87 messages not shown)
jan/02/1970 00:00:18 system,error,critical router rebooted without proper shutdo
wn, probably power outage
jan/02/1970 00:00:18 system,error,critical router rebooted without proper shutdo
wn, probably power outage
jan/02/1970 00:00:18 system,error,critical router rebooted without proper shutdo
wn, probably power outage
jan/02/1970 00:00:18 system,error,critical router rebooted without proper shutdo
wn, probably power outage

jun/05 02:34:59 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 02:35:11 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 02:42:03 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 02:42:06 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 02:42:18 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 02:49:10 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 02:49:13 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 02:49:25 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 02:56:17 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 02:56:21 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 02:56:33 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 03:10:31 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 03:10:35 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 03:10:47 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 03:17:39 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 03:17:43 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 03:17:55 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 03:39:00 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 03:39:03 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 03:39:16 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 03:46:08 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 03:46:11 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 03:46:23 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 03:53:15 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 03:53:18 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 03:53:30 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 04:00:23 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 04:00:26 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 04:00:38 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 04:07:30 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 04:07:33 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 04:07:45 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 04:21:45 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 04:21:48 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 04:22:00 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 04:28:52 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 04:28:55 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 04:29:07 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 04:36:00 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 04:36:03 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 04:36:15 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 04:43:07 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 04:43:10 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 04:43:22 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 04:50:16 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 04:50:19 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 04:50:31 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 04:57:22 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 04:57:25 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 04:57:37 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 05:18:43 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 05:18:47 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 05:18:59 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 05:25:50 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 05:25:53 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 05:26:05 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 05:32:55 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 05:32:58 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 05:33:10 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on24XX, SSID WWS1
jun/05 05:47:05 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 05:47:08 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 05:47:20 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 05:54:10 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 05:54:13 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 05:54:25 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 06:01:15 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 06:01:18 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 06:01:30 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 06:22:29 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 06:22:32 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 06:22:45 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 06:29:34 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 06:29:37 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 06:29:50 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 06:36:38 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 06:36:41 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 06:36:53 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 06:43:42 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 06:43:45 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 06:43:57 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 06:50:45 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 06:50:49 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 06:51:01 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 07:04:54 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 07:04:57 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 07:05:09 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 07:11:57 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 07:12:00 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 07:12:12 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 07:19:01 wireless,info 00:15:6D:XX:XX:XX@wlan1: lost connection, no beacons received
jun/05 07:19:04 wireless,info 00:15:6D:XX:XX:XX@wlan1: failed to connect, on 24XX, association timeout
jun/05 07:19:16 wireless,info 00:15:6D:XX:XX:XX@wlan1 established connection on 24XX, SSID WWS1
jun/05 07:21:28 interface,info ether1 link down
jun/05 07:21:56 interface,info ether1 link up (speed 100M, full duplex)

This magical 6 or 8 minutes "lost connection, no beacons received" is somewhat better when I changed client to mode=station instead of mode=station-bridge (faster reconnect).
I have to change WiFi cards probably to match each other to avoid this problem completely.