+++
The same here, ROS 6.45.9. Yesterday we almost raised security alarm, because entire wireless network suddenly was down, until I discovered it was me using Winbox. Crazy!
ROS 6.44.5 … CAPSMA & WiFi killed with 3.25
I’ve noticed some CAPSMAN ACL rules removed when I used 3.25. Not all.
There is also autospout.rif file generated.
And HOTSPOT!
WinBox v3.25 (64)
first my data on DNS cache disappeared… after many times, when I opened and closed the DNS window, they came back. but I see that it does a autosupout.rif file
RouterOS v6.47.2 @ hAP ac lite and old RB600A and RB493AH and RB2011UiAS-2HnD
CTRL + or CTRL - won’t work
Observation.
WinBox 3.25 removed all CAPSMAN ACL rules following the one which held Polish diacritic letter in a comment.
This particular rule persists but is cleared.
Router was not rebooted.
Maybe because i have them running on 6.46.6. I only have 4 CAPs. This is how they usualy look, from terminal, in 3.25 clicking on the Radio tab I don’t get the chance to see any of them, just the logs showing that they are joining back.
/caps-man radio> print
Flags: L - local, P - provisioned
# RADIO-MAC INTERFACE REMOTE-CAP-NAME REMOTE-CAP-IDENTITY
0 P C4:AD:34:D0:95:6E eth-rd-z3-cap3-1 CAP-C4AD34D0956C eth-rd-z3-cap3
1 P C4:AD:34:D0:95:6F eth-rd-z3-cap3-2 CAP-C4AD34D0956C eth-rd-z3-cap3
2 P C4:AD:34:D0:92:D6 eth-rd-z3-cap1-1 CAP-C4AD34D092D4 eth-rd-z3-cap1
3 P C4:AD:34:D0:92:D7 eth-rd-z3-cap1-2 CAP-C4AD34D092D4 eth-rd-z3-cap1
4 P C4:AD:34:D0:92:9A eth-rd-z3-cap2-1 CAP-C4AD34D09298 eth-rd-z3-cap2
5 P C4:AD:34:D0:92:9B eth-rd-z3-cap2-2 CAP-C4AD34D09298 eth-rd-z3-cap2
6 P C4:AD:34:D0:95:1A eth-rd-z3-cap4-1 CAP-C4AD34D09518 eth-rd-z3-cap4
7 P C4:AD:34:D0:95:1B eth-rd-z3-cap4-2 CAP-C4AD34D09518 eth-rd-z3-cap4
Maybe something in the identity/interface names causes this? beats me. They are also running in CAPsMAN forwarding mode.
I also think this version is responsible for the autosupout.rif files I’m finding in the routers after I browse through some settings without even changing anything.
We are very sorry for any inconvenience caused.
We have reproduced the problem with Hotspot and will work on a fix for that.
We also managed to reproduce the wireless issue. In order to resolve the problem, you have to run at least RouterOS v6.47. We will backport the required fix also to the upcoming long-term releases.
IMHO You shold fix WinBox not ROS ASAP as upgrade to ROS > 6.47 is not always possible
And remove Winbox 3.25 from downloads and upgrade ASAP.
After struggling for some time with firewall order issue and now with all this wireless killer bugs I am reverting back to winbox64-3.21 that seems to work the best …
Maybe it is time to introduce the same beta/stable/longterm releases schema as used in ROS to WinBox too since it is pretty important tool for most users …
WinBox and RouterOS communication is a two way street. This time RouterOS causes the problem.
Here are links to v3.24 if you want to wait for a fix for the Hotspot issue.
http://download.mikrotik.com/routeros/winbox/3.24/winbox.exe
http://download.mikrotik.com/routeros/winbox/3.24/winbox64.exe
Really?
I reported problem with ROS 6.44 + Winbox 3.25 therefore:
Winbox <3.25 is buggy and do not report errors but 3.25 does
or
3.25 has bugs and messes with configuration behind the scene
or
3.25 correctly reports ROS hidden problems
Newer WinBox versions shouldn’t break client’s routers running stable, older ROS versions, disconnecting CAPs or whatever else the current version is able to kill or mess up with.
Or atleast there should be some warning regarding this, when it encounters unsupported (anymore) ROS versions instead of the current unfortunate behaviour.
I won’t upgrade to 6.47.2 just to be able to use the latest WinBox unless there’s some serious security issue with the older ROS.
I’m skeptic about the 6.47.x versions so far to put them in production.
I do play with two routers running 7.1beta2 but those aren’t in production environment and I don’t care that much at home if my Netflix hiccups for some reason.
I’ll keep an eye for autosupouts. If I don’t encounter them anymore than this settles that WB 3.25 was the cause for those also (in 6.46.6 and 7.1beta2).
LE: now that I think of it, could this WB version be the cause for the issue I’ve posted here? http://forum.mikrotik.com/t/v7-1beta2-development-is-released/142356/1
ROS 6.45.9 is supported, this is the latest long-term version. So, while we are waiting for backporting something (we don’t know what) from stable to long-term, Winbox 3.25 should be removed from downloads and from built-in upgrade, or at least there should be two versions downloadable from MikroTik page - for ROS 4.72 and above, and for older versions.
how can we force to not follow system DPI setting?
I faced the same problem. When I downgraded to 3.24 everything works fine…
Back in the future…
+1000000% same issue with Winbox 3.25 release and 6.45.9 and hotspot active tab!! Completely disconnected ALL active hotspot users and breaks. I had to dump all users from the queue.
Not good, As I’m going to get angry phone call from this hotspot customer.
I do not see version 3.24 available to download, wtf?