Good Morning

I'm currently running Linux Mint 18.3 with Winbox 3.12 however my problem is that Winbox (Wine) does not discover devices and cannot use mac address. So I can only use Winbox with IP addressing if I know what the address is and I cannot risk resetting the unit because I won't be able to log into the unit again with 0.0.0.0.

Do any of you have some success stories?

Kind Regards

I ran Winbox on Ubuntu for a long time with no issues. MAC discovery would only work though if I had a gateway set on the interface so maybe that could be something to try.

I ran Winbox on Ubuntu for a long time with no issues. MAC discovery would only work though if I had a gateway set on the interface so maybe that could be something to try.

Tried that, still doesn't discover anything. Tried it on a Ubuntu machine also no luck. Still can only use the unit's IP address.

I don't have problems since wine-1.8.0 on Arch Linux. To access via MAC address, I need to set-up at least a IPv4 link-local address on interface.

MAC discovery would only work though if I had a gateway set on the interface [...]

Same here.

Winbox officially doesn't support MAC at Linux, and the default settings from the MikroTik starts IP at 192.168.88.1.

Have you actually connected Windows device instead of Linux machine and tested this? Maybe simply ND is disabled on RouterBOARDs in your network. We are not aware about any issues with Winbox discovery neither on Windows, Linux or Mac.

Have you actually connected Windows device instead of Linux machine and tested this? Maybe simply ND is disabled on RouterBOARDs in your network.

I'm running Mint 17.3 and discovery does NOT work with 3.11 or 3.12. Using a Windows machine on the same network, it all discovers as you would expect (with the usual weirdness of the unreliability of CHRs of course).

Have you actually connected Windows device instead of Linux machine and tested this? Maybe simply ND is disabled on RouterBOARDs in your network.

I'm running Mint 17.3 and discovery does NOT work with 3.11 or 3.12. Using a Windows machine on the same network, it all discovers as you would expect (with the usual weirdness of the unreliability of CHRs of course).

If Windows works and Linux doesn't then maybe it could be something to do with a recent change in the emulator? Any chance of trying a Ubuntu machine as that has always previously worked for me.

I'm running Mint 17.3 and discovery does NOT work with 3.11 or 3.12. Using a Windows machine on the same network, it all discovers as you would expect (with the usual weirdness of the unreliability of CHRs of course).

If Windows works and Linux doesn't then maybe it could be something to do with a recent change in the emulator? Any chance of trying a Ubuntu machine as that has always previously worked for me.

I tried it on another machine running 17.3 and it works there, so it's not clear cut as to what my problem is. The non-working machine has multiple network interfaces, whereas the working one only has one. I guess I need to Wireshark it to see what's going on. I presume Winbox sends MNDP packets out on all interfaces...

On Windows and Mac and Fedora but Mint and Ubuntu no luck. Was there a specific Winbox version you guys used that actually worked? I don't want to go back to Winbox 2 due to the Malware on it's dll files.

Can't always have static addressing but going to try it tomorrow when i'm back at work.

Have you actually connected Windows device instead of Linux machine and tested this? Maybe simply ND is disabled on RouterBOARDs in your network. We are not aware about any issues with Winbox discovery neither on Windows, Linux or Mac.

Mikrotik's work great. I've tested with Arch, Mint and Ubuntu. No discovery or Mac address use available on winbox. Can only use the Ip to login if I know what the IP is.

Thats funny! RouterOS is linux based but management software ( winbox) available only for windows. )

Sent from my C6833 using Tapatalk

Thats funny! RouterOS is linux based but management software ( winbox) available only for windows. )

Sent from my C6833 using Tapatalk

I've just had a big LOL on your comment. Same with a lot of brands. Controllers and software are linux based and the discovery tools etc are windows. Why can't they just build it in java that is supported by all platforms haha.

Winbox was pure JAVA app until v2.4 actually.
We ourselves use Winbox in Wine, it works great.

Code: Select all

Why can't they just build it in java that is supported by all platforms haha.

Winbox was pure JAVA app until v2.4 actually.
We ourselves use Winbox in Wine, it works great.

It works great when using the IP but it does not discover any devices and layer 2 login does not work. Both my Arc and Ubuntu machines. What did you do differently on your machine to get it to work @Normis.

Maybe you have this feature turned off on the particular interface?

Post results of:

"/tool mac-server mac-winbox export"
"/ip neighbor export"

Does this computer interface have an IP address set on it or not ?

With static addresses on Arch Linux KERNEL: Linux 4.16.4-1, No issues at all.
You can try to launch wine under different wine prefix:
WINEPREFIX=~/.winbox wine winbox.exe

Maybe you have this feature turned off on the particular interface?

Post results of:

"/tool mac-server mac-winbox export"
"/ip neighbor export"

Does this computer interface have an IP address set on it or not ?

Will post the results to you asap. Thank you.

Winbox 3.13 also works fine for me under Linux.
If in doubt, you can always manually scan for mac-addresses in your network.
Using arp-scan for example: "eth0" has to be replaced with your network card. If your Network is different "192.168.88.0/24" also have to be changed.
"arp-scan" is available for most Linux distros or can be installed easily.

I don't have problems since wine-1.8.0 on Arch Linux. To access via MAC address, I need to set-up at least a IPv4 link-local address on interface.

MAC discovery would only work though if I had a gateway set on the interface [...]

Same here.

I tested it confirm as well in linux mint 19.1 tessa, I could only acces through mac-access if I had an IP setup on interface

Winbox MAC discovery and connect using MAC address works for me.
Ubuntu 19.04
Kernel: 5.0.0-20-generic
Wine: wine-4.12.1 (Staging)
Winbox: v3.19

It didn't work because I had ufw enabled. After disabling and clearing iptables it worked.

The only issue I am having now is with DPI scaling, everything else works great.

Winbox MAC discovery and connect using MAC address works for me.
Ubuntu 19.04
Kernel: 5.0.0-20-generic
Wine: wine-4.12.1 (Staging)
Winbox: v3.19

It didn't work because I had ufw enabled. After disabling and clearing iptables it worked.

The only issue I am having now is with DPI scaling, everything else works great.

With OpenSUSE Leap 15.1 was the same issue - firewall!

Disabling the firewall is kinda risky. How to allow winbox with UFW?

Hello team!

Same question: how to enable Winbox (wine) with UFW? Stopping UFW every time to work with winbox is not a good idea....
I opened it: 5678, 8728, 8291 and now I see "Neighbour" but can't connect, got error ERROR: could not connect to XXXXXX

pls help?

Here's how things work:

RB devices use MNDP to announce their presence ... MNDP is broadcast to IPv4 address 255.255.255.255 (which is not usual IP subnet broadcast address) and (if IPv6 is enabled) to ff02::1 "all nodes" IPv6 multicast address. If iptables is configured to block reception of broadcasts with dst-address set to "weird" broadcast addresses, then wine won't see those devices.

When winbox tries to use MAC connection (which is MAC telnet), it will be sending IP/UDP packets with dst-address set to 255.255.255.255. MT device will be replying with IP/UDP packets with src-address set to 0.0.0.0 and destination address set to 255.255.255.255. Again, if iptables is dropping packets with "weird" source or destination addresses, it will drop these.

I'm not familiar with how UFW sets iptables. Use command iptables -L -vn to get iptables settings and check each and every rule to see if there's one blocking MAC telnet. And adjust rules to allow it.

The problem is I am not an expert in Linux and I do not yet know what exactly needs to do :)

I guess most of power users on this forum don't use UFW (they use iptables directly) so it's not very likely somebody will provide a really good "recipe" for enabling winbox in UFW.

FYI

The Uncomplicated Firewall (ufw) is a front-end for iptables and is particularly well-suited for host-based firewalls. ufw provides a framework for managing netfilter, as well as a command-line interface for manipulating the firewall. ufw aims to provide an easy to use interface for people unfamiliar with firewall concepts, while at the same time simplifies complicated iptables commands to help an administrator who knows what he or she is doing. ufw is an upstream for other distributions and graphical front-ends.

But, ok. You are right. Maybe someone can provide solution for iptables?

As with ROS firewall (which is yet another UI to iptablrs BTW): right solution very much depends on current state. Hence my suggestion to check what UFW did on your machine and then add appropriate rule to the right place in right chain.

Or better yet: find the right settings for UFW. Mixing direct config of iptables with UFW might mess things ...

Can anyone elaborate how UFW blocks WinBox? You mean UFW also blocks OUTPUT chain too?

I'm sure there are many experts on this forum that would be able to interpret iptables. I might be able as well, but I'm sure as hell that I won't install UFW just to get a list of iptables rules that default UFW enforces. So somebody running UFW (minimum config which interferes with winbox would be ideal) should provide both UFW config and resulting iptables and we might get to the bottom of it.

Winbox and UFW use
ufw allow from 0.0.0.0 to 255.255.255.255
ufw allow 5678/udp
from SU user

to discover in winbox under wine on second ethernet without default gw,
one should add a route. For example:

To get it working under ufw firewall you need to allow port 5678/udp (Mikrotik Neighbor Discovery Protocol) to pick up ROS devices on L2 level, port 20561/udp (MAC winbox) to establish mac winbox session and allow 0.0.0.0, as ROS device will use it as src IP address.