Ideally winbox should be written in Java, let say using swing as GUI, or even much better newly created technology JavaFXYou mean like now Linux users complain about WINE as huge 'useless' dependency, with Java WinBox everyone could join the party and complain the same way about Java? Yep, sounds really cool, can't wait to have it.WINE is awful because it increases system vulnerability, not just because of dependencies. Java would be terrible as well. People talk abour Raspberry Pi - but i guess not first gen? Because that's what I own and It certainly can't run any GUI with any reasonable performance so it's just forced argument. Why not just create some CLI that can connect via mac?

1. Install Wine In Linux

You know like config over serial port just not through serial but through MAC. WinBox might be created with some WinAPI or other windows-only crap and porting all of it would be pain and completely not work efffort.I personally never used WinBox in my life.

I'm using WebFig and CLI. I find it sufficient. The only advantage of WinBox i know is MAC connectivity. But for this we don't need GUI. Since 6.30 i have also problems connecting with mac on my old debian linux laptop, for some devices it was solved to clean the winbox cache.Also, check your encryption settings when running MAC-Winbox (I would suggest disabling that for MAC connection) - if packets are missing, the secure connection will drop.In turn - I am enabling IPv6 on my routers and using link-local address to connect to the router instead of MAC, as that gives me fully working TCP.Also, not native Linux, but some can check out TikApp.

Especially if running Android on RPI. I'm still at a loss as to why using WINE to run Winbox is such an issue?Why not implore devs to do something useful rather than create functionality we already have?Idk, have you ever read 'Why it's bad idea to install X in production environment'?

Or 'Why it's bad idea to install gcc in production environment' or 'Why it's bad idea to install absolutely anything you don't totally have to in production environment'? Everything that has anything to do with windows makes your machine more vulnerable. And some people use Linux for security. As long as you don't use dedicated device just for network config your device might get compromised.

And if device used for core network config gets compromised. It might be really, really bad scenario and put your company network on the list of hijacked servers to rent on black market.In properly configured, restrictive network devices having access to any kind of configuration can be weakest point in whole security system. Putting WINE on them makes them even weaker. I'm still at a loss as to why using WINE to run Winbox is such an issue?Why not implore devs to do something useful rather than create functionality we already have?Idk, have you ever read 'Why it's bad idea to install X in production environment'? Or 'Why it's bad idea to install gcc in production environment' or 'Why it's bad idea to install absolutely anything you don't totally have to in production environment'? Everything that has anything to do with windows makes your machine more vulnerable.

And some people use Linux for security. As long as you don't use dedicated device just for network config your device might get compromised.

And if device used for core network config gets compromised. It might be really, really bad scenario and put your company network on the list of hijacked servers to rent on black market.In properly configured, restrictive network devices having access to any kind of configuration can be weakest point in whole security system.

Putting WINE on them makes them even weaker.So your point is paranoia? I'm still at a loss as to why using WINE to run Winbox is such an issue?Why not implore devs to do something useful rather than create functionality we already have?Idk, have you ever read 'Why it's bad idea to install X in production environment'? Or 'Why it's bad idea to install gcc in production environment' or 'Why it's bad idea to install absolutely anything you don't totally have to in production environment'?

Install Wine In Linux

Everything that has anything to do with windows makes your machine more vulnerable. And some people use Linux for security. As long as you don't use dedicated device just for network config your device might get compromised. And if device used for core network config gets compromised. It might be really, really bad scenario and put your company network on the list of hijacked servers to rent on black market.In properly configured, restrictive network devices having access to any kind of configuration can be weakest point in whole security system.

Putting WINE on them makes them even weaker.So your point is paranoia?Yeah, some people call it 'security' but I guess it's synonym considering number of vulnerable networks. +1 Winbox is not working correctly in my uptodate Windows10 home, and really sucks in Wine Ubuntu.

If I did this all the time, I would learn command line but I am not a WISP provider. Though I now have a lot of Microtik systems around here. So my vote per routerboard should be more than 7. I am not putting down this laptop to go count them.Wine is easy to use if winbox.exe worked properly under wine. But a linux build for Ubuntu would be nice. I assume Microtik would not want to release source.

Still interested in a native linux version, if a correct 'snap' packages has been crafted it means allot of other non debian/ubuntu distros with snap support will also be compatible(not mentioning cpu architecture differences)!Flatpack is also an option for linux distros?Has anyone tried running winbox on non x86 windows 10 tablets/notebooks and does it run in windows10 (without x86 emulation on the arm) or will Mikrotik make a windows store universal app for covering the upcoming x86/arm windows versions?