Community discussions

MikroTik App
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 2:13 pm

What's new in v3.34:

*) fixed WinBox crash on startup (introduced in v3.33);

What's new in v3.33:

*) added support for hex type fields;
*) enabled "Stop" button on auto start actions;
*) fixed error messages for start, stop and cancel actions;
*) fixed skin when opening in new window;
*) fixed time zone offset support for some fields;
*) improved interface name sorting;
*) properly display all packets captured by sniffer;

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
 
User avatar
Panbambaryla
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Jun 08, 2019 12:12 pm

Re: WinBox v3.33 released!

Thu Feb 10, 2022 2:37 pm

Not working (closing) on opening older router version like 6.49.2
 
eddieb
Member
Member
Posts: 322
Joined: Thu Aug 28, 2014 10:53 am
Location: Netherlands

Re: WinBox v3.33 released!

Thu Feb 10, 2022 2:42 pm

I tried to upgrade in crossover MacOS and after upgrade it does not start ...
restored previous version (bottle) thru timemachine ...
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 19099
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 2:45 pm

Seems like they forgot one! and sounds more like v6.66 ;-)
Too afraid to try it LOL.

Seriously, upgrade worked fine, no issues accessing capac/hex/rb450gx4 on 7.11 and ccr1009 on 6.48

What's new in v3.33:

*) added support for hex type fields;
*) enabled "Stop" button on auto start actions;
*) fixed error messages for start, stop and cancel actions;
*) fixed skin when opening in new window;
*) fixed time zone offset support for some fields;
*) improved interface name sorting;
*) properly display all packets captured by sniffer;

*) stops all access to router
Last edited by anav on Thu Feb 10, 2022 3:38 pm, edited 1 time in total.
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6695
Joined: Thu Mar 31, 2005 3:33 pm
Location: Riga, Latvia
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 2:46 pm

Not working (closing) on opening older router version like 6.49.2
Could you provide us with more information? What router do you use? What version? Do you use Wine (the latest one)?
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26318
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: WinBox v3.33 released!

Thu Feb 10, 2022 2:48 pm

If you use macOS, I suggest using Wine 7.1 from this installer: https://github.com/Gcenx/macOS_Wine_builds/releases
Not Crossover. That one is paid and uses a very old Wine
 
zandhaas
Frequent Visitor
Frequent Visitor
Posts: 73
Joined: Tue Dec 11, 2018 11:02 pm
Location: The Netherlands

Re: WinBox v3.33 released!

Thu Feb 10, 2022 2:51 pm

I upgraded without issues.
Everything works smooth after the upgrade.

Running WinBox on Windows 11 laptop and with RB4011 (7.2rc3), HAPac2 (7.2rc3) and RB750GR3 (7.1.2)
 
eddieb
Member
Member
Posts: 322
Joined: Thu Aug 28, 2014 10:53 am
Location: Netherlands

Re: WinBox v3.33 released!

Thu Feb 10, 2022 2:52 pm

Running Crossover on MacOS for more than 2 years without any issues, upgrading both winbox and dude-client always went smooth except now ...
 
User avatar
Panbambaryla
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Jun 08, 2019 12:12 pm

Re: WinBox v3.33 released!

Thu Feb 10, 2022 3:02 pm

Not working (closing) on opening older router version like 6.49.2
Could you provide us with more information? What router do you use? What version? Do you use Wine (the latest one)?
Windows 10 x64, WinBox x64, RB4011iGS+, RouterOS v6.49.2
Interesting thing happens - when I first open another 7.0 RouerOS device (via VPN) it can connect to local RB4011iGS+. When I start WinBOX and right after that try to connect - it closes unexpectedly.
Last edited by Panbambaryla on Thu Feb 10, 2022 5:24 pm, edited 1 time in total.
 
User avatar
woland
Member Candidate
Member Candidate
Posts: 258
Joined: Mon Aug 16, 2021 4:49 pm

Re: WinBox v3.33 released!

Thu Feb 10, 2022 3:21 pm

Hi,
just a quick report for Linux (Ubuntu 21.10, Wine 5.0.3): 7.2rc3 on CRS305 works. hAP Mini with 6.49.2 via MAC adress works as well.
No more devices here to try, but looks like there are no issues on Linux.

BR
Woland
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6695
Joined: Thu Mar 31, 2005 3:33 pm
Location: Riga, Latvia
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 3:25 pm


Could you provide us with more information? What router do you use? What version? Do you use Wine (the latest one)?
Windows 10 x64, WinBox x64, RB4011iGS+, RouterOS v6.49.2
Interesting this happens - when firt opene another 7.0 RouerOS device (via VPN) I can connect to local RB4011iGS+. When I start WinBOX and right after that try to connect - it closes unexpectedly.
Are you able to repeat it more than once?
 
User avatar
Panbambaryla
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Jun 08, 2019 12:12 pm

Re: WinBox v3.33 released!

Thu Feb 10, 2022 3:31 pm

Windows 10 x64, WinBox x64, RB4011iGS+, RouterOS v6.49.2
Interesting this happens - when firt opene another 7.0 RouerOS device (via VPN) I can connect to local RB4011iGS+. When I start WinBOX and right after that try to connect - it closes unexpectedly.
Are you able to repeat it more than once?
Yes, happens every time I run the WInBOX again when it closes. I use master password and Open In New Windows option. I have cleared WinBox cache. No Event log entry.
 
User avatar
SirPrikol
newbie
Posts: 28
Joined: Wed Oct 11, 2017 12:36 pm

Re: WinBox v3.33 released!

Thu Feb 10, 2022 3:50 pm

Not work on Windows XP
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26318
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:03 pm

How can you worry about winbox, if you have a time machine!
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:18 pm

How can you worry about winbox, if you have a time machine!
When you have a time machine, you can move yourself to a time where you have a feature-complete and basic-bugs-free v7.x version and connect your winbox to that...
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:22 pm

Wine 6 (Crossover 21) - WinBox 3.33 doesn't start. If you're ready to provide 64-bit The Dude version to run on MacOS in Wine directly, without Crossover - I'm ready to switch to Wine 7 :)
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26318
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:23 pm

Dude has been discontinued (again)
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:25 pm

For anyone looking for previous version of WinBox: https://download.mikrotik.com/winbox/3.32/winbox64.exe
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:25 pm

Dude has been discontinued (again)
That doesn't mean it became unusable
 
User avatar
memelchenkov
Member Candidate
Member Candidate
Posts: 202
Joined: Sun Oct 11, 2020 12:00 pm
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:28 pm

For anyone looking for previous version of WinBox: https://download.mikrotik.com/winbox/3.33/winbox64.exe
There should be 3.32: https://download.mikrotik.com/winbox/3.32/winbox64.exe

PS: fix 3.33 for Crossover, please, there is a demand.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:30 pm

Correct. Of course I found the URL, copied it and changed only in my browser, not while posting here :D
 
User avatar
Campano
Frequent Visitor
Frequent Visitor
Posts: 63
Joined: Mon Apr 17, 2006 2:35 am
Location: Ñuñoa - Chile
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:37 pm

Dude has been discontinued (again)
Hi Normis, how is that's? Mikrotik's have in mind a replacement?
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26318
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:42 pm

We have not done work on the Dude for some time now. If it works for you, great, you can use it. But there is no active development on the Dude at the moment. It may resume in the future, it's not known.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:44 pm

Mikrotik's have in mind a replacement?
For monitoring it probably always was better to use one of the existing generic solutions that you run on an external system. Maybe on a container when that is re-introduced.
Still it would be nice when there was a MikroTik-supported tool for centralized management of a group of routers, much like CAPsMAN manages a group of access points.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:47 pm

If it works for you, great, you can use it.
That's what we do. Using Crossover 21 (a free one). Please make WinBox run in it again. I doubt you need Wine 7 for hex fields or something else from v3.33...
 
infabo
Long time Member
Long time Member
Posts: 617
Joined: Thu Nov 12, 2020 12:07 pm

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:50 pm

3.33 works fine on Linux and Wine. Thanks!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26318
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: WinBox v3.33 released!

Thu Feb 10, 2022 4:55 pm

Winbox 3.34 incoming, will fix Wine 6.0.2 which Crossover also uses. Any minute now. We will not test Windows XP. May it rest in pieces.
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 5:44 pm

What's new in v3.34:

*) fixed WinBox crash on startup (introduced in v3.33);
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3250
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: WinBox v3.33 released!

Thu Feb 10, 2022 5:49 pm

We have not done work on the Dude for some time now. If it works for you, great, you can use it. But there is no active development on the Dude at the moment. It may resume in the future, it's not known.
Does this mean we should not plan to see a dude package for V7? Last I'd heard in Sept you'd said
Yes, we are working on it, it will be made
 
infabo
Long time Member
Long time Member
Posts: 617
Joined: Thu Nov 12, 2020 12:07 pm

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 5:53 pm

These critical fixes ship fast recently.
 
User avatar
prislonsky
just joined
Posts: 1
Joined: Tue Sep 18, 2018 1:05 pm
Location: Ukraine
Contact:

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 5:59 pm

Win11+Winbox3.33-3.34 - crash on connect to device. 3.32 - working fine
 
User avatar
Panbambaryla
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Jun 08, 2019 12:12 pm

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 6:00 pm

What's new in v3.34:
*) fixed WinBox crash on startup (introduced in v3.33);
Unfortunately, didn't help in my case. 3.32 is working fine. Give my some debug switch I will use to send you log.
 
User avatar
fposavec
newbie
Posts: 33
Joined: Thu Apr 21, 2011 12:59 pm
Location: Čakovec
Contact:

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 6:01 pm

Win11+Winbox3.33-3.34 - crash on connect to device. 3.32 - working fine
same here
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7041
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 6:03 pm

Works for me on win11, maybe try to clear cache and connect to the router with empty session (not saved)
 
User avatar
fposavec
newbie
Posts: 33
Joined: Thu Apr 21, 2011 12:59 pm
Location: Čakovec
Contact:

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 6:06 pm

Works for me on win11, maybe try to clear cache and connect to the router with empty session (not saved)
clear cache did not work, or not connectet device
 
User avatar
SirPrikol
newbie
Posts: 28
Joined: Wed Oct 11, 2017 12:36 pm

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 6:12 pm

3.34 not work too
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 6:15 pm

Wine is back online :) Thanks!
 
User avatar
prislonsky
just joined
Posts: 1
Joined: Tue Sep 18, 2018 1:05 pm
Location: Ukraine
Contact:

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 6:15 pm

Works for me on win11, maybe try to clear cache and connect to the router with empty session (not saved)
Clearing the sessions folder helped me
Thank you
 
User avatar
memelchenkov
Member Candidate
Member Candidate
Posts: 202
Joined: Sun Oct 11, 2020 12:00 pm
Contact:

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 6:23 pm

What's new in v3.34:

*) fixed WinBox crash on startup (introduced in v3.33);
Thank you!
 
eddieb
Member
Member
Posts: 322
Joined: Thu Aug 28, 2014 10:53 am
Location: Netherlands

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 6:39 pm

3.34 is running on crosover 21 on MacOS !

I am very sad to read that the dude is discontinued ...
this really fine product deserves way better !!!
 
apestalménos
just joined
Posts: 14
Joined: Wed Sep 16, 2020 8:22 pm

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 6:46 pm

3.34 - Linux - Wine --> no issues.
 
r00t
Long time Member
Long time Member
Posts: 672
Joined: Tue Nov 28, 2017 2:14 am

Re: WinBox v3.33 released!

Thu Feb 10, 2022 7:08 pm

Not work on Windows XP
I got worried as I use small rugged milspec notebook that's great for field work, but super slow under win7, so still running XP on it. And just tested 3.34 and it works fine on XP here, no problems.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 7:12 pm

Unfortunately this bug introduced in 3.32 was not fixed:
Before, the QuickSet page on a wireless link (e.g. LHG) showed the signal strength over time graph when the link is up.
This no longer works.
Last edited by pe1chl on Fri Feb 11, 2022 1:13 am, edited 2 times in total.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 released!

Thu Feb 10, 2022 7:17 pm

I got worried as I use small rugged milspec notebook that's great for field work, but super slow under win7, so still running XP on it.
I have an old scrapped laptop that I use to netinstall routers and import config from empty (MAC connect) and it has Windows XP as well...
When that stops working I guess I will have to do it from Linux.
 
User avatar
Panbambaryla
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Jun 08, 2019 12:12 pm

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 7:41 pm

Works for me on win11, maybe try to clear cache and connect to the router with empty session (not saved)
Clearing cache didn't help either...
Windows 10 x64, WinBox 3.34 x64, this time: hAP ac^3 with 6.49.2 (stable).
 
User avatar
Panbambaryla
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Jun 08, 2019 12:12 pm

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 7:52 pm

Works for me on win11, maybe try to clear cache and connect to the router with empty session (not saved)
Clearing cache didn't help either...
Windows 10 x64, WinBox 3.34 x64, this time: hAP ac^3 with 6.49.2 (stable).
Just upgraded the router to 7.1.2 and WinBox 3.34 x64 is working fine with the same device.
 
User avatar
k6ccc
Forum Guru
Forum Guru
Posts: 1490
Joined: Fri May 13, 2016 12:01 am
Location: Glendora, CA, USA (near Los Angeles)
Contact:

Re: WinBox v3.33 and v3.34 released!

Thu Feb 10, 2022 9:08 pm

Crashes every time as soon as I hit "Connect" to connect to my RB-4011 running 6.48.3 from either a Windows Server 2019 and also from a Windows 10 desktop.
3.32 working fine.
 
User avatar
Campano
Frequent Visitor
Frequent Visitor
Posts: 63
Joined: Mon Apr 17, 2006 2:35 am
Location: Ñuñoa - Chile
Contact:

Re: WinBox v3.33 released!

Thu Feb 10, 2022 9:54 pm

We have not done work on the Dude for some time now. If it works for you, great, you can use it. But there is no active development on the Dude at the moment. It may resume in the future, it's not known.
Tks 4 the info
 
zerospace
just joined
Posts: 10
Joined: Tue May 12, 2020 5:39 pm
Location: Serbia

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 1:45 am

Just updated to 3.34 and it closes when I click connect :( HAP ac2 with 6.49.2 RouterOS.
Is it possible to download 3.32?
 
User avatar
k6ccc
Forum Guru
Forum Guru
Posts: 1490
Joined: Fri May 13, 2016 12:01 am
Location: Glendora, CA, USA (near Los Angeles)
Contact:

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 1:53 am

Is it possible to download 3.32?
There is a reason why I just rename the old version to something else before adding a new version. For example, before adding 3.34 to my Program Files \ Mikrotik directory, I renamed the previous Winbox64.exe to Winbox64_3.32.exe

Although I did go through and delete a bunch of the old versions a few months ago, I always have at least the past several versions.

If you don't come up with a better solution, I can E-Mail an older version to you.
 
zerospace
just joined
Posts: 10
Joined: Tue May 12, 2020 5:39 pm
Location: Serbia

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 2:08 am

Found it in post 18 viewtopic.php?t=183119#p912088 waiting for 3.35 :)
 
RafGan
newbie
Posts: 29
Joined: Mon Jun 06, 2011 6:17 pm
Location: Poland / Silesia

Re: WinBox v3.33 released!

Fri Feb 11, 2022 3:43 am

We have not done work on the Dude for some time now. If it works for you, great, you can use it. But there is no active development on the Dude at the moment. It may resume in the future, it's not known.
So, what for I have bought RB1100x4DUDE EDITION ebaut one year ago??? Tell your boss, that this is stupid!
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3250
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: WinBox v3.33 released!

Fri Feb 11, 2022 4:06 am

So, what for I have bought RB1100x4DUDE EDITION ebaut one year ago??? Tell your boss, that this is stupid!
Maybe they should at least update the www.mikrotik.com website... https://mikrotik.com/thedude says
"The Dude network monitor is a new application by MikroTik which can dramatically improve the way you manage your network environment."
– nowhere does it say
Dude has been discontinued (again)
I'd have to agree that isn't fair to a buyer of a product called the "Dude Edition" that ships with "discontinued" software. I also have several of them, and been waiting on V7 Dude server to rollout V7 more fully, so this was a unwelcome surprise today.
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 9:36 am

To everyone experiencing unexpected crashes when connecting to a device: try connecting to the same device with session: <none>. If it does not crash when using <none> session, please send us the previously used (the one that is crashing) .viw session file. You can select a different session when "Advanced mode" is selected under Tools. .viw files are stored in your user's AppData\Roaming\Mikrotik\Winbox\sessions directory.
 
User avatar
Panbambaryla
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Jun 08, 2019 12:12 pm

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 9:58 am

To everyone experiencing unexpected crashes when connecting to a device: try connecting to the same device with session: <none>. If it does not crash when using <none> session, please send us the previously used (the one that is crashing) .viw session file. You can select a different session when "Advanced mode" is selected under Tools. .viw files are stored in your user's AppData\Roaming\Mikrotik\Winbox\sessions directory.
Windows 10 x64, WinBox 3.34 x64, this time: hAP ac^3 with 6.49.2 (stable).
a few minutes later:
just upgraded the router to 7.1.2 and WinBox 3.34 x64 is working fine with the same device.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3291
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 10:59 am

I did just take a look at release history of Winbox 3.x since first release in 2015. It's a very clear trend that Winbox upgrade are released in bulk at same short time periods. Then it can goes up to nearly 1 year without new version. Maybe some more testing before release should be a good thing. :)
 
User avatar
vecernik87
Forum Veteran
Forum Veteran
Posts: 882
Joined: Fri Nov 10, 2017 8:19 am

Re: WinBox v3.33 released!

Fri Feb 11, 2022 11:24 am

Dude has been discontinued (again)
That doesn't mean it became unusable
Actually yes, it does. For several years I am waiting for fix of the bug which disconnects my dude client everytime I hover mouse on top of monitored device as well as most of the time (but not always) when I open details. I essentially can't edit most devices. I have to delete it and create a new one (which loses all the history of course). Some properties can be edited via winbox but not all of them. Observing charts and adding/removing services can be done via Services screen.

New devices usually work fine for a while (I can even hover mouse on top of them) but within one or two outages they break and start triggering this bug as well.

If your installation of TheDude does not behave this way, you are lucky. But not all of us are. And if the suggestion is to delete the whole database and start from complete scratch, then I can as well use some other solution because amount of effort to rebuild everything will be equal (and there will be future support and development)
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 11:40 am

I did just take a look at release history of Winbox 3.x since first release in 2015. It's a very clear trend that Winbox upgrade are released in bulk at same short time periods. Then it can goes up to nearly 1 year without new version. Maybe some more testing before release should be a good thing. :)
And reading of the release topic of the previous version to at least fix the newly introduced bugs in that version... :-)
 
User avatar
prislonsky
just joined
Posts: 1
Joined: Tue Sep 18, 2018 1:05 pm
Location: Ukraine
Contact:

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 12:07 pm

To everyone experiencing unexpected crashes when connecting to a device: try connecting to the same device with session: <none>. If it does not crash when using <none> session, please send us the previously used (the one that is crashing) .viw session file. You can select a different session when "Advanced mode" is selected under Tools. .viw files are stored in your user's AppData\Roaming\Mikrotik\Winbox\sessions directory.
The problem with version 3.34 appears on Windows systems with multiple monitors and the "Open In New Window"option enabled
 
User avatar
vecernik87
Forum Veteran
Forum Veteran
Posts: 882
Joined: Fri Nov 10, 2017 8:19 am

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 12:12 pm

excellent point @prislonsky! And not even multiple monitors are needed. I am on a desktop which has only one screen (and afaik never had more than one) and logging in while "open in new window" is enabled makes winbox crash/disappear.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 12:28 pm

Ah ok that explains why I do not see it, I had that option disabled immediately as I find it irritating...
 
User avatar
leoktv
Trainer
Trainer
Posts: 144
Joined: Thu Dec 01, 2005 1:39 pm
Location: sweden
Contact:

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 3:03 pm

problem to conect not solved 3.34 tested agains ccr2004-1G-12S+2xs and CRS328-24p both running 6.49.2.... it is broken if open in new window is enabled!!!
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 4:05 pm

Tested v3.34 on a couple of Routers with different versions and it seems to be working just fine.. ( windows 10 )
 
User avatar
slimmerwifi
just joined
Posts: 17
Joined: Tue Aug 01, 2017 6:05 pm
Location: Netherlands

Re: WinBox v3.33 released!

Fri Feb 11, 2022 4:50 pm

Not working (closing) on opening older router version like 6.49.2
Could you provide us with more information? What router do you use? What version? Do you use Wine (the latest one)?
3.33 and 3.34 close instantly with CCR1009 sessions, also when set to <none>, also after clearning appdata. Using Windows 11. 3.32 works fine.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 4:54 pm

And what about unchecking "open in new window" in the open dialog?
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: WinBox v3.33 released!

Fri Feb 11, 2022 4:56 pm

3.33 and 3.34 close instantly with CCR1009 sessions, also when set to <none>, also after clearning appdata. Using Windows 11. 3.32 works fine.
Tested on a CCR1009-7G-1C-1S+ and i had no issue...
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: WinBox v3.33 and v3.34 released!

Fri Feb 11, 2022 5:00 pm

And what about unchecking "open in new window" in the open dialog?
Just tested and "open in new window" does not always work... If that is what you mean...
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: WinBox v3.33 released!

Fri Feb 11, 2022 5:27 pm


That doesn't mean it became unusable
Actually yes, it does. For several years I am waiting for fix of the bug which disconnects my dude client everytime I hover mouse on top of monitored device as well as most of the time (but not always) when I open details.
You mean, all those years it was working fine, and now when they decided to deprecate it - it broke?
 
mikrotikedoff
newbie
Posts: 29
Joined: Mon Nov 06, 2017 7:27 pm

Re: WinBox v3.33 and v3.34 released!

Sat Feb 12, 2022 1:39 am

Wow. Okay, so you're discontinuing the Dude. It could be argued that disclosing the discontinuation of that solely by the forums is irresponsible, but whatever. The problem now is that you STILL have the 1100 Dude Edition listed as a current product. You are literally selling people a false bill of goods by leaving the promotional material for that product as is. That needs to be moved to the archived product category immediately. Allowing it to continue to be sold under the false pretext that you currently are is inarguably deceptive and dishonest.
 
RafGan
newbie
Posts: 29
Joined: Mon Jun 06, 2011 6:17 pm
Location: Poland / Silesia

Re: WinBox v3.33 and v3.34 released!

Sat Feb 12, 2022 2:06 am

Wow. Okay, so you're discontinuing the Dude. It could be argued that disclosing the discontinuation of that solely by the forums is irresponsible, but whatever. The problem now is that you STILL have the 1100 Dude Edition listed as a current product. You are literally selling people a false bill of goods by leaving the promotional material for that product as is. That needs to be moved to the archived product category immediately. Allowing it to continue to be sold under the false pretext that you currently are is inarguably deceptive and dishonest.
Let MT only recompile to v7 The Dude as is now and, I think, Dude users will not be angry so much.
 
mikrotikedoff
newbie
Posts: 29
Joined: Mon Nov 06, 2017 7:27 pm

Re: WinBox v3.33 and v3.34 released!

Sat Feb 12, 2022 3:02 am

That's ridiculous, with no development for all you know the very next release could leave the dude permanently broken and who knows how long till some CVE pops up with it and it becomes an unpatched attack vector? With no development going into the dude creating a situation where it can no longer be relied on the only professional and responsible option is to start moving towards removing it completely from production environments BEFORE it becomes a problem.
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 19099
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: WinBox v3.33 and v3.34 released!

Sat Feb 12, 2022 5:12 am

No issues with either 3.33 or 3.34 on my vintage windows 8.1, smooth baby...... [ two screens ]
Last edited by anav on Sat Feb 12, 2022 2:44 pm, edited 1 time in total.
 
r00t
Long time Member
Long time Member
Posts: 672
Joined: Tue Nov 28, 2017 2:14 am

Re: WinBox v3.33 and v3.34 released!

Sat Feb 12, 2022 5:45 am

There really needs to be some official statement on DUDE from Mikrotik. All this silence for months, then such simple reply in completely unrelated thread... This is not how professional company communicates with it's customers! If it's not supported anymore, say it clearly on the website. Is the development paused? Do you ever plan to develop it in the future? Or it's just serious bugfix only? For how long? Or completely abandoned? We need some answers please!

Seriously, Mikrotik, your outside marketing and messaging is ATROCIOUS and WORST of any networking company I know of, just hire someone who can do better job or really make some changes.. as right now your (in)actions are just damaging any remaining reputation your brand still have left...
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Sat Feb 12, 2022 12:50 pm

*) properly display all packets captured by sniffer;
It is only a partial success.
When the sniffer is running and the Packets window is opened, the packets already received are properly displayed.
But the new packets arriving and being added to the window are not, they still show the :: address and missing protocol and port numbers!
 
sid5632
Long time Member
Long time Member
Posts: 553
Joined: Fri Feb 17, 2017 6:05 pm

Re: WinBox v3.33 released!

Sat Feb 12, 2022 2:39 pm

We have not done work on the Dude for some time now. If it works for you, great, you can use it. But there is no active development on the Dude at the moment. It may resume in the future, it's not known.
If MikroTik is not interested any more, please can you just open source it and let the community who use it fix it. Or at least allow an interested set of developers to sign up for restricted access if that suits you better. But don't just sit on it for ever, in its current fragile/buggy/unsuable state, with nothing happening at all. This has been going on for far too long already.
It deserves better.
 
User avatar
Panbambaryla
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Jun 08, 2019 12:12 pm

Re: WinBox v3.33 and v3.34 released!

Sat Feb 12, 2022 5:26 pm

Guys, stop this BS about DUDE in WinBox thread.
 
sid5632
Long time Member
Long time Member
Posts: 553
Joined: Fri Feb 17, 2017 6:05 pm

Re: WinBox v3.33 and v3.34 released!

Sat Feb 12, 2022 5:49 pm

It's not "BS" and anyway it was normis who started it in this thread.
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3250
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: WinBox v3.33 and v3.34 released!

Sat Feb 12, 2022 6:27 pm

Certainly EOL'ing a product in a forum post is pretty ridiculous – especially when it conflicts with comments 6 months ago in the topic Dude for v7.1? stating "Yes, we are working on it, it will be made". I hope Mikrotik can clarify re dude BUT not sure this topic (or even this forum) is the best place for that.

But on winbox topic, I notice that in v3.34 using with Mac/wine/winbox, Command-V now works to "Paste" - which is great! But Command-C still doesn't work, since it's different than Ctrl-C, is there a way to some allow/re-map Command-C to "Copy" (while leaving Ctrl-C for interrupt) on Mac/wine/winbox?
 
AlexanderM
just joined
Posts: 7
Joined: Wed Sep 24, 2014 9:06 am

Re: WinBox v3.33 and v3.34 released!

Sat Feb 12, 2022 11:53 pm

I had some bad experiences with winbox 3.34.
I accidentally upgraded my winbox by clicking upgrade by mistake.
There was no "crash on startup." as in 3.33. However, there was a crash on connecting!

The results was reproduceable on both Windows and Linux (wine). I am posting the wine log:
creating Window Class routeros_null
creating Window Class routeros_connect
DPI=96
EMS=13
ERROR: bad bmp format id=2329
biPlanes=1, biBitCount=1, biCompression=0
ERROR: bad bmp format id=3329
biPlanes=1, biBitCount=1, biCompression=0
creating Window Class routeros_dbl_canvas
rescaleDPI starting-dpi=96, zoom=0 result=96
 discovery started
rescaning
connecting to XXXXXXXX
connecting to XXXXXXXX
loadConfig Z:\home\XXXXXXXX\MikroTik\Addresses.cdb
ConnectWindow::onConnect
discovery stopped
startKeyExchange
sending first challenge
recvd peer challenge 49
recvd response

ACCESS VIOLATION EXCEPTION at address: _ 4eac74

eip=_ 4eac74 eflags=__ 10202
edi=_____ ef esi=_ 232b20 ebp=_ 7be868 esp=_ 7be810
eax=_______0 ebx=_ 232a48 ecx=_____ 16 edx=_ 247f08

winbox version: 3.34

backtrace:
7b035145 
7b46d890 
7bcb3f19 
7bcb3eeb 
7bcafc73 
7bcafffc 
7bcb24cb 
deadbabe 
_ 43c28f 
_ 42c852 
_ 42f693 
7f42b5fc 
7f42bc6d 
7f42dec3 
7f3f366e 
_ 42bd52 
_ 4b4ce1 
_ 51ea3d 
_ 401386 
7b454882 
7b454cfc 
7b45488e 


stack:
_____ 16 _____ 16 _ 7be828 7f178bd0 _ 23a2c0 _ 23a368 _ 7be868 _ 4c6488 
_ 24b2a0 _ 245bc0 _ 7be858 792b6500 _ 24b2a0 _______2 _ 246610 _ 24666c 
_ 24b2a0 _____ ef _ 7be8b8 _ 23a2b8 _ 24b2a0 _____ ef _ 7be8b8 _ 43c28f 
_ 246430 _____ ef _____ 18 7f41a642 _ a3ffb8 _ 7be8dc _ 7be898 _ 246430 

linked to KERNEL32!
modules:
_ 400000    winboxfrh.exe
7bc30000    ntdll.dll
7b420000    kernel32.dll
7b020000    kernelbase.dll
7f740000    ADVAPI32.dll
7f5c0000    COMCTL32.DLL
7f390000    user32.dll
7f220000    gdi32.dll
7ffd0000    version.dll
7f150000    msvcrt.dll
7f0e0000    usp10.dll
7f0c0000    imm32.dll
7ef80000    COMDLG32.DLL
7e580000    shell32.dll
7e500000    shlwapi.dll
7e4d0000    shcore.dll
7e390000    ole32.dll
7e2d0000    rpcrt4.dll
7e270000    winspool.drv
7e180000    CRYPT32.dll
7e150000    bcrypt.dll
7e0d0000    dbghelp.dll
7e060000    IPHLPAPI.DLL
7dfc0000    WININET.DLL
7df80000    mpr.dll
7df50000    ws2_32.dll
7df10000    WINTRUST.dll
7dc20000    winex11.drv
7d6e0000    setupapi.dll
7d580000    uxtheme.dll

code:
8b 50 0c 39 50 08 74 17 83 c0 08 c7 04 24 fe 03
 
AlexanderM
just joined
Posts: 7
Joined: Wed Sep 24, 2014 9:06 am

Re: WinBox v3.33 and v3.34 released!

Sun Feb 13, 2022 12:08 am

Some information:

1. The crash happens after successful authorization, almost at the end of the process.
2. All of the devices were running the last bugfix version. Most of them was:
       routerboard: yes
             model: CCR1072-1G-8S+
     serial-number: XXXXXX
     firmware-type: tilegx
  factory-firmware: 6.44.3
  current-firmware: 6.48.6
  upgrade-firmware: 6.48.6
  
         routerboard: yes
             model: CRS326-24S+2Q+
     serial-number: XXXXXX
     firmware-type: qca9531L
  factory-firmware: 6.45.1
  current-firmware: 6.47.10
  upgrade-firmware: 6.47.10

  
  
3. The winbox upgrade process destroys the old executable without making a backup!
4. I found no official link for downloading old versions on HTTP://mt.lv.
5. I found no official checksums for old releases to verify the 3rd party sources.

It was my mistake to click the upgrade button. I usually use the dialog for information only and upgrade manually.
However, losing the primary tool for controlling over $40 000 of routers and switches with a single update was more than ridiculous.
I guess you can at least post an archive of the old versions and make a backup of the executable as part of the upgrade process, just in case.
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: WinBox v3.33 and v3.34 released!

Sun Feb 13, 2022 12:25 am

The official download link for the older 3.32 vesion was posted above viewtopic.php?t=183119#p912088
I'm sure that someone that manages 40k $ worth of equipment can figure out something so simple.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Sun Feb 13, 2022 12:17 pm

Where is that "upgrade button" that everyone is talking about? I cannot find that anywhere in winbox, only in the routers themselves.
Maybe that is because I am not that stupid to run winbox as an administrator?
 
holvoetn
Forum Guru
Forum Guru
Posts: 5403
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: WinBox v3.33 and v3.34 released!

Sun Feb 13, 2022 12:28 pm

Where is that "upgrade button" that everyone is talking about? I cannot find that anywhere in winbox, only in the routers themselves.
Maybe that is because I am not that stupid to run winbox as an administrator?
Before connecting to any router.
Winbox - Menu - Tools - Check for updates

Is it that you're referring to ?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Sun Feb 13, 2022 1:05 pm

Ah now I see it is an entry in the Tools menu of that window. Not what I would call an "upgrade button", not in plain sight for everyone to click (like the "check for updates" button on Quick Set), and it would not work on my system anyway as the user running winbox has no permission to overwrite it.
 
User avatar
k6ccc
Forum Guru
Forum Guru
Posts: 1490
Joined: Fri May 13, 2016 12:01 am
Location: Glendora, CA, USA (near Los Angeles)
Contact:

Re: WinBox v3.33 and v3.34 released!

Sun Feb 13, 2022 8:37 pm

Confirmed on both my Windows 10 desktop (two monitors) and Windows Server 2019 (one monitor), that 3.34 crashes upon connection if using the "Open in New Window" checkbox when connecting to my RB4011 that has RoS 6.48.3. However if the "Open in New Window" is NOT checked, it works fine.

One more tidbit. WinBox actually has to connect and open the new window before it crashes. When I first tried from the Windows 10 desktop with New Window checked, I fat-fingered the password, so instead of the new window, I just got the password error. Additionally when connecting from the Windows 10 desktop which is at work, I have to use a port knock in order to get the WinBox port opened. I tried to connect before using the port knock, and of course could not connect, but WinBox did not crash.
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: WinBox v3.33 and v3.34 released!

Sun Feb 13, 2022 8:44 pm

Confirmed on both my Windows 10 desktop (two monitors) and Windows Server 2019 (one monitor), that 3.34 crashes upon connection if using the "Open in New
Had same issue as well... Both on a two monitor computer but on my laptop as well...
Open in new window unfortunately does not work...
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Sun Feb 13, 2022 10:00 pm

Instead of "Open in new window" I just open it without that option, then to open another one I click "New winbox" and I get the selection dialog to open another.
Have always done it that way before that open in new window option was added, and remain doing so because then I do not have the lingering selection window.
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: WinBox v3.33 and v3.34 released!

Sun Feb 13, 2022 11:22 pm

Personally i use the Open in New window Feature... It makes things easier in many situations...
 
sinisa
just joined
Posts: 23
Joined: Sun Apr 17, 2011 12:46 am

Re: WinBox v3.33 and v3.34 released!

Mon Feb 14, 2022 9:55 am

Instead of "Open in new window" I just open it without that option, then to open another one I click "New winbox" and I get the selection dialog to open another.
Have always done it that way before that open in new window option was added, and remain doing so because then I do not have the lingering selection window.
I have reported something similar a month ago, but now it'd officially a problem because WIINE 7 is recommended by Mikrotik:
This is not specific to this version od Winbox, also happens with older versions: with new version of Wine, Winbox cannot connect to router if option "Open In New Window" is checked.

To be more precise, Winbox CAN connect, but only after 30 seconds.
On first attempt, it seems like Winbox does not accept a packet from router, waits for 30 seconds, then successfully "reconnects":
08:42:27.311981 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [S], seq 3315150246, win 32120, options [mss 1460,sackOK,TS val 1039955570 ecr 0,nop,wscale 8], length 0
08:42:27.312248 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [S.], seq 2020679341, ack 3315150247, win 65160, options [mss 1460,sackOK,TS val 1453762216 ecr 1039955570,nop,wscale 4], length 0
08:42:27.312279 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [.], ack 1, win 126, options [nop,nop,TS val 1039955570 ecr 1453762216], length 0
08:42:27.327246 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [P.], seq 1:42, ack 1, win 126, options [nop,nop,TS val 1039955585 ecr 1453762216], length 41
08:42:27.327456 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [.], ack 42, win 4070, options [nop,nop,TS val 1453762232 ecr 1039955585], length 0
08:42:27.376476 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [P.], seq 1:52, ack 42, win 4070, options [nop,nop,TS val 1453762281 ecr 1039955585], length 51
08:42:27.376502 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [.], ack 52, win 126, options [nop,nop,TS val 1039955634 ecr 1453762281], length 0
08:42:27.380553 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [P.], seq 42:76, ack 52, win 126, options [nop,nop,TS val 1039955638 ecr 1453762281], length 34
08:42:27.380732 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [.], ack 76, win 4068, options [nop,nop,TS val 1453762285 ecr 1039955638], length 0
08:42:27.408178 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [P.], seq 52:86, ack 76, win 4068, options [nop,nop,TS val 1453762312 ecr 1039955638], length 34
08:42:27.408210 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [.], ack 86, win 126, options [nop,nop,TS val 1039955666 ecr 1453762312], length 0
08:42:27.408521 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [P.], seq 76:176, ack 86, win 126, options [nop,nop,TS val 1039955666 ecr 1453762312], length 100
08:42:27.408684 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [.], ack 176, win 4062, options [nop,nop,TS val 1453762313 ecr 1039955666], length 0
08:42:27.410563 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [P.], seq 86:282, ack 176, win 4062, options [nop,nop,TS val 1453762315 ecr 1039955666], length 196
08:42:27.410579 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [.], ack 282, win 126, options [nop,nop,TS val 1039955668 ecr 1453762315], length 0
08:42:27.410858 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [P.], seq 176:276, ack 282, win 126, options [nop,nop,TS val 1039955668 ecr 1453762315], length 100
08:42:27.411033 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [.], ack 276, win 4056, options [nop,nop,TS val 1453762315 ecr 1039955668], length 0
08:42:27.411946 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [P.], seq 282:382, ack 276, win 4056, options [nop,nop,TS val 1453762316 ecr 1039955668], length 100
08:42:27.412487 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [P.], seq 276:376, ack 382, win 126, options [nop,nop,TS val 1039955670 ecr 1453762316], length 100
08:42:27.412682 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [.], ack 376, win 4050, options [nop,nop,TS val 1453762317 ecr 1039955670], length 0
08:42:27.413662 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [P.], seq 382:1498, ack 376, win 4050, options [nop,nop,TS val 1453762318 ecr 1039955670], length 1116
08:42:27.415326 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [P.], seq 376:492, ack 1498, win 123, options [nop,nop,TS val 1039955673 ecr 1453762318], length 116
08:42:27.415521 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [.], ack 492, win 4043, options [nop,nop,TS val 1453762320 ecr 1039955673], length 0
08:42:27.416478 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [P.], seq 1498:1630, ack 492, win 4043, options [nop,nop,TS val 1453762321 ecr 1039955673], length 132
08:42:27.457856 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [.], ack 1630, win 123, options [nop,nop,TS val 1039955715 ecr 1453762321], length 0
here comes 30s wait, with packet like these:
08:42:37.637408 IP 192.168.222.1.8292 > 192.168.222.30.34974: Flags [.], ack 492, win 4043, options [nop,nop,TS val 1453772542 ecr 1039955715], length 0
08:42:37.637469 IP 192.168.222.30.34974 > 192.168.222.1.8292: Flags [.], ack 1630, win 123, options [nop,nop,TS val 1039965895 ecr 1453762321], length 0
During this wait there is no window, so people could think that Winbox crashed, but it will appear in 30 seconds.


Here is the same dump without "Open In New Window"
08:42:45.343604 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [S], seq 1022278702, win 32120, options [mss 1460,sackOK,TS val 1039973601 ecr 0,nop,wscale 8], length 0
08:42:45.343844 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [S.], seq 694524518, ack 1022278703, win 65160, options [mss 1460,sackOK,TS val 1453780248 ecr 1039973601,nop,wscale 4], length 0
08:42:45.343902 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [.], ack 1, win 126, options [nop,nop,TS val 1039973601 ecr 1453780248], length 0
08:42:45.364457 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [P.], seq 1:42, ack 1, win 126, options [nop,nop,TS val 1039973622 ecr 1453780248], length 41
08:42:45.364699 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [.], ack 42, win 4070, options [nop,nop,TS val 1453780269 ecr 1039973622], length 0
08:42:45.383537 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [P.], seq 1:52, ack 42, win 4070, options [nop,nop,TS val 1453780288 ecr 1039973622], length 51
08:42:45.383589 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [.], ack 52, win 126, options [nop,nop,TS val 1039973641 ecr 1453780288], length 0
08:42:45.394519 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [P.], seq 42:76, ack 52, win 126, options [nop,nop,TS val 1039973652 ecr 1453780288], length 34
08:42:45.394715 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [.], ack 76, win 4068, options [nop,nop,TS val 1453780299 ecr 1039973652], length 0
08:42:45.420327 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [P.], seq 52:86, ack 76, win 4068, options [nop,nop,TS val 1453780324 ecr 1039973652], length 34
08:42:45.420356 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [.], ack 86, win 126, options [nop,nop,TS val 1039973678 ecr 1453780324], length 0
08:42:45.420841 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [P.], seq 76:176, ack 86, win 126, options [nop,nop,TS val 1039973678 ecr 1453780324], length 100
08:42:45.421011 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [.], ack 176, win 4062, options [nop,nop,TS val 1453780325 ecr 1039973678], length 0
08:42:45.422923 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [P.], seq 86:282, ack 176, win 4062, options [nop,nop,TS val 1453780327 ecr 1039973678], length 196
08:42:45.422935 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [.], ack 282, win 126, options [nop,nop,TS val 1039973681 ecr 1453780327], length 0
08:42:45.423215 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [P.], seq 176:276, ack 282, win 126, options [nop,nop,TS val 1039973681 ecr 1453780327], length 100
08:42:45.423384 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [.], ack 276, win 4056, options [nop,nop,TS val 1453780328 ecr 1039973681], length 0
08:42:45.424240 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [P.], seq 282:382, ack 276, win 4056, options [nop,nop,TS val 1453780328 ecr 1039973681], length 100
08:42:45.425332 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [P.], seq 276:376, ack 382, win 126, options [nop,nop,TS val 1039973683 ecr 1453780328], length 100
08:42:45.425539 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [.], ack 376, win 4050, options [nop,nop,TS val 1453780330 ecr 1039973683], length 0
08:42:45.426469 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [P.], seq 382:1498, ack 376, win 4050, options [nop,nop,TS val 1453780331 ecr 1039973683], length 1116
08:42:45.428380 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [P.], seq 376:492, ack 1498, win 123, options [nop,nop,TS val 1039973686 ecr 1453780331], length 116
08:42:45.428591 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [.], ack 492, win 4043, options [nop,nop,TS val 1453780333 ecr 1039973686], length 0
08:42:45.429574 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [P.], seq 1498:1630, ack 492, win 4043, options [nop,nop,TS val 1453780334 ecr 1039973686], length 132
08:42:45.473861 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [.], ack 1630, win 123, options [nop,nop,TS val 1039973731 ecr 1453780334], length 0
08:42:45.552446 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [P.], seq 492:576, ack 1630, win 123, options [nop,nop,TS val 1039973810 ecr 1453780334], length 84
08:42:45.553919 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [P.], seq 1630:1730, ack 576, win 4038, options [nop,nop,TS val 1453780458 ecr 1039973810], length 100
08:42:45.553954 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [.], ack 1730, win 123, options [nop,nop,TS val 1039973812 ecr 1453780458], length 0
08:42:45.611446 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [P.], seq 576:676, ack 1730, win 123, options [nop,nop,TS val 1039973869 ecr 1453780458], length 100
08:42:45.616080 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [P.], seq 1730:2152, ack 676, win 4032, options [nop,nop,TS val 1453780520 ecr 1039973869], length 422
08:42:45.616126 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [P.], seq 676:876, ack 2152, win 123, options [nop,nop,TS val 1039973874 ecr 1453780520], length 200
08:42:45.617964 IP 192.168.222.1.8292 > 192.168.222.30.34976: Flags [P.], seq 2152:2332, ack 876, win 4020, options [nop,nop,TS val 1453780522 ecr 1039973874], length 180
08:42:45.617989 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [.], ack 2332, win 123, options [nop,nop,TS val 1039973876 ecr 1453780522], length 0
08:42:45.668333 IP 192.168.222.30.34976 > 192.168.222.1.8292: Flags [P.], seq 876:976, ack 2332, win 123, options [nop,nop,TS val 1039973926 ecr 1453780522], length 100
....

This is not urgent, but I find option "Open In New Window" very useful, because I manage 200+ devices and often have to visit more than one from same group, so without that option I have a few steps more each time I open new device: New Winbox, scroll 100-200 lines (or filter, but it is annoying to repeat the same search again and again), connect to router, repeat again and again...

Best regards,
Siniša
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Mon Feb 14, 2022 11:42 am

Doing some more work in winbox 3.34 I found that it has a tendency to hang when I paste copied text into a field. I never noticed that in 3.32 so I guess it is a new problem.
E.g. I go to IP->Addresses, copy one address/mask item, then go to Routing->BGP->Networks (this is on a router running v6), add a network and paste that copied value into the network field (of course with the intention to fix it up to become a network address rather than the router address).
At that point winbox became completely unresponsive and I had to forcibly close it.
That happend to me several times in other places as well, but I think every time it was when pasting something that by itself would not be allowable there but would have to be fixed up.
 
volkirik
Member Candidate
Member Candidate
Posts: 208
Joined: Sat Jul 23, 2016 2:03 pm

Re: WinBox v3.33 and v3.34 released!

Mon Feb 14, 2022 3:29 pm

good job!
 
User avatar
gmsmstr
Trainer
Trainer
Posts: 982
Joined: Fri Jun 04, 2004 2:22 am
Location: St. Louis, MO
Contact:

Re: WinBox v3.33 and v3.34 released!

Wed Feb 16, 2022 3:25 pm

When I open it, I can only open v7 devices, it acts like it will open but it won't open anything v6 until I open one v7 device, then i can open v6 devices..
 
densenator
just joined
Posts: 3
Joined: Tue Mar 10, 2020 3:31 pm

Re: WinBox v3.33 and v3.34 released!

Thu Feb 17, 2022 1:43 pm

WinBox crash on startup on windows 11 version when i use checknbox "open in new window"
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Thu Feb 17, 2022 2:58 pm

I used WinBox 3.34 to add new filters to a long list of Routing Filter rules. As always, I select some existing rule, COPY it, modify the name and maybe some other parameters, and move them to the correct place in the list where I want the new items to appear.
All seemed OK but the filters did not work. When I opened the window again in winbox, the new filter items were at a completely different place (and in a different sequence) than where I had moved them.
After moving them again, it was OK. But it makes me feel uneasy... other than the "random jumping around" problem seen in earlier winbox (which was fixed), I have not observed this before.
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: WinBox v3.33 and v3.34 released!

Thu Feb 17, 2022 3:01 pm

When I opened the window again in winbox, the new filter items were at a completely different place (and in a different sequence) than where I had moved them.
Really ?
This does not sound so good...
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Thu Feb 17, 2022 3:16 pm

Indeed... thinking about it, most of the rules appeared to have stuck at the place where they were after the copy, so the move was not really acted upon.
But in the first session, they appeared OK on screen. Only after the refresh (because I closed the window and re-opened it, F5 would probably have worked as well) they were in the wrong place.
 
ditonet
Forum Veteran
Forum Veteran
Posts: 835
Joined: Mon Oct 19, 2009 12:52 am
Location: Europe/Poland/Konstancin-Jeziorna
Contact:

Re: WinBox v3.33 and v3.34 released!

Thu Feb 17, 2022 8:58 pm

Personally i use the Open in New window Feature... It makes things easier in many situations...
When you connect to RoMON, this feature is absolutely necessary.
MT should fix it ASAP.

Regards, Grzegorz.
 
Knapek
just joined
Posts: 20
Joined: Sat Aug 01, 2009 3:08 pm

Re: WinBox v3.33 and v3.34 released!

Fri Feb 18, 2022 2:52 pm

I use WinBox 3.34 on Windows 11.
I can confirm it cannot open device with version 6 with checked Open in new window. WinBox is closed.
When I open device with version 7 with checked Open in new window first, than WinBox works as we expected until is closed.
Please - fix it.
 
Edified
newbie
Posts: 37
Joined: Thu Sep 16, 2010 9:02 am

Re: WinBox v3.33 and v3.34 released!

Sun Feb 20, 2022 2:01 am

I have an issue with Winbox (64bit) v3.34 on Windows 11. When I try to connect to any of a few Routerboard with firmware 6.49.2 right after login Winbox disappears, even when the Open In New Window checkbox is checked.

Curiously if I first login to a device with firmware 7.1.2 device it loads properly. Moreover I can subsequently connect to the 6.49.2 devices, even after I close the 7.1.2 session. All of the logins show up in the router logs whether of not winbox stayed open.

I have tried removing all the version folders as well as the session folder from %appdata%\Roaming\Mikrotik\Winbox with no effect.

Does Winbox provide logs somewhere else?
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: WinBox v3.33 and v3.34 released!

Sun Feb 20, 2022 8:17 pm

I had a similar problem as @pe1chl described, not with firewall rules but with the CapsMan access list...
i was testing an access list on a lab environment, and i did change the position of some rules several times... There was a moment that i noticed that some rules were not on the position i had placed them before...
 
pe1chl
Forum Guru
Forum Guru
Posts: 10194
Joined: Mon Jun 08, 2015 12:09 pm

Re: WinBox v3.33 and v3.34 released!

Sun Feb 20, 2022 9:00 pm

Let's hope this is not another issue that we will have to live with for a long time before MikroTik gets around to reproducing and fixing it!
(as happened with the issue of stuff randomly jumping around when the mouse button is held down)
It appears that some of these issues are only reproducible given some specific .viw file. Which is difficult to debug because .viw files are difficult to understand and modify.
I vote for changing the format of .viw files to something humanly readable, like JSON or XML.
 
Jivo
newbie
Posts: 35
Joined: Wed Jun 08, 2011 11:44 pm

Re: WinBox v3.33 released!

Sun Feb 20, 2022 10:42 pm

Thank you for this link.
3.34 DOES not work for ROS 6.xx.
I have tested with brand new RB4011, RB4011 upgraded to latest 6.XX, and 5 or 6 other routers with ROS 6.xx to which I normally connect with Winbox 3.32.
I am running Windows 10 Pro 21H2.
For anyone looking for previous version of WinBox: https://download.mikrotik.com/winbox/3.32/winbox64.exe
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

Re: WinBox v3.33 and v3.34 released!

Mon Feb 21, 2022 10:53 am

WinBox v3.35 released:

viewtopic.php?t=183456

Who is online

Users browsing this forum: krasikrumov and 17 guests