Change interface name. Is it right?

Question

System administration

I have a thought here. I usually call the microte interface 1.buh 2.glavbuh 3.notwork 4.govnootdel .... and so on. The ordinal visualization in winbox is also saved and I don’t need comments to understand what works on this port. In the logs it is immediately clear where the source of the problem is. Is this approach correct?) Can there be pitfalls?

Answer 1

This is the most correct approach for visualization. The router is more important not the names of the interfaces but their numbers. For example in scripts.

Answer 2

Of course there are pitfalls. Tomorrow you will have a colleague who will fucking demolish your demonism with transliteration. And it will leave the names of the interfaces by default with normal comments to them, namely comments.
ether1 - ISP Romashka
ether2 - local network
ether3 - accountant
Yes, even if you have crs125 as a router - what the hell to call interfaces, today the accountant was there, tomorrow the printer was plugged in, socket numbers in the comments and that's it.

Answer 3

theoretically there could be problems due to a dot in the name, but if everything works for you ...