Hmm it's likely that it's on the same array, did you have lots of disconnections before?

Those signals look on the low side.

Yes, but only two clients on WAP60x3. 4 days uptime and no disconnect with beta48

Do you know whether they're connected to the same internal sector? How far are they apart in the 180 arc?

try 6.48beta48. Now it works for us. But we have only 2 clients...

Interesting, can you confirm you have a 60x3 AP? what are the link down counters showing since you installed beta48?

@Mikrotik

Seems as you can't get this working correctly, is it possible to disconnect the two side sector arrays and run it with a single as the wAP60G AP?

Latest lockup and reboot showed this: jul/22/2020 22:26:52 system,error,critical kernel failure in previous boot

I have removed 4 units now - is there an explanation for the lock up's yet??

For me 6.45.3 same as ROS.

Yes see here: viewtopic.php?t=151046

I can also see from a number of 4011's I've got out in the wild that cpu0 get hammered all the time and the other 3 do very very little :/

# aug/22/2019 17:27:49 by RouterOS 6.45.3 # software id = FDK9-ISF2 # # model = RB4011iGS+ # serial number = AAAF0A1A68A6 /interface bridge add name=********inn-bridge add name=loopback /interface ethernet set [ find default-name=ether1 ] comment=\ set [ find default-name=ether2 ] comment= set [ fin...

Thanks peeps, will post config as soon as I get back to the office.

Graphs are from Librenms, yes to a single IPSEC tunnel back to our NOC, very little traffic. No VLANs.

Who says I haven't sent the sup out info in already regarding the crash? That was merely one part of the issue and informing the community helps if anyone experiences the same in the future. The second part which is open to the community, including the Tik bods, was the question about normal operati...

Is the following normal operation for the 4011? It is doing basic routing, simple queues and firewall/nat.

You can see from the first graph on Friday all went to hell, it was barely accessible via MAC-telnet but managed to reboot.