WinBox v3.40 released!
-
- MikroTik Support
- Posts: 283
- Joined: Fri Sep 15, 2017 8:05 am
- Location: Riga
WinBox v3.40 released!
What's new in v3.40:
Important note!!!
Upgrade from older WinBox versions will not work. Manual WinBox upgrade is required.
*) fit BTH QR code into default settings window;
*) fixed WinBox upgrade procedure (introduced in v3.39);
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
Important note!!!
Upgrade from older WinBox versions will not work. Manual WinBox upgrade is required.
*) fit BTH QR code into default settings window;
*) fixed WinBox upgrade procedure (introduced in v3.39);
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
-
- Frequent Visitor
- Posts: 73
- Joined: Tue Dec 11, 2018 10:02 pm
- Location: The Netherlands
Re: WinBox v3.40 released!
*) fit BTH QR code into default settings window;
Now I can see only the top 20% of the QR-code instead of the top 80% in the previous release. So it has become worse.
Now I can see only the top 20% of the QR-code instead of the top 80% in the previous release. So it has become worse.
-
- MikroTik Support
- Posts: 1623
- Joined: Wed Jul 16, 2014 5:22 am
- Location: Riga, Latvia
Re: WinBox v3.40 released!
Also RouterOS upgrade will be required. BTH is not yet released as stable feature. Will work just fine in upcoming betas.
-
- Member Candidate
- Posts: 258
- Joined: Fri Nov 13, 2009 9:08 pm
- Location: Johannesburg, South Africa
Re: WinBox v3.40 released!
I get "ERROR: Upgrade file was corrupted" when trying to upgrade from v3.38 using the "Update" button. Tried retrying it several times with same result.
So it seems the upgrade problem was introduced earlier than v3.39 ... ?
Edit: Ok, I see the news says "Upgrade from older WinBox versions will not work. Manual WinBox upgrade is required". I will just update it manually, no trouble :)
So it seems the upgrade problem was introduced earlier than v3.39 ... ?
Edit: Ok, I see the news says "Upgrade from older WinBox versions will not work. Manual WinBox upgrade is required". I will just update it manually, no trouble :)
You do not have the required permissions to view the files attached to this post.
-
- Member Candidate
- Posts: 236
- Joined: Fri Mar 24, 2023 2:24 pm
Re: WinBox v3.40 released!
Did you read TFM
Works for me, just replace old with NEW!
Works for me, just replace old with NEW!
-
- Member
- Posts: 366
- Joined: Thu Sep 29, 2016 7:13 am
Re: WinBox v3.40 released!
another update without dark mode !
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
Update works over wine :P
-
- Forum Guru
- Posts: 11986
- Joined: Tue Feb 25, 2014 11:49 am
- Location: Italy
-
- just joined
- Posts: 4
- Joined: Sat Nov 12, 2022 2:04 am
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
Actually I'm also using CrossOver wine fork on Mac (Gcenx build), maybe with official wine it's different. Wine is supporting Windows API WinVerifyTrust, if this API is used in Winbox to verify PE certificate.
Last edited by optio on Tue Oct 10, 2023 7:12 pm, edited 1 time in total.
-
- Frequent Visitor
- Posts: 73
- Joined: Tue Dec 11, 2018 10:02 pm
- Location: The Netherlands
Re: WinBox v3.40 released!
I'm running ROS version 7.12 beta9 in which BTH is active and configured.
Or do you mean this winbox version with BTH is only working with ROS version 7.13 betaxx and above?
-
- Member Candidate
- Posts: 119
- Joined: Sat May 03, 2014 3:04 am
Re: WinBox v3.40 released!
add option: auto safe mode on startup :-(
-
- Forum Guru
- Posts: 1277
- Joined: Tue Jun 23, 2015 12:35 pm
Re: WinBox v3.40 released!
why u make them hard live?another update without dark mode !
what that will change?
-
- just joined
- Posts: 18
- Joined: Thu Jun 18, 2020 6:48 pm
- Location: Lithuania
Re: WinBox v3.40 released!
It will make people to not become narrow-eyed every time Winbox opens in dark room with dark-themed OS.
Also it probably won't happen until complete UI component library redesign (basically Winbox rewrite). Real solution is to make your community open-source tool, like what Portainer did to Docker. RouterOS have really good API for that.
Last edited by vinigas on Fri Oct 20, 2023 5:09 pm, edited 2 times in total.
-
- Forum Guru
- Posts: 1182
- Joined: Fri Dec 31, 2021 10:44 am
- Location: Croatia
Re: WinBox v3.40 released!
I agree with @vinigas, it would be nice to have dark mode...
-
- Forum Guru
- Posts: 11546
- Joined: Thu Mar 03, 2016 9:23 pm
Re: WinBox v3.40 released!
While it would be nice to have dark mode (I don't care though), the question why are certain users nagging about it with every new winbox version is highly relevant. Release threads in this forum (such as this) should be used to report bugs (possibly specific to the particular version). And lack of dark mode is not a bug, it's a missing feature. Go and harass MT via proper support channels (e.g. sales department).
-
- newbie
- Posts: 34
- Joined: Thu May 12, 2011 1:52 am
Re: WinBox v3.40 released!
Every time I execute the new Winbox64.exe on Windows 10, I get the software install warning "The app you're trying to install isn't a Microsoft-verified app" from Windows. I have also tried the 32-bit version of v3.40.
I have Windows set to warn when I'm installing an app from somewhere other than the windows store. This makes it harder for accidental installs of spyware to occur. So, I would rather not turn it off.
Note: I did not get this warning with the 32-bit v3.37.
PS: I hate forced dark mode. I work on the edge of a retail sales floor. There is so much light behind my monitor that it is nearly impossible to read most "Dark Mode" interfaces.
I have Windows set to warn when I'm installing an app from somewhere other than the windows store. This makes it harder for accidental installs of spyware to occur. So, I would rather not turn it off.
Note: I did not get this warning with the 32-bit v3.37.
PS: I hate forced dark mode. I work on the edge of a retail sales floor. There is so much light behind my monitor that it is nearly impossible to read most "Dark Mode" interfaces.
Last edited by RavenWing71 on Fri Oct 27, 2023 7:06 pm, edited 1 time in total.
-
- Forum Guru
- Posts: 3004
- Joined: Sun Aug 24, 2014 1:14 am
- Location: Bogota Colombia
Re: WinBox v3.40 released!
RavenWing71 wrote: ↑Fri Oct 27, 2023 6:57 pm
PS: I hate forced dark mode. I work on the edge of a retail sales floor. There is so much light behind my monitor that it is nearly impossible to read most "Dark Mode" interfaces.
who say anything about Forced ??
always a dark mode is something SELECTABLE
-
- Forum Guru
- Posts: 3004
- Joined: Sun Aug 24, 2014 1:14 am
- Location: Bogota Colombia
Re: WinBox v3.40 released!
i tryed today and i dont have any warning, please re-download maybe something changed, or configure properly your systemRavenWing71 wrote: ↑Fri Oct 27, 2023 6:57 pm Every time I execute the new Winbox64.exe on Windows 10, I get the software install warning "The app you're trying to install isn't a Microsoft-verified app" from Windows.
I have Windows set to warn when I'm installing an app from somewhere other than the windows store. This makes it harder for accidental installs of spyware to occur. So, I would rather not turn it off.
Note: I did not get this warning with v3.37.
-
- newbie
- Posts: 34
- Joined: Thu May 12, 2011 1:52 am
Re: WinBox v3.40 released!
You want to tell Ubiquiti that? They force dark mode in the settings portion of their management software...chechito wrote: ↑Fri Oct 27, 2023 7:04 pmRavenWing71 wrote: ↑Fri Oct 27, 2023 6:57 pm
PS: I hate forced dark mode. I work on the edge of a retail sales floor. There is so much light behind my monitor that it is nearly impossible to read most "Dark Mode" interfaces.
who say anything about Forced ??
always a dark mode is something SELECTABLE
-
- newbie
- Posts: 34
- Joined: Thu May 12, 2011 1:52 am
Re: WinBox v3.40 released!
Check in the Settings app under Apps > Apps & Features heading > Choose where to get apps. Mine is set to "Anywhere, but warn me before installing an app that's not from the Microsoft Store." Every time I run v3.40 of Winbox I get the warning. For some reason Windows thinks Winbox is an installer instead of an app. It did not think this with v3.37.chechito wrote: ↑Fri Oct 27, 2023 7:07 pmi tryed today and i dont have any warning, please re-download maybe something changed, or configure properly your systemRavenWing71 wrote: ↑Fri Oct 27, 2023 6:57 pm Every time I execute the new Winbox64.exe on Windows 10, I get the software install warning "The app you're trying to install isn't a Microsoft-verified app" from Windows.
I have Windows set to warn when I'm installing an app from somewhere other than the windows store. This makes it harder for accidental installs of spyware to occur. So, I would rather not turn it off.
Note: I did not get this warning with v3.37.
-
- Frequent Visitor
- Posts: 52
- Joined: Thu Jun 08, 2023 7:35 pm
Re: WinBox v3.40 released!
Download the application again from the website.
I don't confirm. Verified. Microsoft Windows [Version 10.0.19045.3448]
I don't confirm. Verified. Microsoft Windows [Version 10.0.19045.3448]
-
- Member
- Posts: 435
- Joined: Fri Sep 25, 2020 1:30 pm
- Location: Russia, Moscow
Re: WinBox v3.40 released!
I don’t really understand what we’re talking about here. Downloaded new Winbox. Launched. Everything is working. What is the BTH?
-
- Forum Guru
- Posts: 5436
- Joined: Tue Apr 13, 2021 12:14 am
- Location: Belgium
-
- Forum Guru
- Posts: 1182
- Joined: Fri Dec 31, 2021 10:44 am
- Location: Croatia
Re: WinBox v3.40 released!
Correction, it's available in 7.12 stable.
-
- Forum Guru
- Posts: 5436
- Joined: Tue Apr 13, 2021 12:14 am
- Location: Belgium
Re: WinBox v3.40 released!
Showoff ...
-
- Forum Guru
- Posts: 19251
- Joined: Sun Feb 18, 2018 10:28 pm
- Location: Nova Scotia, Canada
Re: WinBox v3.40 released!
Not all functions are in winbox though, so partially correct ;-PP
-
- Forum Guru
- Posts: 1182
- Joined: Fri Dec 31, 2021 10:44 am
- Location: Croatia
Re: WinBox v3.40 released!
But statement was about is BTH available in 7.12 not are all functions available in Winbox :PPP
-
- just joined
- Posts: 2
- Joined: Sun Jan 05, 2020 8:17 pm
Re: WinBox v3.40 released!
Works for me on Mac with crossOver but I have still the "Open In New Window" issue.
Waiting for a MacOs native Winbox :)
Waiting for a MacOs native Winbox :)
-
- just joined
- Posts: 22
- Joined: Fri Oct 12, 2018 10:13 pm
Re: WinBox v3.40 released!
Has anyone else experienced the System / Reboot button in Winbox no longer works? I have to reboot all my devices using the /system reboot command from the Terminal
-
- Forum Guru
- Posts: 5436
- Joined: Tue Apr 13, 2021 12:14 am
- Location: Belgium
Re: WinBox v3.40 released!
I've done quite a bit of reboots already using Winbox 3.40 / System / Reboot ...
-
- Forum Guru
- Posts: 1182
- Joined: Fri Dec 31, 2021 10:44 am
- Location: Croatia
Re: WinBox v3.40 released!
No problem with reboots or shutdowns on 3.40.
-
- just joined
- Posts: 8
- Joined: Mon Jun 23, 2014 3:16 am
- Location: Tbilisi, Georgia
Re: WinBox v3.40 released!
I'm with @evellin :) Waiting for native macOS WinBox as well
-
- newbie
- Posts: 44
- Joined: Tue Oct 17, 2023 9:25 am
Re: WinBox v3.40 released!
While a native version would be good, I am finding no pain (Winbox itself aside) running Winbox in Crossover. Until yesterday I used Wine, but MacOS refused to believe it truly had permitted directory accesses without reminders, then with Sonoma 14.1.2 it started dropping out during sessions so I tried Crossover which was immediately stable (and appears to run VCDS as well, for a total digression) so I will pay money for that.
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
There is a free macOS Crossover wine solution, mentioned in topic ?t=196622
-
- newbie
- Posts: 44
- Joined: Tue Oct 17, 2023 9:25 am
Re: WinBox v3.40 released!
196622 produced no hits in Search and your mention is not a link.
Are you referring to alternative builds? I am quite happy to support codeweavers who have provided a working solution. For their price, it is not worth my time either to seek alternative builds or to find and compile the source with even slight attendant risk of 'issues'.
Are you referring to alternative builds? I am quite happy to support codeweavers who have provided a working solution. For their price, it is not worth my time either to seek alternative builds or to find and compile the source with even slight attendant risk of 'issues'.
-
- Forum Guru
- Posts: 11986
- Joined: Tue Feb 25, 2014 11:49 am
- Location: Italy
Re: WinBox v3.40 released!
Really?phascogale wrote: ↑Thu Dec 07, 2023 11:35 am 196622 produced no hits in Search and your mention is not a link.
viewtopic.php?t=196622
-
- newbie
- Posts: 44
- Joined: Tue Oct 17, 2023 9:25 am
Re: WinBox v3.40 released!
Yes, really :) but thank you for the link. There appears to be some less literal interpretation of “search for 196622” that I have missed in this forum software.
I had seen that topic before by searching Crossover so I take it that would be the Gcenx build to which I referred above.
Anyway, happy to get on with stuff using Winbox in Crossover. I finally start configuration of the RB5009 today, with a second hap ax lite to follow. Since the first Mikrotik in May I have quite enjoyed the journey despite RouterOS/Winbox idiosyncrasies.
I had seen that topic before by searching Crossover so I take it that would be the Gcenx build to which I referred above.
Anyway, happy to get on with stuff using Winbox in Crossover. I finally start configuration of the RB5009 today, with a second hap ax lite to follow. Since the first Mikrotik in May I have quite enjoyed the journey despite RouterOS/Winbox idiosyncrasies.
-
- MikroTik Support
- Posts: 26354
- Joined: Fri May 28, 2004 9:04 am
- Location: Riga, Latvia
Re: WinBox v3.40 released!
Why use crossover, when Wine works perfectly on macs? If you found an issue, let's solve it together, but there is no need to pay for commercial emulators
-
- Long time Member
- Posts: 528
- Joined: Mon Jan 27, 2014 2:35 pm
- Location: California
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
Guessing norims has no need to run Dude (or any other win32 app) on Mac or is still on Intel Mac.
-
- newbie
- Posts: 44
- Joined: Tue Oct 17, 2023 9:25 am
Re: WinBox v3.40 released!
normis, wine worked perfectly for me for months, then I had dropouts not apparently attributable to Winbox actions on my part (i.e. doing nothing at the time), so I ascribed the problem to the 14.1.2 MacOS update and tried something else which immediately worked. I can imagine that under the hood there is no difference, that some error or other on my part or cosmic rays from the universe meant I did not properly distinguish association from cause and effect. That does not bother me. It is not as if I am attacking Wine, which I still have.
I am also influenced by the fact that a totally unrelated application useful to me installed under Crossover where it did not under Wine, one attempt each. Personal circumstances.
I am also influenced by the fact that a totally unrelated application useful to me installed under Crossover where it did not under Wine, one attempt each. Personal circumstances.
-
- Long time Member
- Posts: 569
- Joined: Fri Jun 21, 2019 10:04 am
Re: WinBox v3.40 released!
WinBox won't auto-upgrade. Says "ERROR: Upgrade file was corrupt":
Not a big problem but thought I'd mention it.
Not a big problem but thought I'd mention it.
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
@robmaltsystems 3rd line in 1st post (also in your screenshot)
-
- Long time Member
- Posts: 569
- Joined: Fri Jun 21, 2019 10:04 am
Re: WinBox v3.40 released!
Doh just proves that people don't read IT messages 😉 In my defence, because it failed, I didn't read any more. So change request, implement colour in the Winbox status box and make that red.
-
- just joined
- Posts: 24
- Joined: Sat Apr 16, 2011 10:46 pm
Re: WinBox v3.40 released!
Speaking of "...let's solve it together...", I have reported this long time ago, viewtopic.php?p=937667#p937667, but no fix ever. Only "Works for me" and "I THINK it is a Wine issue", none of them from Mikrotik people...
So let me try again: fresh install of OpenSUSE LEAP 15.5 and OpenSUSE Tumbleweed, Wine 8.0 and 8.2.1, when you select "Open in new window" and then "Connect" it just returns to the initial screen, then after about 30 seconds new Winbox windows appears with "Router disconnected", then countdown from 5, then new window opens just fine.
I cannot believe that I an the only one seeing this...
By the way, after clicking "Connect" nothing should change in original window, cursor should remain in exactly the same spot (as it is now, the whole window is refreshed and the point of "open in new windows" is lost because I have to scroll down again to find where I was...).
I have done some tcpdump-ing, this is first attempt - unsuccessful
Code: Select all
09:18:53.115667 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [S], seq 2848251094, win 32120, options [mss 1460,sackOK,TS val 2736750616 ecr 0,nop,wscale 7], length 0
09:18:53.116002 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [S.], seq 2694802751, ack 2848251095, win 65160, options [mss 1460,sackOK,TS val 3584758348 ecr 2736750616,nop,wscale 4], length 0
09:18:53.116015 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 1, win 251, options [nop,nop,TS val 2736750617 ecr 3584758348], length 0
09:18:53.127478 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 1:42, ack 1, win 251, options [nop,nop,TS val 2736750628 ecr 3584758348], length 41
09:18:53.127817 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 42, win 4070, options [nop,nop,TS val 3584758359 ecr 2736750628], length 0
09:18:53.180619 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 1:52, ack 42, win 4070, options [nop,nop,TS val 3584758412 ecr 2736750628], length 51
09:18:53.180630 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 52, win 251, options [nop,nop,TS val 2736750681 ecr 3584758412], length 0
09:18:53.181562 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 42:76, ack 52, win 251, options [nop,nop,TS val 2736750682 ecr 3584758412], length 34
09:18:53.181773 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 76, win 4068, options [nop,nop,TS val 3584758413 ecr 2736750682], length 0
09:18:53.204018 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 52:86, ack 76, win 4068, options [nop,nop,TS val 3584758436 ecr 2736750682], length 34
09:18:53.204123 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 76:192, ack 86, win 251, options [nop,nop,TS val 2736750705 ecr 3584758436], length 116
09:18:53.204420 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 192, win 4061, options [nop,nop,TS val 3584758436 ecr 2736750705], length 0
09:18:53.206168 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 86:460, ack 192, win 4061, options [nop,nop,TS val 3584758438 ecr 2736750705], length 374
09:18:53.206276 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 192:308, ack 460, win 249, options [nop,nop,TS val 2736750707 ecr 3584758438], length 116
09:18:53.206534 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 308, win 4054, options [nop,nop,TS val 3584758438 ecr 2736750707], length 0
09:18:53.207344 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 460:592, ack 308, win 4054, options [nop,nop,TS val 3584758439 ecr 2736750707], length 132
09:18:53.208311 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 308:440, ack 592, win 249, options [nop,nop,TS val 2736750709 ecr 3584758439], length 132
09:18:53.208568 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 440, win 4046, options [nop,nop,TS val 3584758440 ecr 2736750709], length 0
09:18:53.209473 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 592:1740, ack 440, win 4046, options [nop,nop,TS val 3584758441 ecr 2736750709], length 1148
09:18:53.210023 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 440:572, ack 1740, win 249, options [nop,nop,TS val 2736750711 ecr 3584758441], length 132
09:18:53.210258 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 572, win 4038, options [nop,nop,TS val 3584758442 ecr 2736750711], length 0
09:18:53.211145 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 1740:1888, ack 572, win 4038, options [nop,nop,TS val 3584758443 ecr 2736750711], length 148
09:18:53.252913 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 1888, win 249, options [nop,nop,TS val 2736750754 ecr 3584758443], length 0
and this is ~35 seconds later
Code: Select all
09:19:28.429673 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [S], seq 2116529504, win 32120, options [mss 1460,sackOK,TS val 2736785930 ecr 0,nop,wscale 7], length 0
09:19:28.430054 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [S.], seq 3680094689, ack 2116529505, win 65160, options [mss 1460,sackOK,TS val 3584793661 ecr 2736785930,nop,wscale 4], length 0
09:19:28.430067 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 1, win 251, options [nop,nop,TS val 2736785931 ecr 3584793661], length 0
09:19:28.441530 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 1:42, ack 1, win 251, options [nop,nop,TS val 2736785942 ecr 3584793661], length 41
09:19:28.441875 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 42, win 4070, options [nop,nop,TS val 3584793673 ecr 2736785942], length 0
09:19:28.460981 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1:52, ack 42, win 4070, options [nop,nop,TS val 3584793692 ecr 2736785942], length 51
09:19:28.460989 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 52, win 251, options [nop,nop,TS val 2736785962 ecr 3584793692], length 0
09:19:28.461867 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 42:76, ack 52, win 251, options [nop,nop,TS val 2736785963 ecr 3584793692], length 34
09:19:28.462033 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 76, win 4068, options [nop,nop,TS val 3584793693 ecr 2736785963], length 0
09:19:28.489387 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 52:86, ack 76, win 4068, options [nop,nop,TS val 3584793721 ecr 2736785963], length 34
09:19:28.489605 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 76:192, ack 86, win 251, options [nop,nop,TS val 2736785990 ecr 3584793721], length 116
09:19:28.489920 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 192, win 4061, options [nop,nop,TS val 3584793721 ecr 2736785990], length 0
09:19:28.492581 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 86:460, ack 192, win 4061, options [nop,nop,TS val 3584793724 ecr 2736785990], length 374
09:19:28.492724 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 192:308, ack 460, win 249, options [nop,nop,TS val 2736785994 ecr 3584793724], length 116
09:19:28.493013 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 308, win 4054, options [nop,nop,TS val 3584793724 ecr 2736785994], length 0
09:19:28.494076 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 460:592, ack 308, win 4054, options [nop,nop,TS val 3584793725 ecr 2736785994], length 132
09:19:28.496609 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 308:440, ack 592, win 249, options [nop,nop,TS val 2736785997 ecr 3584793725], length 132
09:19:28.496945 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 440, win 4046, options [nop,nop,TS val 3584793728 ecr 2736785997], length 0
09:19:28.498084 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 592:1740, ack 440, win 4046, options [nop,nop,TS val 3584793729 ecr 2736785997], length 1148
09:19:28.498810 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 440:572, ack 1740, win 249, options [nop,nop,TS val 2736786000 ecr 3584793729], length 132
09:19:28.499088 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 572, win 4038, options [nop,nop,TS val 3584793730 ecr 2736786000], length 0
09:19:28.500265 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1740:1888, ack 572, win 4038, options [nop,nop,TS val 3584793732 ecr 2736786000], length 148
09:19:28.534424 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 572:672, ack 1888, win 249, options [nop,nop,TS val 2736786035 ecr 3584793732], length 100
09:19:28.534789 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 672, win 4032, options [nop,nop,TS val 3584793766 ecr 2736786035], length 0
09:19:28.536356 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1888:2004, ack 672, win 4032, options [nop,nop,TS val 3584793768 ecr 2736786035], length 116
09:19:28.579582 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 2004, win 249, options [nop,nop,TS val 2736786080 ecr 3584793768], length 0
09:19:28.602815 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 672:788, ack 2004, win 249, options [nop,nop,TS val 2736786104 ecr 3584793768], length 116
09:19:28.624811 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], seq 788:2236, ack 2004, win 249, options [nop,nop,TS val 2736786126 ecr 3584793768], length 1448
09:19:28.625489 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 2236, win 4005, options [nop,nop,TS val 3584793857 ecr 2736786104], length 0
09:19:28.625503 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 2236:2308, ack 2004, win 249, options [nop,nop,TS val 2736786126 ecr 3584793857], length 72
09:19:28.627110 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], seq 2308:3756, ack 2004, win 249, options [nop,nop,TS val 2736786128 ecr 3584793857], length 1448
09:19:28.627676 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 3756, win 4005, options [nop,nop,TS val 3584793859 ecr 2736786126], length 0
09:19:28.627678 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 3756:4340, ack 2004, win 249, options [nop,nop,TS val 2736786128 ecr 3584793859], length 584
09:19:28.631744 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 2004:2120, ack 4340, win 4005, options [nop,nop,TS val 3584793863 ecr 2736786128], length 116
09:19:28.631748 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 4340:5396, ack 2120, win 249, options [nop,nop,TS val 2736786133 ecr 3584793863], length 1056
09:19:28.643868 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], seq 2120:3568, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
09:19:28.643941 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 3568:5016, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
09:19:28.643947 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 5016, win 249, options [nop,nop,TS val 2736786145 ecr 3584793875], length 0
09:19:28.644030 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 5396:5512, ack 5016, win 249, options [nop,nop,TS val 2736786145 ecr 3584793875], length 116
09:19:28.644079 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], seq 5016:6464, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
09:19:28.644181 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 6464:7912, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
....
So, "...let's solve it together...", please.
-
- MikroTik Support
- Posts: 26354
- Joined: Fri May 28, 2004 9:04 am
- Location: Riga, Latvia
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
It was just example for comment "Why use crossover, when Wine works perfectly on macs?". It's not in all cases. And others also mentioned issues with 64-bit app. I had Winbox window freezes several times and I had to kill process (not sure if is related to wine) but it doesn't occur on other applications which are run by wine.
Last edited by optio on Tue Dec 12, 2023 12:14 pm, edited 1 time in total.
-
- MikroTik Support
- Posts: 61
- Joined: Mon May 13, 2019 7:41 am
Re: WinBox v3.40 released!
We have same situation on our local setups, will see if this can be fixed in upcoming releases, thanks for report.
sinisa wrote: ↑Tue Dec 12, 2023 9:27 amSpeaking of "...let's solve it together...", I have reported this long time ago, viewtopic.php?p=937667#p937667, but no fix ever. Only "Works for me" and "I THINK it is a Wine issue", none of them from Mikrotik people...
So let me try again: fresh install of OpenSUSE LEAP 15.5 and OpenSUSE Tumbleweed, Wine 8.0 and 8.2.1, when you select "Open in new window" and then "Connect" it just returns to the initial screen, then after about 30 seconds new Winbox windows appears with "Router disconnected", then countdown from 5, then new window opens just fine.
I cannot believe that I an the only one seeing this...
By the way, after clicking "Connect" nothing should change in original window, cursor should remain in exactly the same spot (as it is now, the whole window is refreshed and the point of "open in new windows" is lost because I have to scroll down again to find where I was...).
I have done some tcpdump-ing, this is first attempt - unsuccessful
Code: Select all
09:18:53.115667 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [S], seq 2848251094, win 32120, options [mss 1460,sackOK,TS val 2736750616 ecr 0,nop,wscale 7], length 0 09:18:53.116002 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [S.], seq 2694802751, ack 2848251095, win 65160, options [mss 1460,sackOK,TS val 3584758348 ecr 2736750616,nop,wscale 4], length 0 09:18:53.116015 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 1, win 251, options [nop,nop,TS val 2736750617 ecr 3584758348], length 0 09:18:53.127478 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 1:42, ack 1, win 251, options [nop,nop,TS val 2736750628 ecr 3584758348], length 41 09:18:53.127817 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 42, win 4070, options [nop,nop,TS val 3584758359 ecr 2736750628], length 0 09:18:53.180619 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 1:52, ack 42, win 4070, options [nop,nop,TS val 3584758412 ecr 2736750628], length 51 09:18:53.180630 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 52, win 251, options [nop,nop,TS val 2736750681 ecr 3584758412], length 0 09:18:53.181562 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 42:76, ack 52, win 251, options [nop,nop,TS val 2736750682 ecr 3584758412], length 34 09:18:53.181773 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 76, win 4068, options [nop,nop,TS val 3584758413 ecr 2736750682], length 0 09:18:53.204018 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 52:86, ack 76, win 4068, options [nop,nop,TS val 3584758436 ecr 2736750682], length 34 09:18:53.204123 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 76:192, ack 86, win 251, options [nop,nop,TS val 2736750705 ecr 3584758436], length 116 09:18:53.204420 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 192, win 4061, options [nop,nop,TS val 3584758436 ecr 2736750705], length 0 09:18:53.206168 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 86:460, ack 192, win 4061, options [nop,nop,TS val 3584758438 ecr 2736750705], length 374 09:18:53.206276 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 192:308, ack 460, win 249, options [nop,nop,TS val 2736750707 ecr 3584758438], length 116 09:18:53.206534 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 308, win 4054, options [nop,nop,TS val 3584758438 ecr 2736750707], length 0 09:18:53.207344 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 460:592, ack 308, win 4054, options [nop,nop,TS val 3584758439 ecr 2736750707], length 132 09:18:53.208311 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 308:440, ack 592, win 249, options [nop,nop,TS val 2736750709 ecr 3584758439], length 132 09:18:53.208568 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 440, win 4046, options [nop,nop,TS val 3584758440 ecr 2736750709], length 0 09:18:53.209473 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 592:1740, ack 440, win 4046, options [nop,nop,TS val 3584758441 ecr 2736750709], length 1148 09:18:53.210023 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 440:572, ack 1740, win 249, options [nop,nop,TS val 2736750711 ecr 3584758441], length 132 09:18:53.210258 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 572, win 4038, options [nop,nop,TS val 3584758442 ecr 2736750711], length 0 09:18:53.211145 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 1740:1888, ack 572, win 4038, options [nop,nop,TS val 3584758443 ecr 2736750711], length 148 09:18:53.252913 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 1888, win 249, options [nop,nop,TS val 2736750754 ecr 3584758443], length 0
and this is ~35 seconds later
Code: Select all
09:19:28.429673 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [S], seq 2116529504, win 32120, options [mss 1460,sackOK,TS val 2736785930 ecr 0,nop,wscale 7], length 0 09:19:28.430054 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [S.], seq 3680094689, ack 2116529505, win 65160, options [mss 1460,sackOK,TS val 3584793661 ecr 2736785930,nop,wscale 4], length 0 09:19:28.430067 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 1, win 251, options [nop,nop,TS val 2736785931 ecr 3584793661], length 0 09:19:28.441530 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 1:42, ack 1, win 251, options [nop,nop,TS val 2736785942 ecr 3584793661], length 41 09:19:28.441875 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 42, win 4070, options [nop,nop,TS val 3584793673 ecr 2736785942], length 0 09:19:28.460981 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1:52, ack 42, win 4070, options [nop,nop,TS val 3584793692 ecr 2736785942], length 51 09:19:28.460989 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 52, win 251, options [nop,nop,TS val 2736785962 ecr 3584793692], length 0 09:19:28.461867 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 42:76, ack 52, win 251, options [nop,nop,TS val 2736785963 ecr 3584793692], length 34 09:19:28.462033 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 76, win 4068, options [nop,nop,TS val 3584793693 ecr 2736785963], length 0 09:19:28.489387 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 52:86, ack 76, win 4068, options [nop,nop,TS val 3584793721 ecr 2736785963], length 34 09:19:28.489605 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 76:192, ack 86, win 251, options [nop,nop,TS val 2736785990 ecr 3584793721], length 116 09:19:28.489920 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 192, win 4061, options [nop,nop,TS val 3584793721 ecr 2736785990], length 0 09:19:28.492581 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 86:460, ack 192, win 4061, options [nop,nop,TS val 3584793724 ecr 2736785990], length 374 09:19:28.492724 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 192:308, ack 460, win 249, options [nop,nop,TS val 2736785994 ecr 3584793724], length 116 09:19:28.493013 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 308, win 4054, options [nop,nop,TS val 3584793724 ecr 2736785994], length 0 09:19:28.494076 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 460:592, ack 308, win 4054, options [nop,nop,TS val 3584793725 ecr 2736785994], length 132 09:19:28.496609 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 308:440, ack 592, win 249, options [nop,nop,TS val 2736785997 ecr 3584793725], length 132 09:19:28.496945 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 440, win 4046, options [nop,nop,TS val 3584793728 ecr 2736785997], length 0 09:19:28.498084 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 592:1740, ack 440, win 4046, options [nop,nop,TS val 3584793729 ecr 2736785997], length 1148 09:19:28.498810 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 440:572, ack 1740, win 249, options [nop,nop,TS val 2736786000 ecr 3584793729], length 132 09:19:28.499088 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 572, win 4038, options [nop,nop,TS val 3584793730 ecr 2736786000], length 0 09:19:28.500265 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1740:1888, ack 572, win 4038, options [nop,nop,TS val 3584793732 ecr 2736786000], length 148 09:19:28.534424 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 572:672, ack 1888, win 249, options [nop,nop,TS val 2736786035 ecr 3584793732], length 100 09:19:28.534789 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 672, win 4032, options [nop,nop,TS val 3584793766 ecr 2736786035], length 0 09:19:28.536356 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1888:2004, ack 672, win 4032, options [nop,nop,TS val 3584793768 ecr 2736786035], length 116 09:19:28.579582 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 2004, win 249, options [nop,nop,TS val 2736786080 ecr 3584793768], length 0 09:19:28.602815 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 672:788, ack 2004, win 249, options [nop,nop,TS val 2736786104 ecr 3584793768], length 116 09:19:28.624811 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], seq 788:2236, ack 2004, win 249, options [nop,nop,TS val 2736786126 ecr 3584793768], length 1448 09:19:28.625489 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 2236, win 4005, options [nop,nop,TS val 3584793857 ecr 2736786104], length 0 09:19:28.625503 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 2236:2308, ack 2004, win 249, options [nop,nop,TS val 2736786126 ecr 3584793857], length 72 09:19:28.627110 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], seq 2308:3756, ack 2004, win 249, options [nop,nop,TS val 2736786128 ecr 3584793857], length 1448 09:19:28.627676 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 3756, win 4005, options [nop,nop,TS val 3584793859 ecr 2736786126], length 0 09:19:28.627678 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 3756:4340, ack 2004, win 249, options [nop,nop,TS val 2736786128 ecr 3584793859], length 584 09:19:28.631744 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 2004:2120, ack 4340, win 4005, options [nop,nop,TS val 3584793863 ecr 2736786128], length 116 09:19:28.631748 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 4340:5396, ack 2120, win 249, options [nop,nop,TS val 2736786133 ecr 3584793863], length 1056 09:19:28.643868 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], seq 2120:3568, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448 09:19:28.643941 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 3568:5016, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448 09:19:28.643947 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 5016, win 249, options [nop,nop,TS val 2736786145 ecr 3584793875], length 0 09:19:28.644030 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 5396:5512, ack 5016, win 249, options [nop,nop,TS val 2736786145 ecr 3584793875], length 116 09:19:28.644079 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], seq 5016:6464, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448 09:19:28.644181 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 6464:7912, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448 ....
So, "...let's solve it together...", please.
-
- Forum Guru
- Posts: 10209
- Joined: Mon Jun 08, 2015 10:09 am
Re: WinBox v3.40 released!
It would also be nice when there would be a possibility to connect to a router in the Addresses table without having to specify username and password.
So when you start "winbox routername" it would connect.
Now, that only works for "winbox routername username password", when used without the username and password it does correctly select the entry from the Addresses table, but it does not connect.
So when you start "winbox routername" it would connect.
Now, that only works for "winbox routername username password", when used without the username and password it does correctly select the entry from the Addresses table, but it does not connect.
-
- just joined
- Posts: 24
- Joined: Sat Apr 16, 2011 10:46 pm
-
- just joined
- Posts: 15
- Joined: Wed Dec 12, 2007 6:49 pm
Re: WinBox v3.40 released!
There seems to be a scaling bug in flood-ping in WinBox that goes back to at least v3.18.
The timeout value is in 10s of milliseconds. Min, Avg, and Max RTT are all in milliseconds.
With the default value of 1000, you'll be waiting 10 full seconds to continue from a missed ping. Just cut the value to 10 if you're expecting ping times below 100 ms.
The timeout value is in 10s of milliseconds. Min, Avg, and Max RTT are all in milliseconds.
With the default value of 1000, you'll be waiting 10 full seconds to continue from a missed ping. Just cut the value to 10 if you're expecting ping times below 100 ms.
-
- just joined
- Posts: 3
- Joined: Fri May 11, 2018 2:56 pm
- Location: Pretoria
Re: WinBox v3.40 released!
Ok, for those getting the Upgrade Error "currupt download" on OSX (Wine), open the Winbox-mac.app package contents and just replace the winbox64.exe under Resources folder.
And "Bob's your Uncle".
And "Bob's your Uncle".
-
- just joined
- Posts: 22
- Joined: Fri Oct 12, 2018 10:13 pm
Re: WinBox v3.40 released!
I have an problem with WinBox. When I use the "System / Reboot" command from the GUI, I am prompted to confirm, and I select Yes, however after the Winbox window automatically closes, I log back into the device and I see that it has not rebooted. The only way I can reboot a device using WinBox is to run the /system reboot command from a terminal window. I can reproduce this problem to show evidence it is occurring. Please advise how I can get this resolved through official support. Thank You
-
- Forum Guru
- Posts: 1526
- Joined: Thu Nov 24, 2011 12:59 pm
- Location: Kharkiv, Ukraine
Re: WinBox v3.40 released!
By contacting the "official support" first, I guess.
https://help.mikrotik.com/servicedesk/servicedesk or support@mikrotik.com
-
- Frequent Visitor
- Posts: 75
- Joined: Tue Jan 31, 2017 11:36 pm
Re: WinBox v3.40 released!
Winbox with Gcenx built wine has one big problem on Mac which screws up all field entries containing commas and periodsoptio wrote: ↑Tue Oct 10, 2023 7:06 pm Actually I'm also using CrossOver wine fork on Mac (Gcenx build), maybe with official wine it's different. Wine is supporting Windows API WinVerifyTrust, if this API is used in Winbox to verify PE certificate.
It is in attachment
Mikrotik support states that this is "not their problem". So much about great interoperability...
You do not have the required permissions to view the files attached to this post.
-
- Forum Guru
- Posts: 11986
- Joined: Tue Feb 25, 2014 11:49 am
- Location: Italy
Re: WinBox v3.40 released!
It is not MikroTik's responsibility to operate third-party software.
Did you ask Gcenx and Apple instead?
Only they at most can say something about it, not just any person passing through the forum...
It's called WinBox, not MacBox or... er... WineBox...
so if you want to run it on another platform that's your business.
Did you ask Gcenx and Apple instead?
Only they at most can say something about it, not just any person passing through the forum...
It's called WinBox, not MacBox or... er... WineBox...
so if you want to run it on another platform that's your business.
-
- MikroTik Support
- Posts: 26354
- Joined: Fri May 28, 2004 9:04 am
- Location: Riga, Latvia
Re: WinBox v3.40 released!
Don't use pre-pacaged Winbox software from 3rd party sources.
wine-8 and winbox64 works perfectly with all functionality and can self-upgrade
wine-8 and winbox64 works perfectly with all functionality and can self-upgrade
-
- Frequent Visitor
- Posts: 75
- Joined: Tue Jan 31, 2017 11:36 pm
Re: WinBox v3.40 released!
So much I can tell that problem is not present with older Wine versions (and does not seem to depend on Winbox version). It would be good to get to the root of this problem though...
-
- Forum Guru
- Posts: 11986
- Joined: Tue Feb 25, 2014 11:49 am
- Location: Italy
Re: WinBox v3.40 released!
So, more than obviously at this point, given what you write, you need to contact those who develop Wine...
-
- Frequent Visitor
- Posts: 75
- Joined: Tue Jan 31, 2017 11:36 pm
Re: WinBox v3.40 released!
Interesting thing here is that Dude does not have this problem with newest Wine engine - but Btest app does. There should be some common denominator explaining this...
-
- Frequent Visitor
- Posts: 75
- Joined: Tue Jan 31, 2017 11:36 pm
-
- Member Candidate
- Posts: 215
- Joined: Sun Jun 21, 2020 10:58 am
Re: WinBox v3.40 released!
On my Mac (M2Pro, Sonoma), winbox 3.40 runs without issues using Gcenx wine builds available atWinbox with Gcenx built wine has one big problem on Mac which screws up all field entries containing commas and periods
https://github.com/Gcenx/macOS_Wine_builds
Even winbox self update works.
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
Except it crashes on some cases viewtopic.php?t=203174#p1047711, not sure if is related to that wine build or is generally Winbox issue.
-
- Frequent Visitor
- Posts: 75
- Joined: Tue Jan 31, 2017 11:36 pm
Re: WinBox v3.40 released!
Problem is not present with 21.2.0-1 but any newer engine exposes the problem. Who knows maybe it can be related to macOS version differences (it is possible that behaviour can be different on macOS 12 on Intel machine than on newer Apple Silicon machines)...jbl42 wrote: ↑Thu Jan 11, 2024 2:39 pmOn my Mac (M2Pro, Sonoma), winbox 3.40 runs without issues using Gcenx wine builds available atWinbox with Gcenx built wine has one big problem on Mac which screws up all field entries containing commas and periods
https://github.com/Gcenx/macOS_Wine_builds
Even winbox self update works.
You do not have the required permissions to view the files attached to this post.
-
- Member Candidate
- Posts: 215
- Joined: Sun Jun 21, 2020 10:58 am
Re: WinBox v3.40 released!
I'm using wine-8.21-staging on macOS 14.2.1
Of course different macOS and wine versions might have different problems.
PS
I'm not sure what those version numbers in your screenshot are referring to. Current wine version is 8.x (9.0 is in RC state)
Of course different macOS and wine versions might have different problems.
PS
I'm not sure what those version numbers in your screenshot are referring to. Current wine version is 8.x (9.0 is in RC state)
-
- Frequent Visitor
- Posts: 75
- Joined: Tue Jan 31, 2017 11:36 pm
Re: WinBox v3.40 released!
CX21.2.0 - Wine 6.0.2
CX22.1.1 - Wine 7.7
CX23 - Wine 8.0.1
CX22.1.1 - Wine 7.7
CX23 - Wine 8.0.1
-
- just joined
- Posts: 11
- Joined: Tue Jan 09, 2024 2:34 pm
Re: WinBox v3.40 released!
It would be helpful to rewrite winbox in Java, to run it everywhere (BSD unix and Linux) with no need for a Windows virtual machine or emulator.
-
- MikroTik Support
- Posts: 26354
- Joined: Fri May 28, 2004 9:04 am
- Location: Riga, Latvia
Re: WinBox v3.40 released!
Why Java. There are better options
-
- MikroTik Support
- Posts: 26354
- Joined: Fri May 28, 2004 9:04 am
- Location: Riga, Latvia
Re: WinBox v3.40 released!
You do not have the required permissions to view the files attached to this post.
-
- Long time Member
- Posts: 654
- Joined: Thu Nov 12, 2020 11:07 am
Re: WinBox v3.40 released!
OMG - thanks for the teaser!
-
- Forum Guru
- Posts: 11986
- Joined: Tue Feb 25, 2014 11:49 am
- Location: Italy
Re: WinBox v3.40 released!
@normis, when? :))
-
- Forum Guru
- Posts: 10209
- Joined: Mon Jun 08, 2015 10:09 am
Re: WinBox v3.40 released!
What do you mean "teaser"? That is just a wine install, that has been possible for a long time.
-
- Forum Guru
- Posts: 11986
- Joined: Tue Feb 25, 2014 11:49 am
- Location: Italy
-
- Member Candidate
- Posts: 160
- Joined: Thu Jun 09, 2022 5:20 pm
Re: WinBox v3.40 released!
Look better 😛
Thanks Normis 🎉
You do not have the required permissions to view the files attached to this post.
-
- Forum Guru
- Posts: 11546
- Joined: Thu Mar 03, 2016 9:23 pm
Re: WinBox v3.40 released!
I don't understand these screenshots. They must be in macOSish. Anthing in Linuxish? 😛
-
- MikroTik Support
- Posts: 26354
- Joined: Fri May 28, 2004 9:04 am
- Location: Riga, Latvia
Re: WinBox v3.40 released!
You want too much from a teaser. Teaser makes you think. Try it.
-
- Forum Guru
- Posts: 19251
- Joined: Sun Feb 18, 2018 10:28 pm
- Location: Nova Scotia, Canada
Re: WinBox v3.40 released!
rextended you see more with one eye, than most with two eyes............
-
- Forum Guru
- Posts: 1526
- Joined: Thu Nov 24, 2011 12:59 pm
- Location: Kharkiv, Ukraine
-
- Forum Guru
- Posts: 11986
- Joined: Tue Feb 25, 2014 11:49 am
- Location: Italy
Re: WinBox v3.40 released!
For historical purposes only...
You do not have the required permissions to view the files attached to this post.
-
- Forum Guru
- Posts: 3377
- Joined: Sun May 01, 2016 5:12 pm
- Location: California
Re: WinBox v3.40 released!
Doubt it. Already 3rd parties that package wine+winbox into an Mac app to get an icon... but given @normis always note this about them it be pretty ironic:
normis wrote: Don't use pre-pacaged Winbox software from 3rd party sources.
In some older threads, there were teasers about upcoming "multiplatform client". So seemingly were at they picked an icon for it stage. ;). And, apparently it's not Java-based.
-
- Long time Member
- Posts: 654
- Joined: Thu Nov 12, 2020 11:07 am
Re: WinBox v3.40 released!
It's still called Winbox. What does the name stand for? "Box of windows?" - would at least describe the look of the application. ROFLMA
-
- Forum Guru
- Posts: 10209
- Joined: Mon Jun 08, 2015 10:09 am
Re: WinBox v3.40 released!
Actually I would prefer when changes like what I mentioned Tue Dec 12, 2023 4:15 pm are implemented (to allow connection to some device directly from a desktop icon).
And also to change the .viw files to a readable/editable format (e.g. .json)...
And also to change the .viw files to a readable/editable format (e.g. .json)...
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
"Teaser" - lol
under that...
You do not have the required permissions to view the files attached to this post.
Last edited by optio on Mon Jan 22, 2024 4:50 pm, edited 1 time in total.
-
- Forum Guru
- Posts: 3377
- Joined: Sun May 01, 2016 5:12 pm
- Location: California
Re: WinBox v3.40 released!
-
- Long time Member
- Posts: 654
- Joined: Thu Nov 12, 2020 11:07 am
Re: WinBox v3.40 released!
Indeed.no promises though.
-
- Forum Guru
- Posts: 1140
- Joined: Tue Oct 11, 2005 2:53 pm
Re: WinBox v3.40 released!
That would be truly awful.
For us using WinBox everyday, all day, it's a tool that's being opened/closed tens or even hundreds of times within the day.
The amount of computer resources and time that will be wasted waiting for java to load every time would be indescribably stupid.
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
It "just" needs rewrite to use some cross-platform GUI library like Qt or GTK.
-
- Forum Guru
- Posts: 3377
- Joined: Sun May 01, 2016 5:12 pm
- Location: California
Re: WinBox v3.40 released!
I've never understood this push to re-write winbox... This Mac user is quite happy with @optio approach — which gets an icon — and worked for years.
Guess we're closer to see where this "teaser" goes... No promises.
-
- Forum Guru
- Posts: 1140
- Joined: Tue Oct 11, 2005 2:53 pm
Re: WinBox v3.40 released!
Even so, it would not be the same UI anymore.
What I love about WinBox is the no bullshit approach to the UI. No stupid margins (ie wasted space), no useless kindergarten icons and colors everywhere, no stupid material design (or whatever the hell is google and apple push for these days), no touchscreen bs (which ruin the desktop UX).
It's a plain windows 95 era UI that's efficient, fast and to the point. No more no less.
Rewriting it using Qt or GTK, there's no way it will ever look the same again and I am fairly confident that the performance and resources requirements will be worse to achieve the same tasks...
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
I worked with Qt, it can be styled to have similar current look, https://doc.qt.io/qt-6/gallery.html. Regarding performance impact I doubt it will noticeable if developed using native Qt Widgets (unless someone is executing on 486/Pentium I machines), using QML/JS framework is different thing and it should be avoided for distribution on low performance devices. Here is comparison between both Qt frameworks. At the end KDE is built on Qt and running 27 years from now on Linux when devices wasn't that fast.
I did not work with GTK, not sure if styling can be done to look as current native windows app, but regarding performance, similar to Qt, it's native library and it's performing on Linux for 25 years.
But I can bet it's a lot of effort for MT to rewrite Winbox, so we can stick to "No promises" as stated above.
I did not work with GTK, not sure if styling can be done to look as current native windows app, but regarding performance, similar to Qt, it's native library and it's performing on Linux for 25 years.
But I can bet it's a lot of effort for MT to rewrite Winbox, so we can stick to "No promises" as stated above.
-
- Forum Guru
- Posts: 1140
- Joined: Tue Oct 11, 2005 2:53 pm
Re: WinBox v3.40 released!
Similar, but never the same.optio wrote: ↑Mon Jan 22, 2024 9:04 pm I worked with Qt, it can be styled to have similar current look, https://doc.qt.io/qt-6/gallery.html.
It will be those pesky little details that they won't be able (or not willing to put in the effort) to port the same to Qt and will ruin the everyday use and feel for us that use WinBox professionally everyday. Efficiency and muscle memory matter when using tools to perform critical tasks.
Even during WinBox 2.x to WinBox 3.x there were subtle differences that were very annoying and never got fixed/re-implemented.
Let alone writing the whole WinBox from scratch. Nothing will work ok for the better part of a decade until it's even close to what we have now.
The fact remains that it will be heavier/slower, regardless of how fast it will look/feel.optio wrote: ↑Mon Jan 22, 2024 9:04 pmRegarding performance impact I doubt it will noticeable if developed using native Qt Widgets (unless is someone is executing on 486/Pentium I machines), using QML/JS framework is different thing and it should be avoided for distribution on low performance devices. Here is comparison between both Qt frameworks. At the end KDE is built on Qt and running 27 years from now on Linux when devices wasn't that fast.
KDE did not use the same Qt that did 27 years ago. That's not an apt comparison. Would office 365 run on a Pentium as Office 1997 did?
KDE especially is a bad example. I remember the days when Plasma was released, it was a resource hog and took many many years for hardware to catch up and software to be optimized enough to run smoothly.
KDE 3.5 on the other hand was a joy to use. I miss those days when UIs were just perfect and developers didn't mess everything up on each release just for the sake of it.
Fingers crossed, they will not do anything and keep it just the (perfect) way it currently is.
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
Well you can always develop on older version library which has better performance. :)
Other solution for cross-platform native app can be that Windows GUI codebase remains same but for other platforms is using some cross-platform library for GUI rendering. That can be splitted in build time dependent for which platform build is performing, still a lot of effort to do that, I doubt we will see that.
For windows users yes, over wine is even bigger performance impact. On my Mac (M1) Winbox startup is approx. 5s (On Intel is some faster because it's not emulated) :) I'm running very heavy apps, none has that much startup time, eg. Eclipse starts much faster. Wine starts multiple processes just to run single app.
Other solution for cross-platform native app can be that Windows GUI codebase remains same but for other platforms is using some cross-platform library for GUI rendering. That can be splitted in build time dependent for which platform build is performing, still a lot of effort to do that, I doubt we will see that.
Last edited by optio on Mon Jan 22, 2024 11:10 pm, edited 10 times in total.
-
- Forum Guru
- Posts: 19251
- Joined: Sun Feb 18, 2018 10:28 pm
- Location: Nova Scotia, Canada
Re: WinBox v3.40 released!
Rhyme Disease '=)
-
- MikroTik Support
- Posts: 26354
- Joined: Fri May 28, 2004 9:04 am
- Location: Riga, Latvia
Re: WinBox v3.40 released!
Even if we make a winbox that is not the same as the good old Windows 95 inspired version, you can always just keep using the old one
-
- Forum Guru
- Posts: 11986
- Joined: Tue Feb 25, 2014 11:49 am
- Location: Italy
-
- Forum Guru
- Posts: 10209
- Joined: Mon Jun 08, 2015 10:09 am
Re: WinBox v3.40 released!
Of course until at some point the authentication or some other fundamental protocol detail is changed in some newer RouterOS version, as has happened before...
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
Like The Dude, while it works you can use it :)
-
- Forum Guru
- Posts: 1140
- Joined: Tue Oct 11, 2005 2:53 pm
Re: WinBox v3.40 released!
-
- just joined
- Posts: 10
- Joined: Wed Jan 31, 2024 9:41 am
Re: WinBox v3.40 released!
From the standpoint of the user, Winbox is a login manager, and everything shown after login comes from the device itself.
-
- Member Candidate
- Posts: 245
- Joined: Thu Nov 05, 2015 11:30 am
-
- Forum Guru
- Posts: 10209
- Joined: Mon Jun 08, 2015 10:09 am
-
- newbie
- Posts: 29
- Joined: Thu Jan 25, 2018 8:12 pm
Re: WinBox v3.40 released!
Java? Crossplatform? Really? Well, goodbye good old winbox, this will be a useless piece of bloatware crap .
Oh, I think we just need some tolerance...How about Electorn-based software? Also you need to integrate a lot of telemetry, shitty touchscreen icons, some pictures, a good donate games (i prefer one or two, but who know), Siri and Google Assistant, ChatGPT...
...And subscriptions. "You can configure routing only for 99 Eur/mo.!"
Oh, I think we just need some tolerance...How about Electorn-based software? Also you need to integrate a lot of telemetry, shitty touchscreen icons, some pictures, a good donate games (i prefer one or two, but who know), Siri and Google Assistant, ChatGPT...
...And subscriptions. "You can configure routing only for 99 Eur/mo.!"
-
- Long time Member
- Posts: 654
- Joined: Thu Nov 12, 2020 11:07 am
Re: WinBox v3.40 released!
Mikrotik, can you please take care of the following skin bug. MPLS is disabled but still shown.
But Winbox menu looks like this:
Code: Select all
{
"Mesh": 0,
"MPLS": 0,
"Dot1X": 0,
"RADIUS": 0,
"CAPsMAN": 0,
"Wireless": {
"W60G Station": 0,
"Nstreme Dual": 0,
"Channels": 0,
"Interworking Profiles": 0
},
"PPP": {
"L2TP Ethernet": 0,
"PPP Scanner": 0,
"PPTP Server": 0,
"SSTP Server": 0,
"OVPN Server": 0,
"Import .ovpn": 0,
"PPPoE Scan": 0,
"PPPoE Servers": 0,
"Secrets": 0,
"Profiles": 0,
"L2TP Secrets": 0
},
"Partition": 0,
"Make Supout.rif": 0,
"WinBox": 0,
"License": 0,
"Interfaces": {
"EoIP Tunnel": 0,
"IP Tunnel": 0,
"GRE Tunnel": 0,
"VXLAN": 0,
"VRRP": 0,
"VETH": 0,
"MACsec": 0,
"Bonding": 0,
"MACVLAN": 0
},
"System": {
"Auto Upgrade": 0,
"Disks": 0,
"Health": 0,
"License": 0,
"NTP Client": 0,
"NTP Server": 0,
"Packages": 0,
"Ports": 0,
"Reset Configuration": 0,
"Special Login": 0
},
"Tools": {
"BTest Server": 0,
"Bandwidth Test": 0,
"Email": 0,
"RoMON": 0
}
}
You do not have the required permissions to view the files attached to this post.
-
- Frequent Visitor
- Posts: 58
- Joined: Sun Nov 21, 2021 6:57 pm
Re: WinBox v3.40 released!
Two things:
How does a user identify which version of Winbox is in use? Can't find that info in Winbox itself or in Wine when executing the .exe file.
Thanks.
Download button on that page has the same URL linked, so clicking there returns to same page. No way to download Winbox.Both Winbox 32-bit and 64-bit versions are available here:
https://www.mikrotik.com/download
How does a user identify which version of Winbox is in use? Can't find that info in Winbox itself or in Wine when executing the .exe file.
Thanks.
-
- Frequent Visitor
- Posts: 58
- Joined: Sun Nov 21, 2021 6:57 pm
Re: WinBox v3.40 released!
Forget the question about the winbox version. I see it in a newly opened Winbox title bar before connecting to a router (when it shows the ROS version). I was on 3.37, downloaded the Oct '23 ver from another site which shows 3.40.
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
From WinBox menu on download page: https://mt.lv/winbox64 vs https://mt.lv/winbox - how is this same URL?ckonsultor wrote: ↑Mon Feb 19, 2024 8:48 pm Download button on that page has the same URL linked, so clicking there returns to same page. No way to download Winbox.
You cannot see that? Like on screenshot from your postckonsultor wrote: ↑Mon Feb 19, 2024 8:48 pm How does a user identify which version of Winbox is in use? Can't find that info in Winbox itself or in Wine when executing the .exe file.
You do not have the required permissions to view the files attached to this post.
Last edited by optio on Mon Feb 19, 2024 9:33 pm, edited 1 time in total.
-
- Long time Member
- Posts: 672
- Joined: Mon Dec 26, 2022 1:57 pm
Re: WinBox v3.40 released!
That's brave (or...?), running router admin software downloaded from non official siteckonsultor wrote: ↑Mon Feb 19, 2024 8:52 pm downloaded the Oct '23 ver from another site which shows 3.40.
-
- Frequent Visitor
- Posts: 58
- Joined: Sun Nov 21, 2021 6:57 pm
Re: WinBox v3.40 released!
Got a fresh download from the official site: Winbox64.
-
- just joined
- Posts: 8
- Joined: Fri Sep 25, 2015 5:52 am
Re: WinBox v3.40 released!
anyone have an issue with version 3.40 of winbox and routeros 7 when logging in the session just disconnects? this only started when I upgraded to winbox 3.4
-
- Forum Guru
- Posts: 5436
- Joined: Tue Apr 13, 2021 12:14 am
- Location: Belgium
Re: WinBox v3.40 released!
Which version of routeros ?
There have been versions (beta/rc) where this was an issue so best to make at least sure you're at the latest stable version.
If it would be a generic problem, this place would be swamped with reports which AFAIK is not the case (yet).
There have been versions (beta/rc) where this was an issue so best to make at least sure you're at the latest stable version.
If it would be a generic problem, this place would be swamped with reports which AFAIK is not the case (yet).
-
- just joined
- Posts: 2
- Joined: Tue Apr 09, 2024 6:08 am
Re: WinBox v3.40 released!
I see native WinBox on Linux in my dream when i sleep )))
-
- Long time Member
- Posts: 569
- Joined: Fri Jun 21, 2019 10:04 am
Re: WinBox v3.40 released!
Which is why IMO effort should be directed at web applications, not native apps. Having written both, I completely appreciate that writing web apps is harder although considering the last one I wrote was 10+ years ago, I would imagine the frameworks have improved massively in that time. A web interface and controller approach would solve many problems and improve sales. Sure, it would introduce some new ones but I'm not in the mood for blockers ;-)
-
- Long time Member
- Posts: 654
- Joined: Thu Nov 12, 2020 11:07 am
Re: WinBox v3.40 released!
There is already a dedicated topic for controller software: viewtopic.php?p=936086
It is not. That's why so many (including the big ones like Microsoft) used to develop Electron "desktop software". In classic software development it is "hard" to separate user interface development. In web applications you easily throw the UI part to any army of FE developers, just hand over a backend interface API documentation and you're pretty ready to go.robmaltsystems wrote: ↑Tue Apr 09, 2024 9:20 am I completely appreciate that writing web apps is harder
-
- Long time Member
- Posts: 569
- Joined: Fri Jun 21, 2019 10:04 am
Re: WinBox v3.40 released!
As I said, it is 10 years since I did any web app development and I still read CodeProject with envy as to how powerful the modern frameworks look these days. I want Mikrotik to thrive. I love the power of RouterOS but I do lose some customers to Unifi for simplicity of their cloud controller.
I'm already subscribed to that topic and the low down is AFAIK, the controller is dead. IMO management and controller are the same thing.
I'm already subscribed to that topic and the low down is AFAIK, the controller is dead. IMO management and controller are the same thing.
-
- Forum Guru
- Posts: 11546
- Joined: Thu Mar 03, 2016 9:23 pm
Re: WinBox v3.40 released!
robmaltsystems wrote: ↑Tue Apr 09, 2024 9:20 amWhich is why IMO effort should be directed at web applications, not native apps.
There's already WebFig ... functionality-wise it's on par with WinBox, so no need to re-invent the wheel.
But there's a very important difference, which can not be fixed by web app at all: WinBox can connect via MAC. And many users use WinBox because this function was a deciding point (when using it for one reason, one can use it always).
And this difference alone is the key selling point of WinBox (and also key differentiator from other vendors' management tools, not many support in-band connectivity which doesn't depend on at least half decently configured IP stack on network gadget).
-
- Long time Member
- Posts: 569
- Joined: Fri Jun 21, 2019 10:04 am
Re: WinBox v3.40 released!
>There's already WebFig ... functionality-wise it's on par with WinBox, so no need to re-invent the wheel.
There is yes but you can't access it remotely unless you set-up port forwarding or VPN. Complexity again... also, it's a per device interface, not a controller for the entire network. I'm not trying to diss it (too much) but defending the existing isn't too helpful when you're trying to think outside the existing box.
>WinBox can connect via MAC.
I agree that this is occasionally a very useful feature but could a much simpler native application act as an interface between a web app and the device? The only reason why an application running in a browser can't do the same as WinBox is because the same API isn't available. This was a generic problem with all web apps which is why Progressive Web Apps came into existence.
There is yes but you can't access it remotely unless you set-up port forwarding or VPN. Complexity again... also, it's a per device interface, not a controller for the entire network. I'm not trying to diss it (too much) but defending the existing isn't too helpful when you're trying to think outside the existing box.
>WinBox can connect via MAC.
I agree that this is occasionally a very useful feature but could a much simpler native application act as an interface between a web app and the device? The only reason why an application running in a browser can't do the same as WinBox is because the same API isn't available. This was a generic problem with all web apps which is why Progressive Web Apps came into existence.
-
- Forum Guru
- Posts: 5436
- Joined: Tue Apr 13, 2021 12:14 am
- Location: Belgium
Re: WinBox v3.40 released!
Same with Winbox.robmaltsystems wrote: ↑Tue Apr 09, 2024 1:56 pm >There's already WebFig ... functionality-wise it's on par with WinBox, so no need to re-invent the wheel.
There is yes but you can't access it remotely unless you set-up port forwarding or VPN. Complexity again.
And please don't respond you can open a port directly on your router for Winbox access. That's, how shall I say ... not smart.
-
- Forum Guru
- Posts: 11546
- Joined: Thu Mar 03, 2016 9:23 pm
Re: WinBox v3.40 released!
It would really help if you stated what are your wishes/requirements from the new web app. Because there are many things that can already be done, but using a few different tools. There's WebFig if you want to configure one device using Web browser (most home users need this). There's WinBox if you want to configure one device but have connectivity issues/requirements. There's RoMoN if you want to configure a fleet of ROS devices which can access each other (but aren't necessary accessible directly from management station). There's API which should in principle offer all management possibilities and one can build their own solution. Etc.robmaltsystems wrote: ↑Tue Apr 09, 2024 1:56 pm I'm not trying to diss it (too much) but defending the existing isn't too helpful when you're trying to think outside the existing box.
And your response to statement by @kko was very vague, but if one keeps it in context with original statement one can assume that you were talking about app which would run in linux ("natively" ... web app is not native anywhere, winbox can decently run in wine environment).
Well, normal L6 applications (e.g. web browsers) are not made to play with L2/L3 stuff. And all OSes provide such API (IP stack, ethernet sockets). There are libraries which expose that to application ... e.g. npcap, which is installed with windows wireshark and provide wireshark access to L2 of network interfaces. Turning such library into API ... IMO that's insanity (a huge can of worms in shape of security issues etc.). And I don't see browsers incorporate such library either. So you can simply forget the idea of seeing web app connect via MAC to your ROS device.robmaltsystems wrote: ↑Tue Apr 09, 2024 1:56 pm The only reason why an application running in a browser can't do the same as WinBox is because the same API isn't available. This was a generic problem with all web apps which is why Progressive Web Apps came into existence.
-
- Long time Member
- Posts: 569
- Joined: Fri Jun 21, 2019 10:04 am
Re: WinBox v3.40 released!
>So you can simply forget the idea of seeing web app connect via MAC to your ROS device.
Much the same was said about accessing cameras from web applications... never say never.
Much the same was said about accessing cameras from web applications... never say never.
-
- Long time Member
- Posts: 569
- Joined: Fri Jun 21, 2019 10:04 am
Re: WinBox v3.40 released!
>It would really help if you stated what are your wishes/requirements from the new web app.
Unifi controller for RouterOS basically.
Unifi controller for RouterOS basically.
-
- Forum Guru
- Posts: 10209
- Joined: Mon Jun 08, 2015 10:09 am
Re: WinBox v3.40 released!
No it is NOT! Work is required to bring it on par. There should be multiple windows, tabs in the windows, saved settings, etc.mkx wrote: ↑Tue Apr 09, 2024 1:46 pmrobmaltsystems wrote: ↑Tue Apr 09, 2024 9:20 am
Which is why IMO effort should be directed at web applications, not native apps.
There's already WebFig ... functionality-wise it's on par with WinBox, so no need to re-invent the wheel.
There should be a simple small portable MikroTik app (program) that you can run to:But there's a very important difference, which can not be fixed by web app at all: WinBox can connect via MAC. And many users use WinBox because this function was a deciding point (when using it for one reason, one can use it always).
- netinstall devices
- put config in new devices
- and: listen on a TCP port and translate actions to the MAC protocol.
Then you can connect via MAC also from a browser.
Preferably it would be open source so it can be installed on any device/OS the user may have.
-
- Long time Member
- Posts: 569
- Joined: Fri Jun 21, 2019 10:04 am
Re: WinBox v3.40 released!
Happened to be catching up on YouTube and came across this video by a staunch Mikrotik supporter with 222 videos mainly about Mikrotik - so you can hardly call him a hater but he felt compelled to release this video entitled "Things I don't like about MikroTik..."
https://www.youtube.com/watch?v=Z2HeQ7znKBs
He covers the subject touched on above at the very end about lack of overall management.
https://www.youtube.com/watch?v=Z2HeQ7znKBs
He covers the subject touched on above at the very end about lack of overall management.
-
- Forum Guru
- Posts: 10209
- Joined: Mon Jun 08, 2015 10:09 am
Re: WinBox v3.40 released!
Central (overall) management is the topic of another thread.
You know, one of those "we are considering, we want your input" and then you never hear from the product again.
You know, one of those "we are considering, we want your input" and then you never hear from the product again.
-
- Long time Member
- Posts: 654
- Joined: Thu Nov 12, 2020 11:07 am
Re: WinBox v3.40 released!
Of course. As soon they realize (after reading community input) it's gonna be a ton of work and a lot of expectations to meet. "Nah, better not".
-
- Long time Member
- Posts: 569
- Joined: Fri Jun 21, 2019 10:04 am
Re: WinBox v3.40 released!
I sometimes wonder, considering the philosophy of Mikrotik esp. around licensing, whether an open source approach to developing web based management tools would work? I'm semi-retiring now and I'm interested in a project although that might be something completely different like a model railway. Mikrotik control the hardware (obviously) and maybe the API on the board and an enthused team develop the rest. Just an idea. If you ever met me, you'd know I'm always looking for solutions to problems and don't like blockers.
PS. Total aside but many model railways are networked so *not* that radical a change.
PS. Total aside but many model railways are networked so *not* that radical a change.
-
- Forum Guru
- Posts: 10209
- Joined: Mon Jun 08, 2015 10:09 am
Re: WinBox v3.40 released!
Yes, you could certainly write a web management tool that performs all its actions via API. That basically is what winbox is doing as well. The winbox protocol and API probably have a lot in common. I think what winbox has extra is the capability to query the available commands and the corresponding dialog layout, and the icons. These are then stored in the version-dependent directory in the winbox application directory.
Unfortunately it seems that the winbox protocol itself (unlike the API) is not documented...
Unfortunately it seems that the winbox protocol itself (unlike the API) is not documented...
-
- Long time Member
- Posts: 569
- Joined: Fri Jun 21, 2019 10:04 am
Re: WinBox v3.40 released!
>That basically is what winbox is doing as well.
Does WinBox effectively issue CLI commands to get/set changes?
Does WinBox effectively issue CLI commands to get/set changes?
-
- Long time Member
- Posts: 654
- Joined: Thu Nov 12, 2020 11:07 am
Re: WinBox v3.40 released!
Who knows?
-
- Forum Guru
- Posts: 3296
- Joined: Sat Dec 24, 2016 10:17 am
- Location: Magrathean
Re: WinBox v3.40 released!
I would think so. If you look at command history, it looks the same if its run from Winbox or from terminal.robmaltsystems wrote: ↑Wed Apr 10, 2024 12:11 pm Does WinBox effectively issue CLI commands to get/set changes?