Winbox for M1

RouterOS Beginner Basics
1

Hi,

When will appear winbox for MacBook m1, this is not serious ???

2

Already there: http://forum.mikrotik.com/t/winbox-on-apple-silicon-first-try/144955/1

3

For M1 macOS Monterey did work

4

Is time to you to use some serious PC instead of one Apple device.

5

If a simple software was created only for one OS it's not serious... Why Mikrotik app exist on android and iOS ?? :smiley:

6

Apps are cool. That’s why they are developed.

7

Should be also Winbox for macOS

8

sorry but this is a really stupid answer.

I hope this is some kind of joke, however inappropriate.

9

Well said..

10

I just moved from Intel to M2 … and solved the display problem by updating winbox4mac to WINE 8 and Winbox 3.37.
Works fine, but is not yet tested in all directions :-p

11

I managed to update the exe in the package of the app.
can you help me to update the wine version ?

12

or can you upload the app updated ? I

13

DO NOT USE ANY PACKAGES WITH WINBOX, this is dangerous.

To use Winbox on Mac with M1/M2 processor you only need two things:

  1. install Wine from here https://github.com/Gcenx/macOS_Wine_builds/releases/download/8.0/wine-stable-8.0-osx64.tar.xz
  2. download winbox64.exe https://mt.lv/winbox64
  3. open winbox64.exe with Wine
14

Not working on latest macOS Ventura 13.2.1. I tried also with latest wine-devel.

15

works with Ventura 13.3
Screenshot 2023-03-21 at 16.40.57.png

16

Works for me. I installed wine with brew. Started wine and from the new terminal I started winbox64.
Tested on M1 macOS Ventura 13.2.1

17

@normis, I just like to understand what’s “dangerous” about use a package manager?

I can see y’all not wanting to support it. Or that redistribution violates Mikrtik copyright/IP/etc. But “dangerous” is a strong claim.

To be clear, nothing has passed Apple’s verification to be in the App Store, and even the document approach requires ignoring OS security warnings.

The problem in the recommend way is that wine is never checked for updates if you just directly installed wine from @gcenx GitHub – so if wine has a vulnerability that’s fixed in a newer version, there is nothing that flag you’d need to update it.

If the Homebrew package(s) are dangerous, someone should report them to the brew team:
https://github.com/Homebrew/brew/security/policy
I’d be happy to make a report myself, but there are no fact to backup the assertion.

18

On the past some “ready package” posted from users, not only for macos have surpriseS inside… :wink:

19

@normis has repeated this claim a few times. See How to install Winbox on macOS

Mikrotik certainly does recommend downloading other third-party things (e.g. Cloudflare, which creates a tunnel to internet using closed-source software and third-party networks) without much warning. So what's the difference with auditable public GitHub project that redistributed by brew?

20

The executable doesn’t make it on github, but the user loads it…
Users don’t check what’s written at all, but they love copy-and-pasting…
Leave it alone if there is someone who reads everything and compiles things on their own …

But this refers to anything, in a general way, not in the specific “GitHub”, “brew” or other cases.