Is there any way to open multiple Winbox Loader versions? To be able to open the loader and have different lists of devices?
Thanks
Is there any way to open multiple Winbox Loader versions? To be able to open the loader and have different lists of devices?
Thanks
Something like Microsoft remote desktop connection manager would be nice. ![]()
BoingoNOC Do you mean open Winbox for two differant devices at the same time? Yes you can, I do it all the time.
No, he is referring to being able to use one version of WinBox to open random RouterOS versions in the field.
And tabs, like tabs in Firefox or Chrome.
webfig with tabs opened in firefox or chrome like tabs in firefox and chrome.
After all webfig is full inbox clone available on any modern browser. And there is at least one modern browser nowadays on any OS with decent GUI
Webfig is nice and it may have all options that WinBox does, but the overal user experience is nowhere close. WinBox can have any number of child windows arranged in any way user wants them. That includes dialogs, you can open more of them, to e.g. look at properties of one firewall rule while creating another one. In Webfig you only see one thing at a time (don’t even try to suggest fiddling with multiple browser windows). Difference is huge.
And IMHO original poster wanted to have more than one winbox.cfg (he asked for “different lists of devices”). E.g. when I’d manage more networks, it would be nice to open one WinBox Loader with list of devices from Network A only and separate one with devices from Network B only. Instead of current global list with everything.
for now, maybe this
$ wine ./winbox.exe --help
usage: winbox [<connect-to> [<login> [<password>]]]
helps a bit to organize stuff. (for now)
Our networks have grown -a lot-, and nothing beats Winbox when it comes to speed and lightness…
Compared to Winbox, a browser is an elephant.
I bet you guys use Winbox there on Mikrotik Headquarters, ![]()
A simple command-line parameter allowing to open winbox.cfg from a different place would suffice.
This way we could have infinite shortcuts to different groups of routers and, mainly, keep them on Dropbox.
(and share them with other staff members!) ![]()
Use different pc users: each users has is own address list…
I am sorry but I don’t understand… are you suggesting to create one windows user (with all the folder structures behind it) per routers group and switch windows users to alternate between them?
I know each user have a different winbox.cfg, but do you think this is a realistic alternative?
Exactly. ![]()
It’s not perfect, but there is a way, if you don’t mind a little beginner hacking. ![]()
Copy original winbox.exe to winbox1.exe. Open it in hex editor, search for string “AppData” and change it to “WinBox1”. Make sure you keep exactly seven characters and don’t change anything else in the file. If you do binary comparison of original and new file (using e.g. Total Commander), the only difference must be those few bytes you changed. Then add new variable to registry:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"WinBox1"="C:\\custom\\path\\to\\winbox\\data"
Now repeat the whole process with different variable for as many separate WinBoxes as you need.
In case you get an idea to use “.” (current directory) intead of full path, which would allow you to have WinBox saving data to current directory, save your time and don’t do it. It might appear to work, but it’s very unrealiable, because WinBox changes current directory. UNC paths don’t work either.
If anyone confirm that is working, in this thread, i got you +3!
Really great post Sob, but the feature request to Mikrotik still stands, right?
The method working?
What I posted is just a quick hack for “but I really need it right now!” situations. Because even if MikroTik adds the option to open different files with settings, you never know how long it’s going to take them.
Another option that comes to mind, is to completely forget WinBox Loader and its limited ability to store settings, and store them somewhere else. That might not sound like a very bright idea, because who should then copy it to WinBox all the time, when they want to connect, right? Wrong.
Fortunately, WinBox Loader does support autoconnect, when you call it with necessary parameters (as was pointed out in this thread already):
winbox.exe <address> <username> <password>
So if your favorite password manager can execute external commands… bingo! For example, lets take popular KeePass (tested with version 1, because I don’t like .NET version 2, but it will be probably the same or similar there). You’ll get as many different config files as you want, that is, if any number of folders and subfolders in one is not enough for you. Or if you need to share different subsets with different people. As a very nice bonus, passwords will be stored encrypted and protected by master password (unlike in winbox.cfg, where you can clearly see all passwords in plain text). To connect it together, you just need to copy winbox.exe to same directory and add the following line to KeePass.ini:
KeeUrlOverride=cmd://"{APPDIR}\winbox.exe" {URL} {USERNAME} {PASSWORD}
Then just double-click on URL column (where you put plain IP address or hostname) and you’re connected.
@rextended: Have a little faith in fellow user, or try it yourself. ![]()
Karma +5
I would like to open one version of winbox in multiple windows but with different lists of devices.
sob, what hex editor would you recommend?
having issues finding a good one.