First excuse my English, it is terrible. I have a problem related to OSPF, the situation and the following: I have a 1000 and rb 433ah RBS 6 connected to a switch, all interconnected by the network 10.2.0.0/27, all are within the same area. rb in 1000 I see all neighbors (433AHs), already in the RBS 433 I do not see the routes and the rb 1000 rb 1000's and my gateway that are not transferred to the 433, the log is showing this error:

11:56:15 route,ospf,info state=Init
11:58:03 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
11:58:03 route,ospf,info state=Init
11:58:06 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
11:58:06 route,ospf,info state=Init
11:58:07 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
11:58:07 route,ospf,info state=Init
11:58:08 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
11:58:08 route,ospf,info state=Init
11:59:34 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
11:59:34 route,ospf,info state=Init
11:59:44 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
11:59:44 route,ospf,info state=Init
11:59:48 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
11:59:48 route,ospf,info state=Init
12:01:20 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
12:01:20 route,ospf,info state=Init
12:04:19 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
12:04:19 route,ospf,info state=Init
12:08:04 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
12:08:04 route,ospf,info state=Init
12:09:47 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
12:09:47 route,ospf,info state=Init
12:10:03 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state
12:10:03 route,ospf,info state=Init
12:10:35 route,ospf,info Ignoring Link State Acknowledgment packet: wrong peer state

rb 1000
router-id: 10.2.0.1
distribute-default: always-as-type-1
redistribute-connected: as-type-1
redistribute-static: as-type-1
redistribute-rip: no
redistribute-bgp: no
metric-default: 1
metric-connected: 20
metric-static: 20
metric-rip: 20
metric-bgp: 4294967295
mpls-te-area: unspecified
mpls-te-router-id: unspecified

[admin@Sumicity RB1000] /routing ospf network> print
Flags: X - disabled, I - invalid
# NETWORK AREA
0 10.2.0.0/27 area_2



[admin@Sumicity RB1000] /routing ospf neighbor> print
0 router-id=10.2.0.6 address=10.2.0.6 interface=Lan B priority=1 dr-address=10.2.0.6 backup-dr-address=10.2.0.2 state="Init" state-changes=1 ls-retransmits=0
ls-requests=0 db-summaries=0

1 router-id=10.2.0.2 address=10.2.0.2 interface=Lan B priority=1 dr-address=10.2.0.6 backup-dr-address=10.2.0.2 state="Init" state-changes=1 ls-retransmits=0
ls-requests=0 db-summaries=0


RBS 433 AH:

[admin@ALEM Alemrio6] /routing ospf> print
router-id: 10.2.0.6
distribute-default: never
redistribute-connected: as-type-1
redistribute-static: as-type-1
redistribute-rip: no
redistribute-bgp: no
metric-default: 1
metric-connected: 20
metric-static: 20
metric-rip: 20
metric-bgp: 20
mpls-te-area: unspecified
mpls-te-router-id: unspecified


[admin@ALEM Alemrio6] /routing ospf network> print
Flags: X - disabled, I - invalid
# NETWORK AREA
0 10.2.0.0/27 area_2
1 10.2.136.0/30 area_2





if someone can help me I thank you, I need to put the ospf run to give valid ips to my clients, hugs to all!

What version of RouterOS are you running?

and... try with routing-test package =)

Sorry for the size of the topic, I'm using version 3.27. I tested here using rounting-test, post the result soon, thanks =)

man, I put the routing test, and not resolved, I am constantly having these problems, some routers do not recognize their neighbors, and some of the ospf to work from scratch and does not work anymore. someone can give me a light? I need urgently resolve this issue. and 3:28 am using version 3.27, with both I have the same problem. embrace the all =)

anyt updates. seeing this on a network now too.

supout.rif + support@mikrotik.com = love

I took the supurt rif of my router and sent to the mkt, the problem was being caused by the existing nat router, since I have the solution, thanks for all the attention =)