I am running fedora core 9 and got wine installed and winbox ver. 2.2.13, everything works fine, except winbox doesn't pick up any routers when I press the [...] button, and I can't access router via their mac address, I get a time out error.

Any tips or hints?

thanx.

I can't access router via their mac address

MAC addresses only apply when dealing with a layer 2 connection, like two devices connected to the same switch.

As for the ... button, it also can be limited to things connected to the same switch.

Are you behind more than one router? Or are you behind one, and the other routers on the other side of that one?

Are you using a bridged network?

+ check if there are no firewalls on your PC or inbetween

II'm using wine 1.0.1 to use WinBox and I can't connect to the Mikrotik using the mac address.
I'm directly connected to the Routerboard (eth to eth), and clicking on [...] nothing appear, so I've to startup windows to guess the ip address of routeros and get back to linux again.
I was trying to use neighbour viewer with not results at all.

There is any configuration we should make on wine config or something else to get winbox fully functional on linux?

Why Mikrotik don't release a winbox version for linux thinking in the way linux and unix are the SO most used by networks administrators, even routeros use linux kernel.

greetings!
Leonardo Rivanera

Yep, winbox on wine doesn't seem to work properly. I've only just tried this so I'm not that familiar with wine.

I'm posting this from a Fedora Core 10 box running Winbox, Netinstall, and The Dude (test environment). The ... button will work under Linux, however we only run the three applications as root. I could be wrong on this, but we were never able to find a way to make some of the functionality work without running the 3 apps as root.

You should be able to just sudo the applications so you don't have to run your whole environment as root.

Scott

I can't access router via their mac address

MAC addresses only apply when dealing with a layer 2 connection, like two devices connected to the same switch.

As for the ... button, it also can be limited to things connected to the same switch.

Are you behind more than one router? Or are you behind one, and the other routers on the other side of that one?

Are you using a bridged network?

Bugger I'm dumb. Took me ages to figure out why i couldn't connect after mucking around with the settings

I think I have finally replicated this problem and found out what is going on. In order for mac-winbox to work properly, you must have an IP address, subnet mask, AND default gateway configured on the interface connecting to the MikroTik. Without this information, wine doesn't have a route to the destination network. It will give a "sendto error 10051" in the console. Hope this helps everyone out.

thanks, I will try this out.

To work around this problem I have always invoked "dhclient eth0" and let it give up, then the ... button will work. Also I didn't have this problem until KDE4 came out, I have no idea what that would have to do with it, but I does make a difference??? I actually ran KDE3 for a long time on my laptop just because of that problem until I found the dhclient work-around.

I think I have finally replicated this problem and found out what is going on. In order for mac-winbox to work properly, you must have an IP address, subnet mask, AND default gateway configured on the interface connecting to the MikroTik. Without this information, wine doesn't have a route to the destination network. It will give a "sendto error 10051" in the console. Hope this helps everyone out.

Thank you very much!!!
I waste a couple of hours to fix the problem, the solution was very easy...

In connection manager set firewall zone as trustedWorks perfect!

try disabling the interfaces that you are not Using on your PC! I'm always having trouble connecting to a mikrotik router when I've got extra interfaces around (especially my virtualbox and vmware connections)