All Ethernet Interfaces show 'R' -running no matter what

I was hoping that the new releases of v5 would solve a problem I have with virtually all my x86 RouterOS machines.
Primarily Dell servers with either Intel 82547GI, or Broadcom NetXtreme BCM5721 GBe controllers.
Other industrial class x86 machines with 82575EB/82574L and 82801G chipsets.

All Ethernet ports always indicate ‘running’. This has been going on for quite a few releases back as far as I can remember, but it is now causing me logistical problems. (Are you sure you have link status?..NO I am not!)

ROS tells me all ports are ‘running’, but if you go to port status, it indicates proper link state, i.e. auto-negotion=done (with no connection), speed=unknown, with no connection to port whatsoever…

RBs dont seem to have this problem. I would hope someone else could corroborate this behaviour, but cant figure out why this hasnt been noticed before. Maybe I am missing something, but there are a lot of these types of machines and chipsets running ROS out there for years.

MT, anyone, please advise…

This should be a FAQ entry.

disable-running-check (yes | no; Default: yes) Disable running check. If this value is set to ‘no’, the router automatically detects whether the NIC is connected with a device in the network or not.

http://wiki.mikrotik.com/wiki/Manual:Interface/Ethernet

On x86, disable-runnning-check in “/interface ethernet” defaults to “yes”. Set it to “no” to get a true reading.

Thank fewi Now is clear for me
:slight_smile:

I’m curious, in what circumstances one would want to set disable-running-check=yes ?

I can’t think of a single scenario.

Learn a new thing every day. Thanks for solving the now obvious mystery. Also cant find a reason why it shoud be in that default condition. Idiosyncrasy of ROS on x86… :sunglasses:

that is historic, when x86 boxes was not this powerful as they are today and drivers lacked cheep possibility to check state - it was set to disabled, to not to strain weak CPU with cheap network adapter.