no beacons

Hello.

I have setup wirless network.

Mikrotik router ------------LAN1
wlan1(mode=bridge,wds)
|
5GHz-turbo
|
wlan1(mode=bridge,wds)
Mikrotik AP
wlan2 (mode=ap_bridge), default_auth=no
|
2.4GHz b/gMode —notebook/pda
|
wlan1(station wds)
RB112CPE
ether
|
client PC

wirless network is transparently bridged so that devices connected to CPE or devices directly connected to AP are available form LAN1
all devices are in access-list
wirless clients are:

  1. Notebook with orionco GOLD wirless card (works fine)
  2. hp ipaq 2490 (works fine)
  3. RB112 CPE mode=station wds (bridged) works fine (shows status connected to ess)
  4. and 2 RB112 CPE which are not working fine.

these 2 CPE have been tested in all aviable modes - bridge, station wds, wds slave. wds-mode set to dynamic, all interfaces added to one bridge. all what can be achieved - registred coonnection for some moument

on AP I have such log:
03:35:30 wireless,info 00:0C:42:05:53:20@wlan2: connected, is AP, wants WDS
03:35:41 wireless,info 00:0C:42:05:53:20@wlan2: disconnected, no beacons
03:35:42 wireless,info wlan2: data from unknown device 00:0C:42:05:53:20, sent deauth

on CPE log auth timeout is shown.

Any ideas what could be the reason?
Distance from AP to CPE is 100 and 150 meters,all at the same height

Hey there,

We’ve also had this problem and I think I have found a solution:
If you look on your CPE equipment, it is highly likely that the “beacon interval” setting is up around 100ms. If you change this down to about 20ms it will send more beacons due to the shorter interval.
This stops the almost “time out” issue that we were getting.
Let me know how you go
Cheers

Did You mean “beacon interval” = on-fail-retry-time (time; default: 100ms) ?
Or maybe it is some other setting?
And should it be changed on AP, CPE or both sides?

I’m not sure what the equivalent is on the rOS side, in fact I’m now getting issues where RouterOS ---- RouterOS links are doing the same… But I changed the beacon interval on the CPE equipment only, and that link seems fine now! I’m going to try the on-fail-retry-time aswell

there is no equivilant on routeros side.
routeros transmits 10 beacons a second (which is 100 milliseconds)