[SOLVED] Basic OSPF-question / no neighbour

RouterOS General
1

Hi,

i try to configure my first ospf-setup, consisting of 2x rb600 and 1x rb433.

all of them are connected “in a row”, so no typical ring setup, just one connected to the next.
looks like that:

rb600–rb600–rb433

i just added the networks at the ospf setup and activated the distribution of the default route at the first router and the distribution of connected routes on all routers.
the second rb600 now has the last (the rb433) as an ospf-neighbour, but the first one does not get connected by the means of ospf to the second. setup is the same on all 3 boards, except the networks and the default-route-setting on the first (even when not distributing a default route it won’t connect)
the first rb600 shows the second one as a neighbour but the second one has no neighbours except the rb433. and of course no routes from the first rb600 get injected in the routing-table on the second rb600.

configs:

first rb600:

[admin@inetfeed] > routing ospf print
router-id: 10.0.0.1
distribute-default: always-as-type-1
redistribute-connected: as-type-1
redistribute-static: no
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@inetfeed] > routing ospf network print
Flags: X - disabled, I - invalid

NETWORK AREA

0 192.168.0.0/24 backbone
1 10.0.0.0/30 backbone
[admin@inetfeed] > routing ospf neighbor print
0 router-id=10.0.0.2 address=10.0.0.2 interface=wlan1 priority=1
dr-address=10.0.0.2 backup-dr-address=0.0.0.0 state=“Init” state-changes=1
ls-retransmits=0 ls-requests=0 db-summaries=0


second rb600:

[admin@transit1] > routing ospf print
router-id: 10.0.0.2
distribute-default: never
redistribute-connected: as-type-1
redistribute-static: no
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@transit1] > routing ospf network print
Flags: X - disabled, I - invalid

NETWORK AREA

0 10.0.0.0/30 backbone
1 10.0.0.4/30 backbone
[admin@transit1] > routing ospf neighbor print
0 router-id=10.0.0.6 address=10.0.0.6 interface=wlan1 priority=1
dr-address=10.0.0.6 backup-dr-address=10.0.0.5 state=“Full”
state-changes=6 ls-retransmits=0 ls-requests=0 db-summaries=0
adjacency=12m54s

any ideas? help would be greatly appreciated. ah and btw all systems running 3.13.

2

Probably second RB600 is not receiving hello packets from first one. Check firewall rules, meybe you are dropping them accidentally.

3

all systems are fresh installed and no configuration has been done except wireless, ips, system identity and ospf. Firewall is not active.

4

I had that same problem in a few cases, and I’m yet to find a solution. In one case it worked fine till I added a new OSPF network, couldn’t get it working again so far yet(good thing OSPF is not critical for me)

I also had a problem earlier this week where OSPF stopped redistrobuting its default route, it worked fine for 2 months before that. Had to reboot the board.

IMO if you are just using 3 boards in a chain, rather use static routes. OFPF doesn’t always seem very stable to me.

5

yeah, this is just a lab-construct, no real production use. i just wanted to get familiar with the whole thing :slight_smile:

maybe i reset them to factory-defaults and try again, who knows.

thanks so far for your answers.

6

The main problem with that is “it just doesnt work, lets default and try again” is not good practice for production. Its fun to play with I agree, but things that stops working for no good reason is not accepable in my books.

7

full ack, that is definitely not acceptable

8

ok, even after resetting the config to factory-default, upgrading to 3.14 and upgrading the firmware to 2.17 (which shouldn’t affect this issue) and also using routing-test the ospf neighbour does not even get created on the second rb600 and is in state init on the first rb600.

anybody an idea of what i can try else?

9

ok, the solution was to use another mini-pci-slot, the used slot initialized the card in a not correct way and the connection just got up when i ping over it a few times.
using another slot it is working like a charm, wlan is up, ospf is up.
the strange thin is, the wlan-connection showed status up all the time and i was able to ping over it as soon it was established from remote, just ospf or rather broadcasts itself were not working. really strange but solved nonetheless