Failed connect to Winbox after upgrade to 7.18 from 1.17.2

The board is RB5009, and the export file is



It seems the bridge is wrong configured, any one can help me to resolve this issue, thanks a lot.

Anyone can help me to resolve this issue?

People in other time zones need to wake up, have coffee, do other work.

Are you saying that you could connect with Winbox under 7.17 but not under 7.18, with no other changes? You can see the MAC address but not connect using it? If so, the bridge is unlikely to be the problem whatever other foibles might be concealed in that 168 KB .rsc file (the last one I downloaded was 9 KB).

The mac address is not showed in the neighbors, and wifi is not working too.

All your connections being normal, I suggest netinstall.

That .rsc is “huge” (it is usually a handful of Kb).

Your next attempt is to reset the router, but then you will need to re-import the configuration.

And unless the issue was caused by a (rare but possible) hiccup in the update process that does not repeat when you re-apply that configuration, you may lock yourself out again.

Your configuration seems full of errors (whether they are part of the issue locking you out is another thing), in theory (apart some particular places like your regexp’s) in a configuration there should be no “*” (asterisk), when a reference to something is lost because the object has been removed or re moved or renamed, the RoS replaces it with an asterisk followed by a (hex) number,
You have many of them, both in disabled items and in active ones.

I believe you should take your time and clean/review that saved configuration before attempting to restore it.

Particularly with a complex configuration like yours, it would be a very good idea (if possible) to reserve a port out of any bridge to emergency management/access.

The usually recommended way to re-import the configuration is to copy and paste section by section in terminal (in Winbox), given the complexity of yours, besides the cleanup, I would copy it to a spreadsheet and colour the various sections, so that it is easier to not miss or overlap anything.

If reset doesn’t work, your next attempt should be netinstall, of course, but trying with reset costs nothing.

The router is reseted now, and now work fine after downgrade to 7.17.2, but upgrade to 7.18(restore from config file) also failed, the config contains some “*” chars(asterisk), it seems that some asterisk is the item id.

As was pointed out its a very complex config, with errors and quite frankly full of bogus stuff like layer7 etc…
Concur, you should netinstall to 7.18 and from defaults, start from scratch focussing solely on needed traffic.

The question I have is did you actually do this config or take it over from someone else??
THe reason being is you attempted no work to fix any of the errors, think its the bridge, and simply reset the router to the previous config.

@phascogale, I actually did look at this last night a tad late, and almost threw up looking at the config, I decided sleep was a better idea.

:laughing: lots config is from network, thanks for your reply, I will try to set a lan as manage port, then update to 7.18.

So its not your config and you dont understand it?

@anav, when I looked I decided that either I did not understand it or I did not want to, probably both.

THere is no point when it would appear that OP doesnt have a clue of what he/she inherited.

I mean the layer 7 config is from network, other config is configured by myself.

The issue may be du to DHCP spoofing as described by @TrevinLC1997.

By the way I have a similar experience upon upgrading directly from 7.18.0RC2 to 7.19.0BETA2 and the network in question does use DHCP snooping and option 82 (MVRP is also used therefore the Mikrotik devices show up).

It works fine now after reinstall with netinstall and restore config with rsc exported.