B
B
brar2021-02-01 19:15:24
Mikrotik
brar, 2021-02-01 19:15:24

Why can't I connect via mac-telnet after updating the firmware?

There are Mikrotik1 (hereinafter M1) and Mikrotik2 (hereinafter M2).

M1 - router. There is access to it. Everything is OK.
M2 - connected to M1 in his (M1) ether4.
There are no settings in M2, it works like a switch.

Before updating firmware from 6.41 stable to 46.8 long-term on M2 and rebooting, it was: / tool ​​mac -
scan ether4
7C:3A:6F:35:4B:05 -telnet 7C:3A:6F:35:4B:05 Just like from a computer in the local network, starting a winbox, one could see M2 in the list of neighbors. After updating the firmware on M2 from 6.41 stable to 46.8 long-term and rebooting, it became:


/tool mac-scan ether4
The list sees 7C:3A:6F:35:4B:00 (note that 00 is at the end, not 05 as before). The dhcp server does not issue an address, more precisely, a request from M2 does not come => does not receive an address.
However:
/tool mac-telnet 7C:3A:6F:35:4B:00
I get a whack. A computer with a winbox also stopped seeing M2 in the list of neighbors. Well, accordingly, there are no M2 in / ip neighbors on M1.
In what trabl can be?
PS There is no physical access to the micros.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
P
poisons, 2021-02-01
@poisons

Ports per m2 in the bridge? Is the admin poppy on the bridge set? I guess not.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question