Could you provide us with more information? What router do you use? What version? Do you use Wine (the latest one)?Not working (closing) on opening older router version like 6.49.2
Windows 10 x64, WinBox x64, RB4011iGS+, RouterOS v6.49.2Could you provide us with more information? What router do you use? What version? Do you use Wine (the latest one)?Not working (closing) on opening older router version like 6.49.2
Are you able to repeat it more than once?Windows 10 x64, WinBox x64, RB4011iGS+, RouterOS v6.49.2
Could you provide us with more information? What router do you use? What version? Do you use Wine (the latest one)?
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.
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.Are you able to repeat it more than once?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.
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...How can you worry about winbox, if you have a time machine!
That doesn't mean it became unusableDude has been discontinued (again)
There should be 3.32: https://download.mikrotik.com/winbox/3.32/winbox64.exeFor anyone looking for previous version of WinBox: https://download.mikrotik.com/winbox/3.33/winbox64.exe
Hi Normis, how is that's? Mikrotik's have in mind a replacement?Dude has been discontinued (again)
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.Mikrotik's have in mind a replacement?
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...If it works for you, great, you can use it.
Does this mean we should not plan to see a dude package for V7? Last I'd heard in Sept you'd saidWe 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.
Yes, we are working on it, it will be made
Unfortunately, didn't help in my case. 3.32 is working fine. Give my some debug switch I will use to send you log.What's new in v3.34:
*) fixed WinBox crash on startup (introduced in v3.33);
same hereWin11+Winbox3.33-3.34 - crash on connect to device. 3.32 - working fine
clear cache did not work, or not connectet deviceWorks for me on win11, maybe try to clear cache and connect to the router with empty session (not saved)
Clearing the sessions folder helped meWorks for me on win11, maybe try to clear cache and connect to the router with empty session (not saved)
Thank you!What's new in v3.34:
*) fixed WinBox crash on startup (introduced in v3.33);
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.Not work on Windows XP
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.
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...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.
Clearing cache didn't help either...Works for me on win11, maybe try to clear cache and connect to the router with empty session (not saved)
Just upgraded the router to 7.1.2 and WinBox 3.34 x64 is working fine with the same device.Clearing cache didn't help either...Works for me on win11, maybe try to clear cache and connect to the router with empty session (not saved)
Windows 10 x64, WinBox 3.34 x64, this time: hAP ac^3 with 6.49.2 (stable).
Tks 4 the infoWe 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.
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.exeIs it possible to download 3.32?
So, what for I have bought RB1100x4DUDE EDITION ebaut one year ago??? Tell your boss, that this is stupid!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.
Maybe they should at least update the www.mikrotik.com website... https://mikrotik.com/thedude saysSo, what for I have bought RB1100x4DUDE EDITION ebaut one year ago??? Tell your boss, that this is stupid!
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.Dude has been discontinued (again)
Windows 10 x64, WinBox 3.34 x64, this time: hAP ac^3 with 6.49.2 (stable).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.
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.That doesn't mean it became unusableDude has been discontinued (again)
And reading of the release topic of the previous version to at least fix the newly introduced bugs in that version... :-)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. :)
The problem with version 3.34 appears on Windows systems with multiple monitors and the "Open In New Window"option enabledTo 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.
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.Could you provide us with more information? What router do you use? What version? Do you use Wine (the latest one)?Not working (closing) on opening older router version like 6.49.2
Tested on a CCR1009-7G-1C-1S+ and i had no issue...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.
Just tested and "open in new window" does not always work... If that is what you mean...And what about unchecking "open in new window" in the open dialog?
You mean, all those years it was working fine, and now when they decided to deprecate it - it broke?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.
That doesn't mean it became unusable
Let MT only recompile to v7 The Dude as is now and, I think, Dude users will not be angry so much.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.
It is only a partial success.*) properly display all packets captured by sniffer;
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.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.
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
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
Before connecting to any router.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?
Had same issue as well... Both on a two monitor computer but on my laptop as well...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
I have reported something similar a month ago, but now it'd officially a problem because WIINE 7 is recommended by Mikrotik: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.
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
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
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
....
Really ?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.
When you connect to RoMON, this feature is absolutely necessary.Personally i use the Open in New window Feature... It makes things easier in many situations...
For anyone looking for previous version of WinBox: https://download.mikrotik.com/winbox/3.32/winbox64.exe