I would like to see some feature to automatically replicate parts of configuration form one mikrotik to another.
For an example, I would like to maintain address list on one Mikrotik and then let other MikroTiks in network to copy that list in their own configuration. As that list is maintained automatically on source MT, other should be able to update on their own. that would allow me to set status on some user, by adding his IP to an address list, and make that status visible to other Mikrotiks if connection goes through chain of MTs.
the appropriate and secure way would be for the dude to have a global address list feature, and an option to push that address list to various clients. then you make the changes in the dude, and it gets added automatically to the router after the next polling interval
It may be risky if done through FTP, thats why suggested MT’s to communicate directly, in more secure manner.
API is here, it is just matter of adding some commands.
Unnecessary? Maybe for you. It would really help me manage my network. Actually, I need more, but this one would do the job, and it looks possible to implement.
I have lots of RBs in use, but I can’t say that this feature would be useful for anything. Every unit is configured differently and doing something different than the next.
What would be nice is a way to take a config from a RB and apply it to another one of the same type. Basically like ghosting a hard drive but from one routerboard to another. I’ve tried exporting scripts and backups but there is always something little that makes it hard. Mac address difference, ver difference, package difference etc…
Would be really nice to copy everything from a running RB and apply it to another one off the shelf and be ready for deployment. If this is possible and i have overlooked how to do it please somebody shed some light
For “export” scripts to be imported into another router, you have to change them a little.
If you have lots of similar exampler, then you export one config, put the commands in a way that they should work, and save them. ( should work: put security profiles for wireless before interface config, get out the mac addresses from export, put default names on interfaces: eg. eth1, wlan1, etc., and use same tacticts when connecting public/internal networks: eg. each time public is eth1, and so on. )
I tried many times, and till now the most annoying thing was exporting a wireless config. You put config interface before security profiles. It gets you an error with no security profile with that name exists.
So, made a list of sec. profiles, put them all at the beggining, and that’s it. The rest, useless configs for me, those that i don’t change from default, i get them out of the export file, and i have a smaller one.
Also, in some post, normis promised they’ll try to put on DUDE something similar to this:
select multiple devices and show common prorpeties that can be changed. Might help.
It’s kind of incipient support for this, but, for mt device, here is what i can set if i select multiple devices:
type of device
parents
agent
SNMP PROFILE ( for me, it’s kind’a cool this…
user name
password.
( secure, router os device also are available.)
For me, it’s cool to set username, password ( that for small groups) and snmp profile, for larger groups.
( user name and password should pleas someone on the forum who was looking for this… )
Guess that there could be implemented some kind of layout common propreties, and many others.
That’s what i found till now. If there are others… write it down.
But hey, it’s a start
Seen that.