Unrecognized Ethernet Interface

RouterOS Beginner Basics
1

Update: I’ve worked around this by finding a supported interface card in storage and installing it. Feel free to move on and read something else!


Greetings,

I’ve installed the latest version of RouterOS (v6.40.0 x86 .iso) onto what once was an old windows 7 workstation that was sitting idle in the office. Unfortunately I am confronted with a problem during setup. Options A, D, and S are all unable to be configured due to there being no network interfaces being detected. So I did a little bit of poking around:

/system resource pci print 
#	Device	 Vendor						Name									  IRQ
0	02:00.0	Broadcom Corporation	 NetLink BCM57780 Gigabi...	    11
...

From the pci tier of the input hierarchy, I have tried a few permutations of get name 0, get 0 name, get [return] 0, etc (so that I could read the full name of the device) and am either met with ‘no such item’ or no output at all.

Despite showing an IRQ number, this device is not listed by /system resource irq print

/driver print
#	Driver
...
1	Broadcom Tigon3

Interestingly, a Broadcom driver is listed here. Perhaps this driver is incompatible with the device, despite the manufacturer being the same?

/interface print

Displays only an empty table.

I read in a separate thread that one cannot load device drivers onto RouterOS anymore, that they must be feature requested. Is that the case?

Other than that, can anyone give me advice for this situation? Our team here would like to put The Dude to work on our network, so we’re hoping to get this (or another) RouterOS box up and running soon!

Thanks for Reading,
Steven

2

You need to contact support support@mikrotik.com and they may be able to add in support for the specific device. If you have another Ethernet adaptor card lying around you might be able to use that as well.

The other option, and probably faster/easier, would be to use the cloud hosted router instead. This works within a virtual machine, so it doesn’t really matter what the underlying hardware is in a lot of ways. As long as the host operating system and hyper-visor support it, the virtual machine can use it. It also makes it possible to migrate the virtual machine to another physical machine later on if needed.

3

Thanks for the reply, I was actually just about to update the post. I did indeed find another adapter lying around which is recognized!

Now to really start exploring routerOS and the Dude.

Thanks again!