hello everyone,
We use Mikrotik products since three years and from some months we have serious problems with the wireless connections.
we have a lot of messages of "extensive data loss".
For example a link (18 Km point-to-point link) has connected to -69/-71.
This is only an example, becouse we have a lot of similar links dislocated in our territory whit the same problems, and not only in the backhauling but also in the access point, clients disconnected with "extensive data loss".
The routerboard used is a rb411ah, the radio is a R52 (Nstreme protocoll is enabled), the antenna a 28dB solid disk.
We have
changed the frequency, but the result is the same, the link disconnected with “extensive data loss”.

below messages wich are visualised in the logs:

bridge side, configured in mode=bridge:

10:45:55 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
10:45:56 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
10:45:56 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
10:46:07 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
10:46:07 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
10:46:07 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
10:53:33 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
10:53:33 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
10:53:33 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
10:53:33 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
10:53:34 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
10:53:34 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
10:53:45 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
10:53:45 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
10:53:45 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
10:55:53 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
10:55:53 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
10:55:53 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
10:55:53 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
10:55:54 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
10:56:05 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
10:56:05 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
10:56:05 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
11:22:14 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
11:22:14 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
11:22:14 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
11:22:14 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
11:22:14 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
12:06:20 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:06:20 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
12:06:20 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
12:06:20 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:06:20 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
12:09:33 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:09:33 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
12:09:33 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
12:09:33 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:09:34 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:09:45 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:09:45 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:09:45 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
12:09:58 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:09:58 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
12:09:58 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
12:09:58 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:10:00 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:10:13 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:10:13 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:10:13 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
12:11:02 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:11:02 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
12:11:02 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
12:11:02 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:11:03 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:11:03 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:11:14 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:11:14 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:11:14 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
12:17:34 system,info,account user admin logged in from 00:0C:42:2F:3A:E9 via mac -telnet
12:21:25 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:21:25 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
12:21:25 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
12:21:25 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:21:25 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
12:27:43 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:27:43 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
12:27:43 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
12:27:43 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:27:44 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:27:44 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:27:55 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:27:55 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:27:55 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
12:30:23 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:30:23 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
12:30:23 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
12:30:23 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:30:24 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:30:24 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:30:35 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:30:35 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:30:35 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
12:33:32 system,info,account user admin logged out from 00:0C:42:2F:3A:E9 via ma c-telnet
12:49:47 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:49:47 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
12:49:47 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
12:49:47 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:49:47 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS
12:52:47 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:52:47 wireless,info 00:0C:42:2B:50:79@wlan1: reassociating
12:52:47 wireless,info 00:0C:42:2B:50:79@wlan1: disconnected, ok
12:52:48 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:52:48 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:52:48 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:52:48 wireless,info wlan1: data from unknown device 00:0C:42:2B:50:79, sent d eauth
12:52:59 wireless,debug wlan1: 00:0C:42:2B:50:79 attempts to associate
12:52:59 wireless,debug wlan1: 00:0C:42:2B:50:79 in local ACL, accept
12:52:59 wireless,info 00:0C:42:2B:50:79@wlan1: connected, wants WDS


station side, configured in mode=station-wds:

feb/16 07:07:51 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5290, SSID seneghe
feb/16 07:08:00 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, received deauth: unspecified (1)
feb/16 07:08:01 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 08:57:32 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 08:57:34 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 08:57:45 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 09:19:08 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 09:19:10 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 09:19:21 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 12:02:04 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 12:02:06 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 12:02:17 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 12:02:19 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 12:02:20 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 12:02:21 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 12:02:22 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 12:02:26 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 12:02:27 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 12:02:38 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 12:03:46 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 12:03:48 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 12:03:59 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 12:58:57 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 12:58:59 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 12:59:10 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 12:59:11 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 12:59:14 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 12:59:27 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 14:38:54 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 14:38:56 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 14:39:07 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 14:58:19 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 14:58:22 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 14:58:35 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 15:08:45 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 15:08:48 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 15:09:01 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 15:10:12 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 15:10:14 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 15:10:25 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 18:58:21 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 18:58:22 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 21:15:39 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 21:15:40 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 21:15:42 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 21:15:44 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 21:15:55 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 21:18:26 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 21:18:28 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 21:18:39 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 21:18:41 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 21:18:43 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 21:18:54 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 21:19:03 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 21:19:05 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 21:19:16 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 21:20:41 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 21:20:44 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 21:20:57 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 21:21:32 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 21:21:34 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 21:21:45 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 21:43:01 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 21:43:03 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 21:43:14 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 21:50:40 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 21:50:42 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 21:50:53 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 21:53:00 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 21:53:02 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 21:53:13 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 22:19:21 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 22:19:22 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 23:03:27 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 23:03:28 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 23:06:40 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 23:06:42 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 23:06:53 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 23:07:05 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 23:07:08 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 23:07:21 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 23:08:08 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 23:08:10 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 23:08:21 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 23:16:02 system,info,account user admin logged in from 00:0C:42:31:3C:47 via mac-telnet
feb/16 23:18:32 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 23:18:33 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 23:24:50 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 23:24:52 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 23:25:03 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 23:27:29 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 23:27:31 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)
feb/16 23:27:42 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 23:30:13 system,info,account user admin logged out from 00:0C:42:31:3C:47 via mac-telnet
feb/16 23:46:54 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 23:46:55 wireless,info 00:0C:42:31:3C:47@wlan1 established connection on 5210, SSID seneghe
feb/16 23:49:54 wireless,info 00:0C:42:31:3C:47@wlan1: lost connection, extensive data loss
feb/16 23:49:56 wireless,info 00:0C:42:31:3C:47@wlan1: failed to connect, on 5210, received deauth: class 2 frame received (6)

I think that the interferencies may be a cause of the problem, but only in some cases not all.
is not possible that wherever we have these problems, especially with signs of -71 (always -69/-71).
cerca

someone has found the same problem?
someone have the same problem?
The Mikrotik staff have an idea to solve this problems?

Thanks for attention and excuse me for my english.

Cordial greetings,

Francesco

Try downgrade RouterOS on both side on some 3.16 version and check again.

Try downgrade RouterOS on both side on some 3.16 version and check again.

hello aaa
ok, i try to downgrade the routerboars package to 3.16.
i will posted the results of downgrade as soon as tested.

thanks for the answer.

PS: the package that actually installed is 3.27 with wireless-test-package.

Cordial greetings,
Francesco

Try downgrade RouterOS on both side on some 3.16 version and check again.

Hi,
Errata corrige,
the package installed is the 3.10.
i don't have found the 3.16 release in mikrotik downloads.
I have found only 3.13 compatible whit rb411 series.

Ok, put latest RouterOS on both side and test in ap-bridge /station mode if problem persist check RF installation (RF cables, pigtails, water in connectors, clear LOS ) and frequency settings.

Ok, put latest RouterOS on both side and test in ap-bridge /station mode if problem persist check RF installation (RF cables, pigtails, water in connectors, clear LOS ) and frequency settings.

We have installed the 3.27 package and wireless-test-package, but there are same problems.
We had checked the RF installation and there was not problems.
The strange thing is that the signals occasionally go from -69 to -87 and vice versa, in this time the link goes to extensive data loss for 1 or 2 seconds.
If runs a ping to the remote routerboard to verify the connection, the logs shows a singol ping timeout while link goes down.

Hello Flynter
I too have the same problem with packet loss and continue disconnections.
At this point I believe that the only solution is to create a
identical link (same locations, same hardware, same release software,
same all....) to the existing one and see if they behave similarly,
if the disconnects do not occur simultaneously on the two links
then I doubt that really is a problem of noise.
Mikrotik then that should give us a definitive solution do not you
think?

Hello Flynter
I too have the same problem with packet loss and continue disconnections.
At this point I believe that the only solution is to create a
identical link (same locations, same hardware, same release software,
same all....) to the existing one and see if they behave similarly,
if the disconnects do not occur simultaneously on the two links
then I doubt that really is a problem of noise.
Mikrotik then that should give us a definitive solution do not you
think?

Hello Mark66,
i think that the problems could be caused same interference, but only in one our location, not in all.
Now we are waiting to measure the area, where we have installed the links, whit a spectroscope.
Probably in next week.
for others links i hope that Mikrotik staff can help us to resolve our problems.

cordial greetings,
Francesco

Did any of you eventually find out anything from all your research on the above subject? How did you solve the problems of the disconnection, post it here for others to benefit from it pls.