I bought my first MikroTik because I wanted enterprise networking features at home. While RouterOS is incredibly powerful, I found the learning curve for common management tasks to be fairly steep compared to other platforms i have used professionally
That experience led me to build SimpleTik.
My goal is simply to reduce the learning curve by making common networking tasks easier to visualize and manage, while still preserving the flexibility and power of RouterOS.
Current Preview features include:
Network Overview with live network statistics
VLAN creation and management
Multi-WAN configuration
DHCP management
Firewall management
Traffic analysis
Virtual Router profiles for experimenting with different network configurations
Intent-driven command queue that stages RouterOS operations before they are applied
Write operations and script export are intentionally disabled in the Preview while those features continue to be developed and tested.
I'd genuinely appreciate any feedback, suggestions, or ideas from the MikroTik community.
This looks very cool indeed. I like the look of traffic monitor pages and firewall management. I've not got a Windows device anymore but I hope you get some great feedback for this!
That's a great shame. In the last year or so, with the arrival of WinBox 4, I managed to resolve my last Windows dependency after more than 30 years. And Windows 11 is so awful that I am not going to go back and support a Windows installation again.
biggest problem with these kind of tools is that user will feel "almighty / superfoce" beause using this tool let him adjust MT config with few clicks. vlans, fw ... without real knowledge.
problems arise when this tool is not enough for something, and then, steep learning curve kick in, but this time harder
head scatch, uhhmu, i haved a progam for vlans/fw/etc, and clicked here and there, but now, i need to unlearn/learn fom scratch
for example, firewall settings, looked at screenshot, it tend to have taste of OpenWRT zone config style, which is wrong in MT wold
anyway, if someone is fan of webfig and similar, maybe this tool could be useful
Clearly "the great shame" is a Whinderps only dependency. More and more people are moving away for more advanced platforms, so releasing a tool that only supports one is rapidly becoming less and less wise . . . Heck, even Mikrotik figured that out!
I wouldn't say "great job" as the "good job" is enough.
We do not know the reasons why it is Win only but maybe it was a school assigment and as it seems to work good enough to be shared, so it has been shared. Is it written in .net? If yes, then migrating to other platforms should be quite simple.
A lot of us, users, does not need fancy multiplatform tools. Simple "install&forget" tool that shows a few crucial data is enough, so let them use it.
It could be the basis for creating a sort of unofficial "RouterOS for Home" aimed at home/soho users. I like the idea, since it's undeniable that Mikrotik is slowly addressing these users as well (did someone say DLNA/file sharing?).
What about thinking about a container, making everything independent of the client platform?
No need - Winbox 4 already provided that (and since I am not hung up on ancient Winblows look and feel, I have no issues with it.).
And I won't touch Wine with a 10 foot pole! Every time I have touched it it has sucked, so I run full QEMU virtualization, and can emulate pretty much any architecture/run any OS from inside Linux. Perhaps Wine works now, but no desire to move that far backwards with this in place and rock solid . . .
Seriously, on Linux, I have had zero issues with WB4.
Thanks! You aren't wrong, and cross-platform support is definitely something I'd like to explore in the future. For the initial build, I chose to continue on the platform I was most comfortable with and have used professionally for many years. That let me focus on developing the application rather than trying to learn a new framework at the same time.
That said, I may have unintentionally backed myself into a bit of a corner with WPF, as I've since learned it isn't the easiest framework to port to other platforms.
True, that would have been the smarter way to go... Hindsight is always 20/20. The code itself is C# which from what i can tell is somewhat portable, but yeah, id have to redesign the interface for a new platform...
.
,we used to have:
. . . )
