We are having an issue with OSPF under 3.15 and 3.16. The log files follow. We have two matched routers that we upgraded to 3.15 last week. This morning at 2:00, I downgraded one to 3.13, and upgraded the other to 3.16 due to this problem. The first issue:

05:59:29 route,ospf,info OSPF: Invalid cryptographic sequence number
05:59:29 route,ospf,info OSPF: mine=2212
05:59:29 route,ospf,info OSPF: received=2211
05:59:29 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
05:59:29 route,ospf,info OSPF: source=x.x.x.x
06:29:29 route,ospf,info OSPF: Invalid cryptographic sequence number
06:29:29 route,ospf,info OSPF: mine=2459
06:29:29 route,ospf,info OSPF: received=2458
06:29:29 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
06:29:29 route,ospf,info OSPF: source=x.x.x.x
06:59:29 route,ospf,info OSPF: Invalid cryptographic sequence number
06:59:29 route,ospf,info OSPF: mine=2707
06:59:29 route,ospf,info OSPF: received=2706
06:59:29 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
06:59:29 route,ospf,info OSPF: source=x.x.x.x
07:59:29 route,ospf,info OSPF: Invalid cryptographic sequence number
07:59:29 route,ospf,info OSPF: mine=3211
07:59:29 route,ospf,info OSPF: received=3210
07:59:29 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
07:59:29 route,ospf,info OSPF: source=x.x.x.x
08:59:29 route,ospf,info OSPF: Invalid cryptographic sequence number
08:59:29 route,ospf,info OSPF: mine=3724
08:59:29 route,ospf,info OSPF: received=3722
08:59:29 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
08:59:29 route,ospf,info OSPF: source=x.x.x.x

You can see basically every hour, we're seeing the authentication failed, but it doesn't seem to affect the routing. Then this morning, we get the following

10:34:02 route,ospf,info OSPF: OSPF neighbor x.x.x.x: state change from Full to Init
10:34:03 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:03 route,ospf,info OSPF: state=Init
10:34:03 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:03 route,ospf,info OSPF: state=Init
10:34:03 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:03 route,ospf,info OSPF: state=Init
10:34:10 route,ospf,info OSPF: OSPF neighbor x.x.x.x: state change from Full to Init
10:34:13 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:13 route,ospf,info OSPF: state=Init
10:34:19 route,ospf,info OSPF: Invalid cryptographic sequence number
10:34:19 route,ospf,info OSPF: mine=4712
10:34:19 route,ospf,info OSPF: received=4707
10:34:19 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
10:34:19 route,ospf,info OSPF: source=x.x.x.x
10:34:20 route,ospf,info OSPF: OSPF neighbor x.x.x.x: state change from Full to Init
10:34:23 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:23 route,ospf,info OSPF: state=Init
10:34:29 route,ospf,info OSPF: Invalid cryptographic sequence number
10:34:29 route,ospf,info OSPF: mine=4800
10:34:29 route,ospf,info OSPF: received=4798
10:34:29 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
10:34:29 route,ospf,info OSPF: source=x.x.x.x
10:34:29 route,ospf,info OSPF: Invalid cryptographic sequence number
10:34:29 route,ospf,info OSPF: mine=4806
10:34:29 route,ospf,info OSPF: received=4802
10:34:29 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
10:34:29 route,ospf,info OSPF: source=x.x.x.x
10:34:29 route,ospf,info OSPF: Invalid cryptographic sequence number
10:34:29 route,ospf,info OSPF: mine=4806
10:34:29 route,ospf,info OSPF: received=4804
10:34:29 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
10:34:29 route,ospf,info OSPF: source=x.x.x.x
10:34:30 route,ospf,info OSPF: OSPF neighbor x.x.x.x: state change from Full to Init
10:34:33 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:33 route,ospf,info OSPF: state=Init
10:34:33 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:33 route,ospf,info OSPF: state=Init
10:34:39 route,ospf,info OSPF: Invalid cryptographic sequence number
10:34:39 route,ospf,info OSPF: mine=4925
10:34:39 route,ospf,info OSPF: received=4922
10:34:39 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
10:34:39 route,ospf,info OSPF: source=x.x.x.x
10:34:39 route,ospf,info OSPF: Invalid cryptographic sequence number
10:34:39 route,ospf,info OSPF: mine=4927
10:34:39 route,ospf,info OSPF: received=4926
10:34:39 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
10:34:39 route,ospf,info OSPF: source=x.x.x.x
10:34:40 route,ospf,info OSPF: OSPF neighbor x.x.x.x: state change from Full to Init
10:34:43 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:43 route,ospf,info OSPF: state=Init
10:34:43 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:43 route,ospf,info OSPF: state=Init
10:34:49 route,ospf,info OSPF: Invalid cryptographic sequence number
10:34:49 route,ospf,info OSPF: mine=5016
10:34:49 route,ospf,info OSPF: received=5013
10:34:49 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
10:34:49 route,ospf,info OSPF: source=x.x.x.x
10:34:50 route,ospf,info OSPF: OSPF neighbor x.x.x.x: state change from Full to Init
10:34:53 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:53 route,ospf,info OSPF: state=Init
10:34:54 route,ospf,info OSPF: Ignoring Link State Acknowledgment packet: wrong peer state
10:34:54 route,ospf,info OSPF: state=Init
10:34:59 route,ospf,info OSPF: Invalid cryptographic sequence number
10:34:59 route,ospf,info OSPF: mine=5105
10:34:59 route,ospf,info OSPF: received=5104
10:34:59 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
10:34:59 route,ospf,info OSPF: source=x.x.x.x
10:34:59 route,ospf,info OSPF: Invalid cryptographic sequence number
10:34:59 route,ospf,info OSPF: mine=5108
10:34:59 route,ospf,info OSPF: received=5106
10:34:59 route,ospf,info OSPF: Discarding packet: MD5 authentication failed
10:34:59 route,ospf,info OSPF: source=x.x.x.x


At this point, it simply loops between init and full. Under 3.15, the only way I could clear it was to reboot both routers. Under 3.16 and 3.13, all I had to do was reboot the 3.16. Anyone have any ideas?

Thanks

Dan

check your time and dates on both routers.

Both are NTP synchronized. We had the problem with the clock running too fast under 3.15, but it was doing the same thing under 3.16, where the time and date bug was fixed.

We have the same problem here.

Can you upload a capture file by chance?

Have you set the router id?

It seems to be important on 3.15+

I also think ospf seems more unreliable on the newer versions.

Any Other suggestions?

I'm having issues, not related to MD5, but routes keep appearing and dropping, OSPF adds the hotspot interface as Priority 1, Cost 10 Default gateway, although traffic doesn't go out that way, I don't need OSPF on that interface, so I setup Hotspot manually as Priority 0 DROTHER.

However, I can't find why my routes keep dropping and restarting. Everything was setup and operating on 2.9.38, upgrade to 3.19 has broken it.

Setup.

AP0 - WDS - AP1
AP1- WDS - AP0
AP2 - WDS - AP1
AP2 - WDS - AP0

OSPF
2.4Ghz Links Cost 55, Priority 1, MD5, Broadcast
5.8Ghz Links, Cost 10, Priority 1, MD5, Broadcast
Uplinks, Ethernet, Cost 1, Priority 1, Static

No RIP, BGP or other Interior Routing Protocols.

Routes will drop from approx 80 Routes, down to 30 (down to 17 if I remove the Static Routes that are keeping us alive)

Any help appreciated. I'm going to try and replicate the issue in my testing network.

At the moment my Testing network is all Dynamic OSPF and seems to work ok. But that's 3 nodes vs 50 in this ospf cloud.

Thanks!!

Have you set the router id?

It seems to be important on 3.15+

I also think ospf seems more unreliable on the newer versions.

Router ID should be set up automatically by router (highest ip address), if this option is not set manually. If not so, this is the issue of RouterOS 3.15+.
What's with 3.20?

I have a number of routers installed at different versions. Under the later versions of RouterOS the router id in OSPF settings seems to be set to 0.0.0.0 (not the highest IP). However, when you look at the neighbor list on each of the routers in the network the router id is correct.

Can someone at Mikrotik confirm this is just a display issue?

I have a number of routers installed at different versions. Under the later versions of RouterOS the router id in OSPF settings seems to be set to 0.0.0.0 (not the highest IP). However, when you look at the neighbor list on each of the routers in the network the router id is correct.

Can someone at Mikrotik confirm this is just a display issue?

yessss, if you set 0.0.0.0 in settings, highest IP is selected dynamically, and you can see it in OSPF neighbours. ID in settings does not change

I've just been on a late night mission re-configuring the ospf for my routers and updating the last 4 to 3.19, it's now 3:40am.

However I've got OSPF working!! YAAY! Bar 1 Router, more about him in a tick. OSPF Settings which worked and killed my pain.

Set ospf to ptmp, MD5, with AUTH, changed my main uplinks to priority 2, upgraded all routers to the same ROS.

Note: When changing Network Type I had to disable and re-enable the ospf interface to get it to talk nicely.

The rogue one...
I have one rogue router now, it's claiming "Database Description packet has different master status flag new master flag=false"

Can anyone shed some light on what this means?

As a bit more of an update. Not everything is ok.. I'm getting...

Edit:! Not quite ok, I spoke too soon.

Wireless debug logging to dudes syslog and I'm getting lots of


wireless,info wlan1: data from unknown device 00:80:48:XX:XX:XX, sent deauth. As in up to 20 or 30 in a second.

The link is good!! I have -61 quality at both ends. I'm guessing this is part of what is causing my routes to keep dropping and re-assigning. Along with other things. Any suggestions? Hardware? Config? interferrence?