MikroTik

Hi everybody,
in the last days I tried a test configuration before roll-out v4 upgrade to all my Mikrotik based network.

Well, on every single Routerboard upgraded from 3.24 to 4.5 I found the same bug on OSPF: "authentication" parameter under Routing-->OSPF-->Interfaces-->Interface that was initially set to "MD5" changed automatically to "none". This happened on 532, 532A, 600 and 433AH both on ethernet and wireless interfaces with OSPF on them.

Doing that, OSPF link went down: no more neighbors and devices where reachable only via MAC address.

Solution: under Routing-->OSPF-->Interfaces-->Interface add a new interface with the very same parameters of the original one, but with authentication=MD5. Doing so, the original ones switch to MD5 and OSPF is up and running again.

Below you'll find attached images of before and after.

Bye,
mattia

It is not a bug, In v4 and also in v3.x routing-test, authentication is configured for each ospf interface.

Well, actually it is a bug, since authentication parameters change with no reason after upgrade, crashing all OSPF links that need authentication!!!

Well, actually it is a bug, since authentication parameters change with no reason

actually, the reason is upgrade: v4's 'routing' package is v3's 'routing-test'. so, if you were using 'routing-test' in v3 - you'll upgrade smoothly

Ok, but I was upgrading from 3.24 to 4.5 using common "combined package" and are both stable versions of RouterOS and there is no advice on this "strange" behaviour, so a common user would never be aware of what is about to happen.

So if you don't agree on recognizing the arbitrary change of OSPF parameters as a bug (again: switching from "MD5" to "none" crashes your whole network and this is definitely a bug for me!!), at least you should agree on warning OSPF users on this behaviour before upgrading!!!

Cheers,
mattia

iw4eky is right for sure. It' impossible to forecast this kind of behaviour and use in advance specific packages...
I believe iw4eky is a very good mikrotik expert and if i were you i would invite him in china for the MuM for free.

iw4eky is right for sure. It' impossible to forecast this kind of behaviour and use in advance specific packages...
I believe iw4eky is a very good mikrotik expert and if i were you i would invite him in china for the MuM for free.

Guys, you know I love you, but MuM in Poland would be closer to me!

And yet, no kidding, authentication on OSPF interfaces after upgrading from 3.24 to 4.5 is really a bug.

Use of md5 authentication makes sense only if you specify authentication-key.
In older routing package you could set authentication type also in area configuration, in that case dynamic interfaces will show authentication as md5, but there are no key and use of that configuration is useless. That is why this option was removed.

Proper OSPF authentication is configured per interface where authentication type and key is specified, which you don't have.

I would suggest to configure authentication on all OSPF routers the way it should be configured, then upgrade process will be smooth.

Proper OSPF authentication is configured per interface where authentication type and key is specified, which you don't have.

I would suggest to configure authentication on all OSPF routers the way it should be configured, then upgrade process will be smooth.

Right, this is a good observation.

But please, in next release of RouterOS, pay attention to fix the case of MD5 with no key (before the upgrade) that becomes "none" and crashes OSPF after the upgrade to 4.5!