Nope. And unlikely. RouterOS value, IMO, is that is a relatively fixed schema and consistent interface around Linux networking... so that it is NOT a hodgepodge of different Linux tools and files with variant schemes/file formats/etc.
There's a learning curve to RouterOS config/scripting, but the idea once you understand the scheme... all the protocol/service configuration follows the same scheme which makes it easier long-term.
Overall, RouterOS does not use "files", other than store/retrieve them in a few places for L5+ features or custom scripting. While RouterOS uses the Linux kernel, its userland does not use GNU/BSD/etc for "userland". Most Linux things to have RouterOS command equalivalnts. So /file/print is their version of "ls". There is a :grep, if that help. As a result, a shell would not help with configuration, there are no "config files".
They do offer container, so an easy solution is use the with alpine if you need Linux tools. And you mount the RouterOS file system to container to do more typical Linux things.
There's a learning curve to RouterOS config/scripting, but the idea once you understand the scheme... all the protocol/service configuration follows the same scheme which makes it easier long-term.
Overall, RouterOS does not use "files", other than store/retrieve them in a few places for L5+ features or custom scripting. While RouterOS uses the Linux kernel, its userland does not use GNU/BSD/etc for "userland". Most Linux things to have RouterOS command equalivalnts. So /file/print is their version of "ls". There is a :grep, if that help. As a result, a shell would not help with configuration, there are no "config files".
They do offer container, so an easy solution is use the with alpine if you need Linux tools. And you mount the RouterOS file system to container to do more typical Linux things.
Statistics: Posted by Amm0 — Wed Mar 12, 2025 8:22 pm