Winbox: router not detected despite being on the same broadcast domain

RouterOS General
1

Hello,
I have a cable plugged directly into ether2 from my desktop running winbox. I tried ether1 and even ether3.
When I run the arp command I can see the router but winbox can’t.
Of course I can’t connect either, otherwise I wouldn’t be here.

2

New router ? Default configuration ? Does your computer gets IP address from the router ? If it does can you access webfig ?

3

It’s my own config. Yes I get an IP from the router.

Thankfully I was able to connect with SSH and enable and connect with webfig. Winbox is still broken though and I would like to fix it. I usually connect through a Windows VM but this issue prompted me to install wine, so keep in mind I have never used winbox with it successfully.

4

Anything in your own config that would be blocking WinBox? Best bet is post your configuration - else we’re mostly guessing.

5

deleted

6
7

Now internet is back but I lost connection with the router.
I can ping the IP but neither webfig or SSH respond. I didn’t touch the firewall.
Wireshark is complaining of TCP retransmission on port 22. “TCP Port numbers reused”.
No winbox, no webfig, no SSH. That’s not fun.

EDIT: connection to webfig and SSH reestablished by plugging my ethernet cable directly into ether2 instead of passing through a switch.

8

It’s weird that I can connect with SSH and webfig but winbox still can’t see the router.

9

Did you mess with the interface lists ?

10

Winbox can connect with the router’s IP address. Only mactelnet does’t work.

Yeah, I added ether2 to LAN because this port was connected to the switch, but maybe I was not supposed to do that. Either way winbox can’t connect via mactelnet.

Here are my addresses and routes. Does something look wrong?
My Mikrotik router is connected to an internet-facing router while I am learning the ropes.

#   ADDRESS            NETWORK       INTERFACE         
;;; defconf
0   192.168.88.1/24    192.168.88.0  bridge            
1   172.16.0.1/24      172.16.0.0    bridge-guest-vlan9
2   192.168.1.149/24   192.168.1.0   ether1            
3 D 192.168.88.252/24  192.168.88.0  ether1 

[code]  
  #       DST-ADDRESS      GATEWAY             DISTANCE
  DIdH  0.0.0.0/0        192.168.88.1               1
0  As   0.0.0.0/0        192.168.1.1                1
  DAc   172.16.0.0/24    bridge-guest-vlan9         0
  DAc   192.168.1.0/24   ether1                     0
  DAc + 192.168.88.0/24  ether1                     0
  DAc + 192.168.88.0/24  bridge                     0
11

Save yourself and anyone else a bit of trouble and post your config …
You can’t learn if you are chasing your own tail.

Worst case (if your really don’t want to show your config), reset to default and start over.
Take step by step and see where it stops working. That’s where you went wrong then.

12

I just did. I posted just part of it to save time. If everything looks good. I will look elsewhere.

13

How to export and post your configuration:
http://forum.mikrotik.com/t/forum-rules/173010/5

14

No, you did not.
Those are extracts from print statements. That’s not config.

Use the instructions Larsa linked to.

15

I decided to reset the configuration. Mactelnet still doesn’t work on my Linux machine but I confirmed it does work with a fresh Windows install. I will let it be and move on.

16

The 3rd party linux mactelnet client ia reportedly incompatible with recent (like: last few years) ROS versions.

17

Just to be clear, I am talking about Winbox (MAC-ADDRESS), which is not a third-party client.

18

Does your linux run any kind of firewall or SElinux? These two may interfere with winbox and mac connectivity.

19

I use Portmaster. It didn’t prompt me to unblock anything. I also tried disabling it. I have Apparmor. Disabling it didn’t work either.
What I should do next is try with a different Linux host but I currently lack the motivation.

20

Are you talking about neighbor discovery or actually connecting? Are you able to connect if you manually enter the MAC address?