Hi everyone,
I'm using version 7.20.1 because that was available when I set up the network (I was previously using v6).
I'm experiencing an anomaly when exporting the configuration; the export doesn't include anything about the "lo" interface.
For example, it doesn't include the fact that I renamed it (which is less relevant), nor does it include any associated IP addresses, nor whether it's present as an instance template in OSPF.
This creates major problems with backups.
I see we've now upgraded to version 7.20.4, but I'm wondering if this bug has been resolved.
Thanks for your help.
So far, no one has reported this bug,
because no one had ever thought of changing the default name of the loopbkack interface...
I wonder why... right???
Leave the default name, and you'll see that it exports everything... (at least that's how it is in 7.16.2)
Thanks for your reply.
I understand it's unusual. I'm used to calling the loopback "extended" and not "lo" since v6, so it was instinctive to do so here too.
I'll do some testing without renaming it, and with the latest versions, maybe this won't be the case.
If anyone else has experience with this, please let me know.
Thanks
you miss the "r"... 
"lo" do not exist (or better, is hidden) on v6, so when you create another interface for loopback, is another interface, not "lo"...
so, still create "extended" interface if you want keep how you manage the device on the past, and leave alone "lo"...
The issue comes from RouterOS treating “lo” as a system interface, so renaming it makes the exporter ignore it. The safest approach is to leave “lo” untouched and create your own loopback interface if you want a custom name.