Mikrotik Metal 2.4 wihtout wireless

Hardware MikroTik hardware general
21

So, what is the MikroTik team official respond at this topic?
The fact is: MikroTik Metal 2,4GHz working as AP - disconnects radio clients.
The MikroTik Groove 2,4Ghz at he same place with the same config - working good.
Conclusion: all MikroTik Metal 2,4GHz have hardware problem that is VERY frustrating and makes it unusable as Access Point!

22

I am requesting to MikroTik for any real action.

23

In addition to the reboot log I posted above, I’m noticing that the unit will set itself to the 250Mhz cpu speed setting. I assume it’ sdoing this because of a failed boot or something simliar during a kernel failure/reboot and stepping down the freq.

I dont’ know that i would have caught it except with RANcID runing each hour to pull the config and diff it against the previous retrieval. it shows up every few days like this:

  set enabled=yes mode=unicast primary-ntp=10.1.1.10 secondary-ntp=10.1.1.110
+ /system routerboard settings
+ set cpu-frequency=250MHz
  /system scheduler
24

I too had this problem with the 2.4GHz Metals stopping transmitting. I am told v6.10 has a fix in it for this problem. Try it out.

25

i tried it a few days ago as you suggested. 2 Metal2.4s and an SXT, things are definitely improved to just under 1 reboot per day… better than it was but not quite what I’d like to see. I still see the 250Mhz CPU setting kicking in/out via my RANCID config backup change notifications

it seems now the main reason for reboots is the wireless client count reboot script.

Mar  1 21:07:22 10.4.9.52 metal2 router rebooted
Mar  1 23:52:30 10.4.9.52 metal2  still 0 associated clients, router reboot
Mar  1 15:53:22 10.4.9.52 metal2 router rebooted
Mar  2 14:29:30 10.4.9.52 metal2  still 0 associated clients, router reboot
Mar  2 14:30:22 10.4.9.52 metal2 router rebooted
Mar  3 18:18:40 10.4.9.52 metal2 System rebooted because of kernel failure
Mar  3 18:18:40 10.4.9.52 metal2 router was rebooted without proper shutdown
Mar  5 20:59:30 10.4.9.52 metal2  still 0 associated clients, router reboot
Mar  5 21:00:24 10.4.9.52 metal2 router rebooted
Mar  6 16:43:41 10.4.9.52 metal2 System rebooted because of kernel failure
Mar  6 16:43:41 10.4.9.52 metal2 router was rebooted without proper shutdown
26

I am in same problem.

27

Same problem here, Metal 2.4, version 6.10, up to 3 wireless freezes per day, only reboot to bring back.