Package Details: winbox 4.0beta16-1

Git Clone URL: https://aur.archlinux.org/winbox.git (read-only, click to copy)
Package Base: winbox
Description: Mikrotik RouterOS GUI Configurator
Upstream URL: https://mikrotik.com/download
Licenses: custom
Submitter: TomHetmer
Maintainer: dundee (eworm)
Last Packager: eworm
Votes: 65
Popularity: 3.13
First Submitted: 2013-05-11 20:19 (UTC)
Last Updated: 2025-01-10 12:42 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 9 Next › Last »

keithy commented on 2024-09-13 18:09 (UTC)

Hmm, doesn't show any neighbours for me. Any ideas what I'm doing wrong??

eworm commented on 2024-09-13 11:27 (UTC)

Ah, well... Qt ist linked statically, so after all there was little change that this works. 🙃

Can you try to start it with QT_QPA_PLATFORM=xcb?

Janhouse commented on 2024-09-13 11:08 (UTC)

I already have qt6-base and qt6-wayland, it does not work.

eworm commented on 2024-09-13 08:46 (UTC)

Not using wayland here, but... The qt6-base package has an optional dependency on qt6-wayland. Perhaps you are missing that?

Janhouse commented on 2024-09-12 06:41 (UTC)

Missing some deps?

WinBox
Warning: Could not find the Qt platform plugin "wayland" in "" (:0, )
Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.
 (:0, )
[1]    697208 IOT instruction (core dumped)  WinBox

vmsh0 commented on 2024-09-03 08:44 (UTC) (edited on 2024-09-03 08:59 (UTC) by vmsh0)

Please note that one side effect of this update is losing saved devices. I'm not sure whether the Linux version of WinBox attempts to convert your old settings to the new version; I have used the Windows version to perform the conversion as follows:

  • Download WinBox 4 for Windows
  • Run it as WINEPREFIX=~/.winbox/wine wine WinBox.exe
  • It will pick up and convert your old config file :)
  • cp -r ~/.winbox/wine/drive_c/users/$USER/Application\ Data/Mikrotik/Winbox/* ~/.local/share/MikroTik/WinBox/

OPTIONAL: delete ~/.winbox, as otherwise your passwords will linger there forever

Please note just FYI that as of 4.0beta3 I'm seeing graphical glitches, multi-line input boxes are rendered as single-line inputs, and Safe Mode is absent; so it is indeed not production ready for my use case as it's missing vital features :)

eworm commented on 2024-08-30 14:53 (UTC)

Looks like Mikrotik is already pushing this in social media, see: https://youtu.be/IOjkWJfmM24

Also interest is pretty high. So already pushed winbox 4.0beta3...

If you still want or need the "legacy" Winbox 3.x go for package 'winbox3'. These two can even be installed side by side.

vmsh0 commented on 2024-08-30 11:20 (UTC)

I use this package for work. Switching to a new potentially unstable version wouldn't be so disruptive (in the sense that I can just download 3.41 again and keep working), but it would make the package unsuitable for my use case.

Thus, imho, this package should switch to 4.x whenever it is generally considered stable and equivalent to 3.x feature-wise. I agree that this first beta looks very promising!

eworm commented on 2024-08-29 06:58 (UTC)

Mikrotik has just release a first beta version of new Winbox 4.x, including a native Linux port: https://forum.mikrotik.com/viewtopic.php?t=210505

I guess we should switch to that one day or another... Any opinion when this should happen? First try looks very promising. :)

walrus commented on 2024-04-19 18:21 (UTC)

The download URL for winbox64.exe has changed. The new URL is: https://download.mikrotik.com/routeros/winbox/3.40/winbox64.exe.

diff --git a/PKGBUILD b/PKGBUILD
index a52f18c..e037d63 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -13,7 +13,7 @@ optdepends=(
   'ttf-ms-fonts: for better fonts'
 )
 install=${pkgname}.install
-source=("${pkgname}-${pkgver}.exe::https://download.mikrotik.com/winbox/${pkgver}/${pkgname}64.exe"
+source=("${pkgname}-${pkgver}.exe::https://download.mikrotik.com/routeros/winbox/${pkgver}/${pkgname}64.exe"
         "${pkgname}.desktop"
         "${pkgname}.png"
         "${pkgname}")