CHR x86 ethernet interfaces random names

RouterOS General
1

Hi!

Once and once again im facing problem with CHR x86 interface names on EVE virtual enviroment.
Interface names are named in some random fashion after reboot and i can not find the root of such behavior.

Example:

[admin@R-02] /routing bgp peer> /interface ethernet export
# jan/07/2018 18:11:02 by RouterOS 6.41
/interface ethernet
set [ find default-name=ether2 ] name=ether1
set [ find default-name=ether3 ] name=ether2
set [ find default-name=ether4 ] name=ether3
set [ find default-name=ether1 ] name=ether4

Wiki says “for any other reason interfaces on the router are renamed”:
https://wiki.mikrotik.com/wiki/Tips_and_Tricks_for_Beginners_and_Experienced_Users_of_RouterOS#Make_sure_that_interface_names_are_correct

Any fix on that?

2

Hi
Did you siolve this issue?
I’m running through the same problems.

3

@Vooray did you ever find a solution to this? I’m seeing the same thing in my environment

set [ find default-name=ether3 ] name=ether1 speed=1Gbps
set [ find default-name=ether4 ] name=ether2 speed=1Gbps
set [ find default-name=ether1 ] name=ether3 speed=1Gbps
set [ find default-name=ether2 ] name=ether4 speed=1Gbps

Cisco CDP Neighbors show as below even though in my test environment they’re connected on ether1

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
MikroTik         Gig 0/2              111               R            MikroTik  ether3

Does this affect you being able ping to and from the WAN interface of the Mikrotik instance?

I’m having this issue, very strange

4

Hello, I have this issue too.

I’ve tested it on 6.39.3 (bugfix), 6.40.8(bugfix), 6.42.6 on Vmware and KVM/QENU.

Is it any solution?

Regards,
MMS101

5

I am facing the same problem. I created a CHR and added 8 ethernet interfaces, one by one as I already know about this issue,
hoping that they will keep the same name. After every interface I added I renamed it from ether1 to ether1-purpose1 etc until ether8-purpose8
and after having done all that only 2 of them have kept the name in /interface print while it still is set in /export.
After reboot the mapping between default-name and given name is a complete jumble.
And the interfaces do not connect to the correct networks either!

HELP!

6

Running which version?
There’s something about this in 6.44beta.

7

I am running 6.43.1 (stable)
I found that after a reset-to-defaults the name mapping appears consistent.
Maybe I should have added all interfaces at once before first boot instead of one-by-one while the router was running…
(I hoped that the software would build a mapping from PCI-ID or MAC-Address to interface number)

However, now that I have done that it has become very unstable. It crashes with “Irq without vector” messages.
Should I try with the RC?