What’s new in v3.38:
*) fixed connecting to wireless network from QuickSet when there was no password specified;
*) fixed date and time value representation in the User Manager;
*) fixed skin file reading;
If you experience version related issues, then please report them to support@mikrotik.com.
Both Winbox 32-bit and 64-bit versions are available here:
https://www.mikrotik.com/download
thank you
nice work, thx
Firewall rules lists are still ‘cut in the middle’ when first displayed. As soon as you move to another tab and go back to the previous one, the list is complete.
My experience is that:
Not a big deal but annoying since it’s been present for a couple of winbox version w/o a proper fix.
Works OK for me. Try removing your session file, that often solves winbox problems.
thank you. appreciated.
I’ve already tried, even w/o session/profile and clearing cache it is still beheaving almost in the same way (“filter”/83, “nat”/46 and “mangle”/73).
Nothing’s changed from the previoius version, I can live with that but it’s worth mentioning here not to forget.
This means that if I use winbox 3.37 and earlier, with bad skins from 7.8 onwards (barring future bugfixes), I can have full access,
instead using 3.38 the menus are hidden correctly, giving false security, but just use 3.37 and you still have full access?..
But I still cant set group key update to 12h on wave2 capsman.
I think skins are not really about security. They “hide” certain options, but when you know how you can still access them.
It is mainly intended as a helper for people who do not need certain options and are confused by the many menus and buttons.
Any chance to fix this viewtopic.php?p=938420#p938367 simple issue of not sorted Address List in DHCP static lease drop down option? Reported already many times with each new release :-(, How much time takes this fix…on or two minutes?
Never seen that. Just opened WinBox 3.37 here and connected to my main home router. Filter rules is 253 items and NAT is 168. Both showed the full list right away. I don’t have near enough Mangle rules to hit that limit.
Can you add a minimum winbox version option for the next release of ROS? We’re interested in releasing winbox access for customers (currently we only allow a heavily skinned webfig) but need to ensure that skins are honored by all connections, and so need to ensure that old versions of winbox that have problems are not allowed to connect.
It works OK here. Did you try to reproduce it without your session file for that device (temporarily move it away)?
SKINS ARE NOT FOR SECURITY
It is to hide confusing items from beginner users. maybe your novice technician needs to disable users and doesn’t want to see confusing menus. Set him up with correct winbox and tell him what button to push. You can also use it for translation, or simplification of menu names.
SKINS ARE NOT FOR SECURITY
@maisonmdsgreen
do not quote unnecessarily, and even without the slightest sense
do not write the same thing over and over again
https://forum.mikrotik.com/viewtopic.php?p=999592#p999592
OK, For the ten thousandth time, if you don’t want us to use skins for this then GIVE US A PROPER TOOL TO RESTRICT DEVICE FUNCTIONS THAT ARE FOR SECURITY.. MANY of us deploy these routers as CPEs for ISP deployments or other industrial / enterprise applications, these routers do not belong to the users that log into them, they are simply on loan to them. The end users are granted limited access to customize specific settings while in their possession but restrictions on the configuration need to exist, and most of the devices eventually get returned to be reassigned to a new end user when they move out. We need a functional and reliable method to do this, skins are an entirely satisfactory method to limit this access for most people, we just need them to work every time and not break after every 2nd or 3rd update, and for you to recognize that this “not for security” functionality is something that is actually extremely important to many of us, regardless of if you want to call it security or not, the end result is what matters.
99% of our use of and need for skins falls exactly in line with your description, except for the problem where they don’t always work. We simplify the UI for end users to only present them the controls they need to access, and we hide from them the menus and controls which they should not be inside of. I don’t care if you want to call it security or not, but whatver you call it and if not skins, however you choose to implement it, your customers are telling you we need this functionality to be reliable.
Thanks for this..I did double check the current state - it seams that it is sorted on selected devices only OR it is related to ROS version. On RB 750G r3 and ROS 7.2.1 it is sorted, but od CCR1036 6.49.7 is NOT. Unfortunately we cannot move from 6.49.7 at least because of unsuported UPS for CCR in v7. Not sure if the device or ROS version is the reason (removing session file does not help).
You are right, I tested it only with v7 but now that I look on a v6.49 router indeed it is not sorted. Apparently the sorting is done by the router, not winbox.
So now it is clear that this issue remain in ROS 6.49.7 only 
Unfortunately there are still many devices and installations where ROS 7 cannot be used (in our case the unsupported UPS or SD cards on CCR or routing priority issue (undocumented change) since ROS v7.2.1+).