%interface is a lot less useable than a dropdown (especially for dynamic / non-trivial interface names)
Winbox thrives because of its "WYSWYG" design, almost user-proof, and self-explanatory
ditching that design language, and requiring previous knowledge of the arcane incantations of %@ syntax is a mistake,and a lack of indication on the GUI that such a thing even exists will frustrate a lot of people
by that point, it's just easier to use the CLI
CLI FTW 
Agreed, but Winbox is a big selling point for Mikrotik.
Messing with the most basic diagnostic function, frustrating the userbase,can prove to be a bad move
There was the same problem with the ârouting filtersâ which in v7 became a âlanguageâ that you had to enter manually, while in v6 the same filters could be entered using a GUI.
In the end, there was a âfilter wizardâ built in that would generate (but not edit) a new-style filter from panels similar to the old-style GUI.
Maybe similarly some smartness could be added to WinBox to allow entering an address field and select VRF and interface from dropdown lists that dynamically appear when entering the address?
I still donât get why I have to create a VRF to be able to ping using a specific table. In v6 I could just create a route with a routing mark and specify that in the ping or traceroute windows. In v7, I have to first creating an extra routing table, THEN create a new VRF, THEN create my route with routing mark and only THEN I can ping. Makes no sense.
Well, you can still specify the source-address of the ping, which would usually select the routing table via the routing rule or a mangle ruleâŚ
In fairness, WinBox4 does describe the scheme:
Now agree vrf/interface should be a drop-down in WinBox/WebFig "Advanced" tab (and essentially appended to the ping-to).
But I'm not sure how a "routing table" selector is related to ping, since that's not part of ICMP packet generation while interface/vrf do effect that. As @pc1chl suggests src-address (and dst-address/"ping-to") will be process by routing table/rules â which IMO why you're using ping to test the routing table/s.
If the %if / @vrf syntax is implemented throughout every setting, it becomes your second nature. No need to look up the syntax, no need to look for the field situated 50 fields lower. In my experience with other vendors, referring to a specific interface/vrf via something added to the address is much simpler and much more straight forward than to look up the specific way of the specific setting referring to a vrf by something more complicated like -vrf âmyVRFâ.
IMHO this is exactly the way how things should work.
Whatâs Iâm missing still is the possibility to configure multiple instances of services listening on different VRFs.
Yes, but what people do not like is that with those special characters you need to KNOW the exact name and type it, while in the old format such an interface or VRF field was a pulldown where you could select the correct one.
I suggest that WinBox be changed so that when you have an address field and you type a % or @, a dropdown magically appears at that moment where you can make a selection and the value will be copied in the field. That would be the best of all worlds.
I suggest that WinBox be changed so that when you have an address field and you type a % or @, a dropdown magically appears at that moment where you can make a selection and the value will be copied in the field.
Couldnât agree more!
Perfect solution would be to get a list when you type % or @, then if you type the next letter, the list should get filtered by what you have typed.
Iâm also running into this issue (with beta 5), once it starts (about an hour after reboot) pretty much nothing works anymore.
I wonder if previous versions of WinBox like v3.41 or 2 do the same...
As previously tested:
SSH creates the same issue.
And supout won't export items either.
So it's a no
Dear Mikrotik Team,
We are writing to bring to your attention a critical issue with BGP VPNv4 that can cause significant service disruptions when a BGP flap occurs. Despite reporting this issue almost a week ago (SUP-203163) and providing detailed support output, topology information, and a video, we have yet to receive a response. Given the severity of this issue and its impact on all RouterOS versions 7.19.x, 7.20.x, 7.21.x, and the latest nightly build 7.22_ab261, we kindly request that you prioritize this customer report and provide a timely response.
Thank you
on CCR2216 with hwl3 intra vlans traffic when the router boot on 7.21b5 the vlans doesnât report tx traffic in counters and dosnât show tx traffic in interface winbox window.
To recover the TX traffic reporting you have to disable/enable a vlan. Just a cosmetic bug
Thank you for
Can we also have the hostname? the two make a huge difference in trouble shooting.
Of course not. How would the router know that? It is not in the data that is passing by.
Well, it could resolve the name from DHCP leases (if available) and/or ARP.
It depends a bit if you have an AP or a Station, in my case I use a LHG as a station and the IP addresses flashing by in that column are from all over the place. The only way to resolve them to hostnames would be via DNS, and that would introduce quite some DNS load, besides that it becomes less and less common to have reverse DNS.
+1 this would be super useful