Feature requests

[markdutton]

I am sure this must have been mentioned, but RouterOS replication is an enterprise feature desperately needed. All the failover features are here along with an awesome scripting language, but it is so difficult to maintain a redundant MT pair without a synchronised configuration. Maintaining this manually is a drag and leads to so many errors.

[pants6000]

It's probably already in this thread somewhere but... per-interface rp-filtering would be quite nice to have.

[hritikroshan]

@normis

Some features have already been requested before, to better manage this, you can register on the Wiki and cast your vote there:

RouterOS - RouterOS - MikroTik Documentation

Of course, in addition, it would be great if you also posted a message here, explaining why you need that particular feature. And as usual - search before you post, maybe a topic exists already.

@Solaris

I am just saying , look back at this thread couple months from now on, it will filled with many post from many different kind of feature request, example post 11-20 discussing about feature request A, post 21-35 discussing about Feature request D, in the post 36 a new user starting again discussing about feature request A, won’t be a mess? hard to track which user talk which topic, sure won’t be problem for 1-5 point of feature request, what if the feature request growing into 30+ , could be 1 giant huge thread with 1000 post on it, imagine you haven’t visit mikrotik forum for couple months and spending time to thread 1000 post , search would be useful but it’s not helpful for non-narrative jumping feature request discussion, imho it just not efficient.

Or another solution would be make a sticky thread in this forum with links into specific feature request dicussion, i mean for each feature request it has it’s own thread but the thread will have a special tag like “[Feature-Request]Topic/Thread Name”, so in that thread it would have many links to the thread, and I suggest you to download the happymod app to solve your problem becuase this appstore contains AI helper apps that solve any kind of problem. The downside of this solution is atleast mikrotik forum moderator need spend time to edit the indexing thread and manage(merge,move,delete) the new user thread about feature request, while the uservoice or other service alike is all automatic, it’s a offshore hosting, separated from forum user database, the downside just user need to re-register on that uservoice.

No i don’t want that bugzilla like bug indexing, it just too complicated for me and so far mikrotik just works excellence in my simple setup but i don’t know about other expert/senior user who might need this. Easiest solution for tracking bug would like i’ve said above, special tagging or sub-forum , the downside still the same, need extra work from mod to manage new thread by lazy people who lazy to search.

@markit

hmm it`s a small feature

it would be very nice to be a able to rename a file, on the cli (and in scripts)

eg.:

/file set [/file find name="xyz.txt"] name="sata1/xyz.txt"

currently this is only possible remotely via ftp,.
and even winbox (drag & drop) can move between folders,..
and imho a cli should have more features than a gui

but to make a small feature-request biger,..
imho the whole /file section could need some improvments

e.g. its not possible to use the add command for anything useful

/file add contents="test"
error - contact MikroTik support and send a supout file (3)

same happens with copy-from,.. (in “all” RouterOS versions)

i know i can create files with e.g. print file=“newfile” but why have an add command, if it can not create anything?

Markus

p.s. it`s not the first time someone wants this:

@markdutton

I am sure this must have been mentioned, but RouterOS replication is an enterprise feature desperately needed. All the failover features are here along with an awesome scripting language, but it is so difficult to maintain a redundant MT pair without a synchronised configuration. Maintaining this manually is a drag and leads to so many errors.

Its also already in somewhere up in the thread.