I have a crazy feature request.Abandon the current GUI framework that WinBox is using and move to QT. Yes, I know it will be a LOT of work, but it will make life easier for Mikrotik developers, and allow Mikrotik to add more features in the long run.How did you guess they have any problem with this framework?They just have more important priorities than 'rewrites' of GUI tools.
The WinBox is an effort to deliver one of the most usable of router managers. It stands out for the simple user interface that still gets to be one of the most user-friendly ones on the market. It stands out for the simple user interface that still gets to be one of the most user-friendly ones on the market. WinBox is a small utility that allows administration of Mikrotik RouterOS using a fast and simple GUI. It is a native Win32 binary, but can be run on Linux and Mac OSX using Wine. All WinBox interface functions are as close as possible to Console functions.
Like for example providing us with working WPA3 or adding features to RouterOS.Green developers in their mid-20s would rewrite everything with no reason. I would go even further and say please rewrite all to a Progressive WebApp (PWA). That will make it OS independent and also adjust better to screen size. Would also make the admin tool a lot more modern.It'd be the worst decision ever made. Don't go that way, Mikrotik.
I value the very lightweight tools you provide, their instant response times, low network requirements and high GUI update speeds. Web cannot provide that and you're gonna drown in endless JavaScript framework crap work and costly HTTP/Json garbage. Plus, instead of being 1.5 MB in size, it's going to be at least 500 MB. Please, don't even think about wasting your time with Electron or PWAs. Since v3.15 when opening a static IPv6 route that has a link-local gateway causes 100% cpu usage on winbox using Win7 x64.With a global address as gateway there is not cpu usage.In the meantime everything stops updating in Winbox (all other windows don't show new info)If I leave it open for over a few seconds winbox will disconnect completely from the router.v3.14 works without any issues.Oh, and I agree. Don't you dare change Winbox to some stupid Electron app.
Winbox is perfect as it is. We DON'T want it to change. I would welcome when the winbox-router connection is a little more patient in cases of network loss.With brief network interrups, like an intermediate router rebooting or an access point re-associating or a PPPoE connection being re-made, the open winbox windows all fall back to the connection screen.It would be nice when there was a configurable timeout or some option for patience in case of 'network unreachable' replies.
It could come back soon+1Especially now with winbox 3 that completely hides the whole window when disconnected so you cannot see what was happening at the time that got disconnected.Winbox 2 would keep the window open with all windows inside as they were at the time of the disconnection (and rarely would completely exit on disconnect). The problem with 'Click Reconnect, then Winbox window disappears and after exactly 30 seconds automatically disconnect from device with Connection lost window appearing again' still persist(first time spotted in v3.14 )same. Every one have this problem?I have a CCR1009 (6.42.5) with a routed subnet connected through a cable connection and a fiber line through PPPoE. When I connect to my PPPoE fiber I get the 30 seconds disconnect. I also notice that my winbox stats (time/cpu/uptime) all remain on 00:00:00. When I connect to my cable connection on the same box this issue doesn't appear, my connection remains stable and I receive the winbox stats after 2 seconds.
I also tested this on a RB3011 with 6.40.8 and fiber PPPoE, same issue: no stats and 30 second disconnect.When downloading winbox 3.12 my connection to the PPPoE connections remain stable and I receive my winbox stats immediately, this goes for the CCR1009 & the RB3011. Since v3.15 when opening a static IPv6 route that has a link-local gateway causes 100% cpu usage on winbox using Win7 x64.Have the same symptom here in the CAPsMAN Channel-List. Sometimes when copying channel and editing either frequency name or other items for that channel, the dialog freezes and does not respond to entries (Win7 x64).Best regards@colinardoAnd another place this bug occurs is when I have an EoIP tunnel and I click on the MTU field. It doesn't occur when adding a new EoIP tunnel, only when editing an existing one that doesn't have the MTU field configured yet. 'abandoned support for connecting to older RouterOS versions (older than v6), no DLLs will ever be downloaded'You probably don't want to do it, but what about support for local dlls?
A one-time download containing all 5.26 dlls that WinBox would be willing to use if available? Because there are some older devices that can't be upgraded to 6.x at all, or it's too heavy for them. It probably wouldn't be the perfect solution, because I guess there's no backward compatibility (5.26 dlls for other 5.x or even 4.x.), but better than nothing. Keeping older WinBox is of course an option, but it's a little annoying to remember which one needs to be used for given device. Or perhaps an option in new WinBox to open older one, when RouterOS.
There would not be a single user of routers who would not have found the utility in using some of the router management software. The WinBox is an effort to deliver one of the most usable of router managers. It stands out for the simple user interface that still gets to be one of the most user-friendly ones on the market. The small file size does offer faster speeds of downloads as compared to the near competitors. This could also be the main reason that the file is delivered intact and without corruption for the most parts.Despite the freedom that comes with the WinBox router manager, there are sufficient checks in place to keep the core functions of the router out of bounds to the user.
This does ensure that there is no system failure and is rather straightforward in the approach. It is this safeguard that calls for signing out of the system to have access to the innards of the working processes.It is entirely possible to keep track of the data traffic and a lot more of the operational aspects of the router after having installed the WinBox system onto it. Maximum use is made of the drag-and-drop feature and hence makes the whole operation simple enough to handle.
There is little interference to nearby systems and other management software that might be in the very vicinity.There is a possibility that the system can be tuned in to offer information on a real-time basis. The future of router management would mean more interventionist measures than currently in practice.
It could, in turn, expect a lot meaner systems too. There are enough and more space for further development with the WinBox system that it would not get outdated any time soon.The glove-like fit that the WinBox router software provides to the MikroTik router would often leave the onlooker wondering if it was designed with the management software in mind. The application does score over the more rustic management software tool that comes standard with the MikroTik router.
There is the intense use of technology here that little other competing software can provide the same level of compatibility for the most parts.