RouterOS allows slight system customization with the help of a branding package. This is a special system package, which you can generate from within your mikrotik.com client account, in the client account section "Branding maker". The resulting file will have a .dpk extension and can be installed by all the same means as an .npk package. The generated package can be installed in any RouterOS version. To install the package in a device you simply need to upload it and reboot the router, you can also use Netinstall tool for the same effect.
...
This is the text logo shown, when logging into the commang command line interface, iei.e. Telnet, SSH, Winbox Terminal. The ASCII logo you can create right there in the browser, or copy from any other plaintext editor. Make sure it is not wider than the form in the branding maker page, or your logo will be distorted.
...
You can customize the default RouterOS information page, which shows up, when accessing the router IP address, and a password is set on the device. When making the HTML file, you can use a few of these variables:
- %version% will change to the router's current version
- %host% will change to the routers IP address. Use these variables in the Telnet link, or in the header.
The file must be named "index2.html". Make sure you use properly nested HTML to make your page compatible with all browsers. You can also upload images or javasctipt JavaScript files, they must referenced reference to the same path as the index file, no custom folder names can be used. If you wish to only change the MikroTik logo, and not upload the whole html HTML file, the name of the default image is mikrotik_logo.png, uploading another file with the same name, will overwrite the original.
...
"Default configuration": Note that when using the default configuration file, configuration is appended when simply installing the package, but after using system reset, only the configuration in your file will be used, all other standard default config will not be used during reset. The file must be a text/rsc file with one RouterOS command per line. You can use a export file from the console as a starting point, but we recommend only leaving the exact comands commands you want to be run. This configuration will be kept even after RouterOS reset.
...