Randomly disabling Wi-Fi clients?

Question

network hardware

Hello. There is an RB Groove A-52HPn with an AX-2411R Omnidirectional Antenna. Installed at a height of about 10 meters in an almost open field a few kilometers from the city (cottage village), there is practically no interference (if necessary, I can do a frequency analysis).
Various clients (routers, laptops, tablets, etc.) connect to this Mikrotik via Wi-Fi, and their connection periodically breaks at the same time. Then the connection appears, then breaks again, and so on. Moreover, the connection can work stably for a day or more, and then suddenly and without any administrator intervention or external reasons, switch back to the connect-disconnect mode.
Mikrotik settings are elementary, authorization of everyone in a row without a password and simply transfer information to the LAN in bridge mode.
I would assume that this is a malfunction of this particular Mikrotik, but at some distance from it (about a kilometer) exactly the same Mikrotik is installed (already powered from a completely different line), which is completely configured in the same way (except for the frequency of the wireless channel, the name of the wireless network and IP -addresses), with which similar garbage is being created. set [ find default-name=wlan1 ] band=2ghz-b/g basic-rates-a/g=9Mbps \ basic-rates-b="" disabled=no frequency=2422 hw-protection-mode=rts-cts \ hw-retries=15 l2mtu=2290 mode=ap-bridge periodic-calibration-interval=10 \ radio-name=AlexNet-1 rate-set=configured ssid=AlexNet-1 \
It can be seen from the logs that there is a constant loss of connection, but at the same time, the client signal is not so low, from -55 to -80 dB.
Log and settings attached below.
SYSTEM
> export
# dec/10/2015 10:58:20 by RouterOS 6.33.3
# software id = HEG4-ENPB
#
/interface bridge
add l2mtu=1600 name=bridge1
/interface wireless
supported-rates-a/g=9Mbps,12Mbps ,18Mbps,24Mbps,36Mbps supported-rates-b="" \
tx-power=20 tx-power-mode=all-rates-fixed wireless-protocol=802.11
/interface wireless nstreme
set wlan1 enable-polling=no
/interface vlan
add interface=ether1 l2mtu=1596 name=vlan10 vlan-id=
/ip hotspot user profile
set [ find default=yes ] idle-timeout=none keepalive
mac-cookie-timeout=3d
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=wlan1
/ip address
add address=192.168.0.11/24 interface=vlan10 network
/ip route
add distance=1 gateway=192.168.0.1
/ip upnp
set allow-disable-external -interface=no
/system clock manual
set time-zone=+03:00
/system leds
set 0 interface=wlan1
/system logging
add topics=!packet
/system ntp client
set enabled=yes mode=unicast primary-ntp=62.76. 96.4
/system routerboard settings
set cpu-frequency=600MHz
>
===========================
LOG
08:18 :44 route,debug,event status=UP,RUNNING
08:18:44 route,debug,event mtu=1500
08:18:44 route,debug,calc Begin calculation
08:18:44 route,debug, event Link up
08:18:44 route,debug,event interface=wlan1
08:18:44 route,debug,event Update
08:18:44 route,debug,event interface=wlan1
08:18:44 route,debug,calc end calculation
08:19:07 wireless,info E8:DE:27: 9D:3B:[email protected]: disconnected, extensive data loss
08:19:10 route,debug,event Interface change
08:19:10 route,debug,event interface=wlan1
08:19:10 route,debug,event status= UP
08:19:10 route,debug,event mtu=1500
08:19:10 route,debug,calc Begin calculation
08:19:10 route,debug,event Link down
08:19:10 route,debug,event interface= wlan1
08:19:10 route,debug,event Update
08:19:10 route,debug,event interface= wlan1
08:19:10 route,debug,calc End calculation
08:23:52 wireless,info wlan1: data from unknown device 64:70:02:F7:F6:7F, sent dea
uth
08:23:54 wireless,debug wlan1: 64:70:02:F7:F6:7F attempts to associate
08:23:54 wireless,debug wlan1: 64:70:02:F7:F6:7F not in local ACL, by default acce
pt
08:23:54 wireless,info 64:70:02:F7:F6:[email protected]: connected
08:23:54 route,debug ,event Interface change
08:23:54 route,debug,event interface=wlan1
08:23:54 route,debug,event status=UP,RUNNING
08:23:54 route,debug,event mtu=1500
08:23:55 route,debug,calc Begin calculation
08:23:55 route,debug,event Link up
08:23:55 route,debug,event interface=wlan1
08:23:55 route,debug,event Update
08:23:55 route,debug,event interface=wlan1
08 :23:55 route,debug,calc End calculation
08:23:55 wireless,info wlan1: data from unknown device E8:DE:27:9D:3B:E1, sent dea
uth
08:23:58 wireless,debug wlan1: E8:DE:27:9D:3B:E1 attempts to associate
08:23:58 wireless,debug wlan1: E8:DE:27:9D:3B:E1 not in local ACL, by default acce
pt
08:23:58 wireless ,info E8:DE:27:9D:3B:[email protected]: connected
08:24:18 wireless,info 64:70:02:F7:F6:[email protected]: disconnected, extensive data loss
08:24:21 wireless ,info E8:DE:27:9D:3B:[email protected]: disconnected, extensive data loss
08:24:24 route,debug,event Interface change
08:24:24 route,debug,event interface=wlan1
08:24:24 route,debug,event status=UP
08:24:24 route,debug,event mtu= 1500
08:24:24 route,debug,calc Begin calculation
08:24:24 route,debug,event Link down
08:24:24 route,debug,event interface=wlan1
08:24:24 route,debug,event Update
08 :24:24 route,debug,event interface=wlan1
08:24:24 route,debug,calc End calculation
08:25:44 wireless,info wlan1: data from unknown device E8:DE:27:9D:3B:E1, sent dea
uth
08:25:46 wireless,debug wlan1: E8:DE:27:9D:3B:E1 attempts to associate
08:25:46 wireless,debug wlan1: E8:DE:27:9D:3B:E1 not in local ACL, by default
accept
08:25:46 wireless,info E8:DE:27:9D:3B:[email protected]: connected
08:25:46 route,debug,event Interface change
08:25:46 route,debug,event interface=wlan1
08: 25:46 route,debug,event status=UP,RUNNING
08:25:46 route,debug,event mtu=1500
08:25:46 route,debug,calc Begin calculation
08:25:46 route,debug,event Link up
08:25:46 route,debug,event interface=wlan1
08:25:46 route,debug,event Update
08:25:46 route,debug,event interface=wlan1
08:25:46 route,debug,calc End calculation
08 :26:09 wireless,info E8:DE:27:9D:3B:[email protected]: disconnected, extensive data loss
08:26:12 route,debug,event Interface change
08:26:12 route,debug,event interface= wlan1
08:26:12 route,debug,event status=UP
08:26:12 route,debug,event mtu =1500
08:26:13 route,debug,calc Begin calculation
08:26:13 route,debug,event Link down
08:26:13 route,debug,event interface=wlan1
08:26:13 route,debug,event Update
08:26:13 route,debug,event interface=wlan1
08:26:13 route,debug,calc End calculation
08:27:44 wireless,info wlan1: data from unknown device E8:DE:27:9D:3B:E1 , sent dea
uth
08:27:47 wireless,debug wlan1: E8:DE:27:9D:3B:E1 attempts to associate
08:27:47 wireless,debug wlan1: E8:DE:27:9D:3B:E1 not in local ACL, by default acce
pt
08:27:47 wireless,info E8:DE:27:9D:3B: [email protected]:connected
08:27:47 route,debug,event Interface change
08:27:47 route,debug,event interface=wlan1
08:27:47 route,debug,event status=UP,RUNNING
08:27:47 route,debug,event mtu=1500
08:27:47 route,debug,calc Begin calculation
08:27:47 route,debug,event Link up
08:27:47 route,debug,event interface=wlan1
08:27:47 route,debug,event Update
08:27:47 route,debug,event interface=wlan1
08:27:47 route,debug,calc End calculation
08:27:52 wireless,info wlan1: data from unknown device 64:70:02:F7:F6: 7F, sent dea
uth
08:28:10 wireless,info E8:DE:27:9D:3B:[email protected]: disconnected, extensive data loss
08:28:13 route,debug,event Interface change
08:28:13 route,debug,event interface=wlan1
08:28:13 route,debug,event status=UP
08:28:13 route,debug,event mtu=1500 pt 08:29:42 wireless,info 64:70:02:F7:F6:[email protected]: connected 08:29:42 route,debug,event Interface change
08:28:14 route,debug,calc Begin calculation
08:28:14 route,debug,event Link down
08:28:14 route,debug,event interface=wlan1
08:28:14 route,debug,event Update
08: 28:14 route,debug,event interface=wlan1
08:28:14 route,debug,calc End calculation
08:29:42 wireless,debug wlan1: 64:70:02:F7:F6:7F attempts to associate
08:29 :42 wireless,debug wlan1: 64:70:02:F7:F6:7F not in local ACL, by default acce 08:29:42 route,debug,event interface=wlan1 08:29:42 route,debug,event status =UP,RUNNING 08:29:42 route,debug,event mtu=1500 08:29:42 route,debug,calc Begin calculation 08:29:42 route,debug,event Link up 08:29:42 route,debug, event interface=wlan1
08:29:42 route,debug,event Update
08:29:42 route,debug,event interface=wlan1
08:29:42 route,debug,calc End calculation
08:29:44 wireless,info wlan1: data from unknown device E8:DE:27:9D:3B:E1, sent dea
uth 08:29:48 wireless,info E8:DE:27:9D:3B:[email protected]: connected 08:30:05 wireless,info 64:70: 02:F7:F6:[email protected]: disconnected, extensive data loss 08:30:11 wireless,info E8:DE:27:9D:3B:[email protected]: disconnected, extensive data loss 08:30:14 route,debug ,event Interface change 08:30:14 route,debug,event interface=wlan1 08:30:14 route,debug,event status=UP 08:30:14 route,debug,event mtu=1500 08:30:14 route, debug,calc Begin calculation
08:29:48 wireless, debug wlan1: E8:DE:27:9D:3B:E1 attempts to associate
08:29:48 wireless,debug wlan1: E8:DE:27:9D:3B:E1 not in local ACL, by default acce
pt
08:30:14 route,debug,event Link down
08:30:14 route,debug,event interface=wlan1
08:30:14 route,debug,event Update
08:30:14 route,debug,event interface=wlan1
08:30:14 route,debug,calc End calculation
08:30:35 ntp,debug Wait for 900 seconds before sending next message
08:30:35 ntp,debug gradually adjust by -1ca8fa
08:31:44 wireless,info wlan1: data from unknown device E8:DE:27:9D :3B:E1, sent dea
uth
>

Answer 1

We should not forget that wifi is a collision network. If clients start broadcasting at the same time, it does not lead to anything good. The hidden node problem is also common. The solution is to use polling or tdma protocols. But Mikrotik has its own, proprietary. If you have a lot of clients in the village, it is better for each of them to install something like SXT lite2 or lite5 in bridge mode, depending on the frequency used on the groove. Next, each client at home has a router with his own Wi-Fi., With such a topology (point-to-multipoint), configure either the NStreme or NV2 protocol. Each of them has advantages and disadvantages. But when using them, it is the point that controls the transfer of data from clients, not allowing them to broadcast at the same time. Yes, the cost is more than just sticking one point in a huge area, hit it with 20 dBm + another 6 dBi antenna and fry flying jackdaws with it. But it will work. If transparency between clients is needed, it will not be much more difficult to set it up.

Answer 2

You have all sorts of "unknown device" appearing there (
I suppose they break you, sir(
Run the www.acrylicwifi.com acrylic scanner under wine.
Without any logs, a graphical representation by channels / by time with an estimate of the signal level and so on ...
In principle, to capture x/neck it is enough to break the connection with the client
once.This works mdk3, Athrophy (?), and one more software (I don’t remember offhand).Alternatively
, you have wps enabled with association blocking after N unsuccessful pins.For its (access point) reset (reboot) and these softins are applied.In theory, Mikrotik should not have behaved like this, but ... kagritsa xs (
Try to make an open guest subnet with which give only wan.
Simply disabling wps will not do anything, in the sense that your clients have no access) through a permanently rebooting router - just a broker))) will bring down etc. in place (
Do not be greedy) In general, this is mmm ... sometimes, shorter. Especially when other people's APs jam / crush the signal of someone's working (
pisi
oops (I
re-read it and saw "without a password." The
question is not in the password field filled with characters or an empty field, but in the selected encryption.
True, I won’t say if Mikrotik will miss the empty field password for accessing the network, other routers with an empty password came across only in the admin panel)

Answer 3

Thanks for the answer!
I don't quite understand what kind of encryption you are talking about. There is no password, no encryption, all Mikrotik settings are visible in the topic header.
The main difficulty in diagnosing the causes of disconnects is that the problem occurs spontaneously. Periodically, and even often, everything works as it should. That is, clients can hold out without a single disconnection for more than a day, and then, for example, within two to three hours, they start disconnecting / connecting without exception. Then, on the 500th connection time, Mikrotik suddenly connects everyone and again everything works as it should. It's kind of a nightmare :(

Answer 4

Update firmware to 6.35